Re: kdevplatform/kdevelop branching?
On 06.01.09 23:02:55, Dirk Mueller wrote: > > Hi, > > We need to decide what to do with kdevplatform and kdevelop. At the moment it > is under trunk/KDE, which means that it was copied also to /branches/KDE/4.2 > > a) does kdevelop/kdevplatform stay on a seperate schedule? Yes. > b) if so, branching should be done later and outside /branches/KDE/4.2, > correct? Right. I'll do the branching once the code is ready for its rc. Leaves one question: We wanted to release beta1 with KDE 4.2.0, how do we best go about this? Do it the same way as done with the beta's, i.e. you fetch trunk/kdevplatform+trunk/kdevelop into the rc tags and put tarballs into the unstable/ directory? Or should we do this ourselves now that 4.2 is in its own branch? Andreas -- You will be given a post of trust and responsibility. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.1.4 (try #1) uploaded
On Tue, Jan 6, 2009 at 11:01 PM, Dirk Mueller wrote: > > Hi, > > I just finished uploading the initial set of KDE 4.1.4 tarballs. Please let me > know of any issues. Planned announcement is next week Tuesday. kdelibs' content: documentation eu is it mr README regards, Harald ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
kdevplatform/kdevelop branching?
Hi, We need to decide what to do with kdevplatform and kdevelop. At the moment it is under trunk/KDE, which means that it was copied also to /branches/KDE/4.2 a) does kdevelop/kdevplatform stay on a seperate schedule? b) if so, branching should be done later and outside /branches/KDE/4.2, correct? Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
KDE 4.1.4 (try #1) uploaded
Hi, I just finished uploading the initial set of KDE 4.1.4 tarballs. Please let me know of any issues. Planned announcement is next week Tuesday. kde-l10n tarballs are still being generated, I'll upload them tomorrow morning. Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.2 branched
On Tuesday 06 January 2009, Dirk Mueller wrote: > Hi, > > on our road towards KDE 4.2 RC1 tagging (tonight), I've just branched KDE > 4.2 into /branches/KDE/4.2 from trunk/KDE svn revision 906698 (yes, I > couldn't wait for 906700). Is it ok to make all modules in the 4.2 branch require at least version 4.1.96 of kdelibs ? Or should they stay working with trunk from e.g. last week ? Should we increase the version in trunk now to 4.2.80 or something ? I'll do that if you agree. Alex ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.2 branched
On Tuesday 06 January 2009 18:55:54 Dirk Mueller wrote: > on our road towards KDE 4.2 RC1 tagging (tonight), I've just branched KDE > 4.2 into /branches/KDE/4.2 from trunk/KDE svn revision 906698 (yes, I > couldn't wait for 906700). > > Any commit after 906698 that is intended to be part of KDE 4.2 has to be > backported to /branches/KDE/4.2 > > Please note that branches/KDE/4.2 is feature frozen at this point and heads > towards KDE 4.2 RC1 (tagged today 23:59 UTC). > > Translations are currently taken from branches/KDE/4.2 and merged into > trunk/l10n-kde4. the branching of l10n-kde4 will happen with KDE 4.2.0 > release, so no change for translators for now. And in case it wasn't clear: This means that trunk/ is open for feature development again, though I would like to remind everybody to concentrate on making 4.2 kick ass first, and to not forget to backport important fixes to the 4.2 branch. Personally, I felt that the (to my feeling) rather long freeze period was a success as we've stabilized KDE4 a lot and as such now have a wonderful basis for future work. -- 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
KDE 4.2 branched
Hi, on our road towards KDE 4.2 RC1 tagging (tonight), I've just branched KDE 4.2 into /branches/KDE/4.2 from trunk/KDE svn revision 906698 (yes, I couldn't wait for 906700). Any commit after 906698 that is intended to be part of KDE 4.2 has to be backported to /branches/KDE/4.2 Please note that branches/KDE/4.2 is feature frozen at this point and heads towards KDE 4.2 RC1 (tagged today 23:59 UTC). Translations are currently taken from branches/KDE/4.2 and merged into trunk/l10n-kde4. the branching of l10n-kde4 will happen with KDE 4.2.0 release, so no change for translators for now. Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
