Upcoming OpenBMC release 2.11

Upcoming OpenBMC release 2.11

[Patrick Williams]

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

Hello,

It has been almost a year since our last release (2.9).  We created a tag for
2.10.0-rc1 but it was never completed.  We recently created a branch for the
upstream Yocto Honister release and primed it with everything that was in our
`master` plus an update of Yocto to the Honister release branch.

What I'd like to do is target January 14th, 2022 for our 2.11 release.  If you
are interested in your systems working on that release branch, please test the
'honister' branch and let me know of any issues you see either here or in
#release-planning.

Since there has typically not been tons of demand on release branches and
support of them, this is going to be a low-effort process.  If anyone is
interested in better defining (and executing) a release process going forward,
we are certainly interested in volunteers.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Upcoming OpenBMC release 2.11

[Patrick Williams]

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

Reminder...

On Wed, Dec 15, 2021 at 04:14:10PM -0600, Patrick Williams wrote:
> What I'd like to do is target January 14th, 2022 for our 2.11 release.  If you
> are interested in your systems working on that release branch, please test the
> 'honister' branch and let me know of any issues you see either here or in
> #release-planning.

I have not heard from anyone on interest in a 2.11 release.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Upcoming OpenBMC release 2.11

[Thaj]

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

Hi Patrick,

2.9 is quiet old. There are a lot of changes after that. A newer u-boot
with secure boot support, better AST2600 support etc. A new release is
necessary. There is no 2.11.0-rc1 yet. Is it possible to initiate a release
process?

Regards,
Thaj

On Thu, 20 Jan 2022, 01:30 Patrick Williams, <patrick@stwcx.xyz> wrote:

> Reminder...
>
> On Wed, Dec 15, 2021 at 04:14:10PM -0600, Patrick Williams wrote:
> > What I'd like to do is target January 14th, 2022 for our 2.11 release.
> If you
> > are interested in your systems working on that release branch, please
> test the
> > 'honister' branch and let me know of any issues you see either here or in
> > #release-planning.
>
> I have not heard from anyone on interest in a 2.11 release.
>
> --
> Patrick Williams
>

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

Re: Upcoming OpenBMC release 2.11

[Patrick Williams]

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

On Fri, Feb 11, 2022 at 03:33:12PM +0530, Thaj wrote:
> Hi Patrick,

Hello Thaj,

> 
> 2.9 is quiet old. There are a lot of changes after that. A newer u-boot
> with secure boot support, better AST2600 support etc. A new release is
> necessary. 

It seems that not many people who are active contributors in the community
actually care about releases, so there hasn't been much effort put into it.
You used the word "necessary".  Would you care to expand, for the community,
what your use case is where you rely on releases?

> There is no 2.11.0-rc1 yet. Is it possible to initiate a release
> process?

The honister branch is effectively the '2.11.0-rc'.  I don't have permissions
to create tags myself.  I'll see if Brad has bandwidth to create a tag in the
near future.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Upcoming OpenBMC release 2.11

[Brad Bishop]

> On Feb 11, 2022, at 3:56 PM, Patrick Williams <patrick@stwcx.xyz> wrote:
> 
> On Fri, Feb 11, 2022 at 03:33:12PM +0530, Thaj wrote:
>> Hi Patrick,
> 
> Hello Thaj,
> 
>> 
>> 2.9 is quiet old. There are a lot of changes after that. A newer u-boot
>> with secure boot support, better AST2600 support etc. A new release is
>> necessary. 
> 
> It seems that not many people who are active contributors in the community
> actually care about releases, so there hasn't been much effort put into it.
> You used the word "necessary".  Would you care to expand, for the community,
> what your use case is where you rely on releases?
> 
>> There is no 2.11.0-rc1 yet. Is it possible to initiate a release
>> process?
> 
> The honister branch is effectively the '2.11.0-rc'.  I don't have permissions
> to create tags myself.  I'll see if Brad has bandwidth to create a tag in the
> near future.

We have a 2.11.0 tag now.