Update the Feature Plan!
Hi, Now would be a good time to update the feature plan on techbase. It's the document we use to distill the feature set for the next KDE Software Compilation release, a.k.a. 4.4 http://techbase.kde.org/Schedules/KDE4/4.4_Feature_Plan We want this document to reflect the improvements and additions that have gone into 4.4, please help with that. An incredible amount of work has gone into the KDE SC over the past months, and if that doesn't end up in the Feature Plan really soon now, it might not even get mentioning in the release announcement, visual guide, in reviews or by the user. The entries in the Feature Plan will be distilled into the Release Goals document, for a more human-readable compilation of important changes. Some words if you're unsure whether you should edit the document: - Please only edit features you worked on yourself. If you see something that's not updated correctly (for example a feature is actually in trunk right now, but still marked as FeatureInProgress,) but you aren't directly involved with the code, check with the developer named for the feature before you update this entry. - Adding new features that have not been committed to trunk before the hard freeze later today is not allowed, adding and updating features that are already in trunk is OK. - It's especially important to update the progress of the entry (from FeatureInProgress to FeatureDone), only green features can be announced. Your feature might still have bugs, that's OK and will be fixed -- you can mark it as green already. - The promo team can't constantly check what changed in the document, so if you change something after Friday, please send a note to kde-pr...@kde.org to make sure we can see what happened and don't write about stuff that - If you forgot to add a feature to the plan, but you have actually merged it into trunk/, please add it and mark it as FeatureDone - Items that are not marked as FeatureDone will be moved to the Feature Plan for 4.5 Thanks for your collaboration, it only costs 5 minutes and is important for documenting KDE's coolness :) -- 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
Re: KDE 4.4 Beta1 Tagging ahead
A Dimarts, 24 de novembre de 2009, Dirk Mueller va escriure: > Hi, > > according to the schedule, we're planning to tag KDE 4.4 Beta1 in two days. > Does that sound reasonable to everyone? Any blocking issues? I won't have time to check the l10n packages compile so if anyone can take care of it the better. Sorry. Albert > > Thanks, > Dirk > ___ > release-team mailing list > release-team@kde.org > https://mail.kde.org/mailman/listinfo/release-team > ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE3 maintenance
On Wednesday 18 November 2009 1:48:01 pm Timothy Pearson wrote: > Hi all, > > I have been maintaining and improving KDE3 for Ubuntu for a while now, and > have accumulated a massive set of patches that: > * Add lots of functionality > * Fix old bugs > * Allow compilation on new systems > > How would I go about including them into the KDE3 SVN/GIT, and then > generating a new 3.5.11 release? > Dear Release Teamers, I think we should put out a formal policy statement on 3.5. Here are some thoughts: + 3.5 is done and finished. there will be no more 3.5 releases + we will not allow commits into the 3.5 branch willy-nilly without the normal process of maintainer and/or peer review + we could create a 3.5 group on reviewboard for 3.5 patches to be collected. If the patch creator wants their patch into 3.5 SVN, then they need to work through normal maintainer/peer review channels to get the patch accepted and committed. + the kde-packagers mailing list will be notified if critical/security fixes for 3.5 become available. + perhaps we should tell kde-packagers about normal bugfixes and new features too?? + I have no idea what we should do about new i18n strings or updated docs that need translations. Aside: as part of our KDAB jobs, tmcguire and I create bugfixes and features for the kdepim 3.5 stuff in the separate kdepim/enterprise branches. We translate only into German, though. We forward port into trunk as permitted by the release schedule. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.4 Beta1 Tagging ahead
On Tue, 24 Nov 2009 13:26:22 +0100, Tom Albers wrote: > Op Tuesday 24 November 2009 11:17 schreef u: >> according to the schedule, we're planning to tag KDE 4.4 Beta1 in two >> days. >> Does that sound reasonable to everyone? Any blocking issues? > > It does mean we have tagging and releasing 4.3.4 and 4.4-beta1 at exactly > the same dates. > > Are we - packaging, promo/marketing - and the packagers up for that > challenge? It's probably not a big deal but I think it would be better to release the beta of 4.4 a few days after the 4.3.4 release. This we we could concentrate on the (maybe) last release of the 4.3 series and have a look at 4.4 afterwards. But I wont care that much if you are all fine with this. There is no real need to have packages of a beta at the day of release. Greetings, Pierre -- Pierre Schmitz, https://users.archlinux.de/~pierre ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.4 Beta1 Tagging ahead
On Tuesday 24 November 2009 13:26:22 Tom Albers wrote: > Op Tuesday 24 November 2009 11:17 schreef u: > > according to the schedule, we're planning to tag KDE 4.4 Beta1 in two > > days. Does that sound reasonable to everyone? Any blocking issues? > > It does mean we have tagging and releasing 4.3.4 and 4.4-beta1 at exactly > the same dates. > > Are we - packaging, promo/marketing - and the packagers up for that > challenge? >From a PR point of view, it should be OK. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.4 Beta1 Tagging ahead
Op Tuesday 24 November 2009 11:17 schreef u: > according to the schedule, we're planning to tag KDE 4.4 Beta1 in two days. > Does that sound reasonable to everyone? Any blocking issues? It does mean we have tagging and releasing 4.3.4 and 4.4-beta1 at exactly the same dates. Are we - packaging, promo/marketing - and the packagers up for that challenge? Best, Toma___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
KDE 4.4 Beta1 Tagging ahead
Hi, according to the schedule, we're planning to tag KDE 4.4 Beta1 in two days. Does that sound reasonable to everyone? Any blocking issues? Thanks, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 4.3.4?
On Friday 06 November 2009, Allen Winter wrote: > Done > http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule Thanks, I'll do that. Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
