[bitbake-devel] New Release Number 2.99 in Bugzilla

[Stephano Cetola]

Please excuse the cross posting here. This information is pertinent to
anyone submitting bugs to the Yocto project Bugzilla, so I want to reach
as large an audience as is appropriate.

The Yocto Project team is moving to a new release planning process and I
want to provide an overview as there will be some things I need from
those of you making changes and adding things to Bugzilla.

Overview:
We are moving to a “Pull” process for planning rather than a “Push”
process.  What this means is that we will start with an empty 2.6
release bucket and pull bugs and enhancements in that map to our top
priorities rather than push things out of a giant bucket.  We are hoping
this will help us start 2.6 with a very clear idea as to what we will
focus on and be much less overwhelming than pushing a giant snowball
through each release.

How does this effect you?
If you are pushing bugs/enhancements to the next release or adding new
bugs/enhancements for the next release you need to be aware of the
following:

-We have a M+ Future status that holds items that are important and need
to be addressed soon.  This bucket is pretty big.
-We have moved all 2.6 features and bugs to a 2.99 release.  This bucket
is a temporary hold for the items that didn’t make it into 2.5 and are
at the very top of our list for review to pull in.  We don’t want them
to get lost in the M+ Future bucket.  Once 2.6 planning is complete,
this 2.99 bucket will be empty and removed.
-If you are adding new bugs and enhancements that you believe should be
slotted for 2.6, please enter them as 2.99.
-If you are pushing anything from 2.5 to 2.6, please enter it as 2.99.

Please let me know if you have any questions about this.

Thanks,
Stephano