About upgrade a package to a Release Candidate version (RCX)

About upgrade a package to a Release Candidate version (RCX)

[Robert Yang]

Hello,

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.

-- 
Thanks

Robert

Re: About upgrade a package to a Release Candidate version (RCX)

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

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.

Ross

[-- Attachment #2: Type: text/html, Size: 1049 bytes --]

Re: About upgrade a package to a Release Candidate version (RCX)

[Richard Purdie]

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.

Cheers,

Richard

Re: About upgrade a package to a Release Candidate version (RCX)

[Robert Yang]

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
>
>
>
>