On 2014-04-03 18:05, Tomasz Paweł Gajc wrote:
We are currently somewhere between beta and RC1 stage.
Tommorow RC1 should be released and GA released is scheduled 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:
Yes -- we should definitely have a GA release ready (and copied to a
couple of our USB sticks) before the events. That doesn't give us much
room for delays.
Without a released product it would be hard to get any impressions, and
doing
this with old release is just a step back.
Yes. We should definitely not use the old release. Even the beta we have
right now is much much better.
Speaking of bugs that were marked blockers:
422
I still say messing with Xorg.conf these days in general is wrong,
modern Xorg is designed to detect everything by itself. XFdrake is evil
and has to go.
The only legit use I can see that it has is switching to evil non-free
drivers. We may want to use a much simpler tool for just that...
424
seems to be fixed
562
This is a real problem, but so hard to debug that we probably can't fix
it in time. There's so many components involved there that it's even
complicated to figure out what may be at fault.
We should try to fix this, but not make it a blocker for the release. We
can always release an update to fix it as soon as we can.
614/307
I've fixed this by replacing the bootloader config stuff in drakconf
with a call to kcm-grub2. Probably some fans of never changing anything
will scream, but this should be good enough to fix the problem.
613
This seems to be fixed.
Additionally, there's good news on the UEFI front - I've had a
successful boot using UEFI last night (haven't been able to build a new
iso because of random abf breakage since, though).
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
That sounds like a reasonable plan to me.
So who is ready to take those bugs and squash them, please respond timm
tommorow ?
I'll be around...
ttyl
bero
