On Monday 16 June 2008 18:12:08 Tom Albers wrote: > As we are approaching the final 4.1 release, I think we can think about the > schedule for 4.2 a bit and brainstorm about what we like and don't like. To > kick off the discussion, let me throw some ideas around. > > Because we became a lot more stable during the 4.1 development, I think we > can give it a bit more feature development in the next release. So I would > like to suggest to skip the alfa1 completely. Or if you insist, remove one > of the beta's and call that alfa. I just don't like the term alfa anymore, > as it does not seem to get tested, so I rather keep it with the two beta's.
One of the obvious differences is that alpha is source-only, IIRC. I do agree with your assessment that we'll need less time to stabilise, I support your suggestion. > Also, I think the two beta's should be closer together, like 2 or 3 weeks, > but this requires to reduce the time between tagging and releasing (say > tagging on Tuesday, release on Friday), else there is not much time for the > users to test the beta. > > So, all in all, that would be something like: > > August - early December: free hacking > ~15 December Release Beta 1 > ~3 January Release Beta 2 > ~17 January Release RC 1 > ~30 January Release Final From a quick look at the calendar, that looks good to me. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team