On Wed, Apr 18, 2012 at 03:47:47PM +0100, Richard Purdie wrote: > I thought I'd update everyone with the current 1.2 status. > > I'm going to branch master for release at this point. We've fixed a lot > of issues, I'm hoping the -rc4 build will be a good one. There are signs > there are some more minor issues around and bugs do keep getting opened. > These are still being investigated so we'll continue to let that happen. > Once we have a QA report for -rc4, we'll be in a better position to make > a call on how things are looking.
Does it mean that after creating branch, master will be open for postponed patches from ML and master-next or do you want to keep master as close to release branch as possible for some time (e.g. for those 1.2.1 fixes)? > If people don't have 1.2 issues to work on, I'd like people to start > looking at the bugs marked as 1.2.1. The reasoning here is simple, if we > do have to go to a -rc5 and the fixes are good enough, they might make > it into 1.2 (but no promises). We need to fix these issues in master and > for any 1.2.1 release anyway. I'd prefer people not to start working on > new features at this point but concentrate on improving the quality of > the release and fixing bugs. > > Cheers, > > Richard > > > > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
