It looks like most the bugs were fixed and/or severity lowered, and also no big changes, so I have no qualms. On Apr 4, 2014 4:29 AM, "Tomasz Paweł Gajc" <[email protected]> wrote:
> Please give your voice for accept or refuse for RC1 and GA re-schedule. > > According to original plan today is RC1 release, which won't happen today. > We need to release announcement on this with new dates and with reason why > delay. > > > Wysłano z BlackBerry® w Orange > > -----Original Message----- > From: Tomasz Paweł Gajc <[email protected]> > Date: Thu, 03 Apr 2014 18:05:30 > To: <[email protected]>; <[email protected]> > Subject: 2014.0 release > > > We are currently somewhere between beta and RC1 stage. > Tommorow RC1 should be released and GA released is cheduled for 2014-04-18. > > Current situation is not so bright, as RC1 and GA release dates are > threatened > with delay. > > We need to find a proper solution for next releases, because as you may > noticed OMA will be representing our comminity on three big events which > are > starting on may: > > 1. LinuxTag > 2.FISL > 3.SolutionsLinux > > Without a released product it would be hard to get any impressions, and > doing > this with old release is just a step back. > > Speaking of bugs that were marked blockers: > 422 > 424 > 562 > 614/307 > 613 > > Some of them are hard to debug, others are just painfull for users. One > thing > is common for them, they are quite old and either bugreporters are trying > to > provide proper debug/logs/etc that will help maintainers to figure out any > solution or maintainers are lazy/busy which finally means these bugs have > small chance of being fixed ASAP. We failed with some of them for alpha2, > beta > and now with RC1. > > In my opinion proper solution goes like that: > > 1. Call for volunteers who will focus only on one bug > 2. Time for fixing this bug is no more than a week (2014-04-07 till > 2014-04-13) > 3. During this time if a bug will still left unresolved then hereby we > sorry > for oursleves > 4. We pospone these bugs as a blockers for next release > 5. RC1 release date moves to GA (2014-04-18) > 6. RC1 iso is going to be build for QA on 2014-03-13 > 7. GA release date moved to 2014-05-01 > 8. GA iso must be build for QA on 2014-04-21 > > The plan is build as a compromise between Cooker Team and QA - delay and > try > to fix bug in return GO for RC1 and GA. > > So who is ready to take those bugs and squash them, please respond timm > tommorow ? > > -- > Cheers > TPG > _______________________________________________ > OM-QA mailing list > [email protected] > http://ml.openmandriva.org/listinfo.cgi/om-qa-openmandriva.org >
