All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: About upgrade a package to a Release Candidate version (RCX)
Date: Tue, 28 Jul 2015 17:45:03 +0800	[thread overview]
Message-ID: <55B74F1F.2050409@windriver.com> (raw)
In-Reply-To: <1438076219.24778.4.camel@linuxfoundation.org>


On 07/28/2015 05:36 PM, Richard Purdie wrote:
> On Tue, 2015-07-28 at 09:09 +0100, Burton, Ross wrote:
>> On 28 July 2015 at 08:53, Robert Yang <liezhi.yang@windriver.com>
>> wrote:
>>          Is it a good idea to upgrade a package to a Release Candidate
>>          version,
>>          such as RC1, RC2 and so on ? I think no because:
>>
>>          1) Maybe the RC version is not stable enough.
>>          2) Maybe the package's final version doesn't release when
>>             oe-core/meta-oe releases, I think that use an older but
>>          stable
>>             version is better than new RC version usually.
>>
>> In general that's true, - qemu is the obvious recent exception because
>> they should be releasing before we freeze and there were major fixes
>> in the RC compared to the latest stable release.
>>
> Agreed. If there is a pressing reason for an RC release which gives us
> more benefit than drawback, we can consider it on a case by case basis.
> With QEMU and the autobuilder issues we've been seeing, we decided we're
> better off being close to upstream right now.
>

Got it , thanks.

// Robert

> Cheers,
>
> Richard
>
>
>
>


      reply	other threads:[~2015-07-28  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  7:53 About upgrade a package to a Release Candidate version (RCX) Robert Yang
2015-07-28  8:09 ` Burton, Ross
2015-07-28  9:36   ` Richard Purdie
2015-07-28  9:45     ` Robert Yang [this message]

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=55B74F1F.2050409@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@intel.com \
    /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.