On Wed, Nov 10, 2010 at 7:50 AM, Stefan Schmidt <[email protected]> wrote: > Hello. > > December the 1th is our first release due. It will be the first in a, > hopefully > long, row. > > As it is the first release it will not be perfect, but we should try to make > it > a stable base anyway. Some steps that I think should help are listed below: > > - Stop pushing maybe problematic changes in the last 2 weeks. That gives you > one > week from now to get this in and fixed. So what is problematic? Changes to > bbclass files, the toolchain, core system services and changes that may > introduce runtime breakage should be avoided. There might be more. > If in doubt sent the patch to the ml and ask others what they think. > > - If you care about a specific machine, set of recipes or images start testing > them now in our testing-next branch. The plan was to base the release tag on > the testing-next branch. Or at least have it as fallback if master is broken. > > The testing matrix in the wiki will be used in the release tag in the same > way > it is used right now with the tested tag. Make sure the stuff you care is > listed there as working to show other they could use it in this release. > > - Try to take some hours in the last two weeks to get into bug fixing mode for > some moments and help OE forward to the release. check the ML for problem > reports and patches. Test, apply and mark them in patchwork as applied. > > I think that are the minimal steps we need to get a release out of the door. > More will come when learning from the first releases. > > Anyone willing to take the release mainatainer hat for this release? My time > is > rather occupied with other things the next weeks. :/ > It would be only for this release. Afterwards we can discuss if this should > be a > fixed position or newly assigned for any release. Such a person should keep > the > people motivated to fix some bugs, monitor the commit log for potential > problems > and discuss them and finally make the release tag in the meta data. > > Any takers?
I would be able to help here with the release > > regards > Stefan Schmidt > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
