On March 6, 2007, Benjamin Reed wrote: > Cornelius Schumacher wrote: > > This would delay the release. I don't think aKademy is that important to > > the release. If a group feels that they need a personal meeting to > > facilitate getting ready for the release we can organize smaller focused > > developer meetings. The e.V. is able to help with that, if needed. > > I don't know that that would be the issue so much as, it seems like a > lot of innovative (dare I say, synergistic? hehe) group hacking goes on > during akademy, it would be a shame for the 4.0 API to be frozen before > giving those things a chance to happen...
as Stephan notes, we probably don't need to get BIC perfect for 4.0. i do think we need to settle back into BC for releases in KDE4, e.g. 4.1 on, but we don't absolutely need to freeze ourselves into 4.0's libs. april 2, if announced this week, gives people ~3 weeks to get things together. we may want to give a full month from the announcement on kde-core-devel just to give people ample time, but otherwise, i think the schedule looks good. what we should be using akademy for is stabilizing and polishing 4.0, not more framework diddling. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
pgpkpQ814ZwRL.pgp
Description: PGP signature
_______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team