I've pushed your builds. Speaking of grub legacy issue, I'd suggest to drop support for it from drakx.
So the list of bugs gets shorter thanks to Crispin work \o/ Wysłano z BlackBerry® w Orange -----Original Message----- From: Crispin Boylan <[email protected]> Sender: [email protected]: Fri, 04 Apr 2014 02:00:22 To: Cooker OpenMandriva<[email protected]> Reply-To: Cooker OpenMandriva <[email protected]> Subject: Re: [OM Cooker] 2014.0 release ok so 424 and 613 should be fixed. 422 has a fix in place for ldetect-lst which should resolve it. 562 i sent the latest snapshot of intel driver to build 2014 to see if it makes a difference, its worth having anyway. 307 - it depends what we want to do with this? basic operations work like installing grub2 bootloader on a simple system and there is good workaround (using grub-customizer/kcm-grub2). In terms of the grub graphics support we could fix it with some work, but should that be a blocker? it already notes that grub text mode works, and if you really want grub 1 then is it a massive deal that you can have the graphical one? as this was also an issue with 2013 i dont see why we should block on this. if someone could publish the builds 1743020 1743021 1743019 1743018 1742976 1742977 1742973 1742972 that should help! bed now. cheers cris. On 03/04/14 20:13, Crispin Boylan wrote: > i can take look at 422/4 and 613 > > On 03/04/14 17:05, Tomasz Paweł Gajc wrote: >> 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 ? >> >> >> > >
