All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: <openembedded-devel@lists.openembedded.org>,
	Martin Jansa <martin.jansa@gmail.com>
Subject: Discuss: ruby-1.9.x EOL -- someone to add ruby-2.2?
Date: Mon, 2 Mar 2015 09:14:29 -0500	[thread overview]
Message-ID: <54F47045.4080503@windriver.com> (raw)


As stated in the post below, ruby-1.9.3 is no longer supported
and CVEs will not be released.

I'm not a rubyist but I assume we should upgrade to ruby-2.2.0 which
became the stable version as of December 25, 2014. Comments?
Martin, you are listed as maintainer of the meta-multimedia,
do you have any concerns about such an upgrade?

If anyone wants to start work on this for meta-oe, that'd be great.
If no one gets around to it, then a developer from WindRiver will
likely be able to work on it but not a few months.

../Randy

---
As of today, all support for Ruby 1.9.3 has ended. Bug and security 
fixes from more recent Ruby versions will no longer be backported to 1.9.3.

This end of life was announced over a year ago.

We highly recommend that you upgrade to Ruby 2.0.0 or above as soon as 
possible. Please contact us if you’d like to continue maintaining the 
1.9.3 branch or if for some reason you can’t upgrade.

Posted by Olivier Lacan on 23 Feb 2015
---
Also see:
https://bugs.ruby-lang.org/projects/ruby/wiki/ReleaseEngineering

-- 
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200 Ottawa, Ontario, 
Canada K2K 2W5


             reply	other threads:[~2015-03-02 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 14:14 Randy MacLeod [this message]
2015-03-02 14:26 ` Discuss: ruby-1.9.x EOL -- someone to add ruby-2.2? Martin Jansa
2015-04-02  4:39   ` akuster808
2015-04-02  4:57     ` Tim Orling
2015-04-02 14:30       ` Randy MacLeod

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54F47045.4080503@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.