Re: KDE 3.5.8
On Thursday 04 October 2007 12:37 am, Eike Hein wrote: > Sebastian Kügler wrote: > > So are we going to ship 3.5.8 without flash 9 support and push out 3.5.9 > > as soon as that's implemented, or should we delay 3.5.8 until that's > > done? > > If we do delay 3.5.8 for the Flash thing, I guess > that would give Clarence that extra week he asked > for. I just finished all my commits to [branches/KDE/3.5/kdegraphics/kolourpaint] anyway :) ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
On Friday 21 September 2007 6:02 pm, Stephan Kulow wrote: > It's been a while since KDE 3.5.7 (released may 22nd) and a lot has changed > in the 3.5 branch since then, so I would like to release another service > pack. > > As the translators requested some clean up time, I suggest we go with > October 7th as tagging date and release on 15th. > > Any objections? If not, I let everyone know :) I have some changes that I haven't made yet on the 3.5 branch. I can try get them done by Oct 7 but if you can give me an extra week, that would be great. Clarence ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Hold Kopete out of KDE 4.0 final
On Tuesday 21 August 2007 17:15, Dirk Mueller wrote: > On Saturday, 11. August 2007, Clarence Dang wrote: > > I gave up keeping up with kdelibs and just have a branch that I merge > > into trunk/ every so often. > > Thats fine, but I think we're beyond that state now and it should be fine > to keep up with kdelibs, as the number of source incompatible changes > should be very minimal. If thats not the case, it would be better to speak > up than to hide in a private branch. Basically, the minimal changes that happen are enough to stop me from committing changes in the same file since I can't "svn update" the file, because I don't recompile kdelibs often. That will change though since it's getting closer to the release and I have to start testing that the app integrates with KDE. However, changes in the API that affect virtually every .cpp file I have, even when the "core library APIs are frozen solid", are very irritating. See kDebug. > BTW, I remember that there was once a rule in KDE SVN that in order to have > your application in the release cycle it should be primarly developed as > part of it, not in some private branch that is then tossed over os in one > swamp. Oops :) I'll fix that first thing tomorrow. I think kdelibs should be ok now. Clarence ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Hold Kopete out of KDE 4.0 final
On Friday 10 August 2007 10:53, Matt Rogers wrote: > I'm nearly 100% positive that we won't be able to do this during the beta > and RC period because on most weeks, there are roughly a dozen commits and > most of those are just to keep things in line with the kdelibs BIC changes > on Monday. We just need more time. I gave up keeping up with kdelibs and just have a branch that I merge into trunk/ every so often. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 3.5 Branch
On Tuesday 29 May 2007 20:10, Stephan Kulow wrote: > > What I'm suggesting is keep the 3.5 branch open for commits and when > > enough bugfixes have been done or X months have passed (where X is > > large), just do another release. However, don't open the 3.5 branch for > > adding more features again :) > > No more features, no more string changes, no more docu changes. That's my > idea. I'd basically like to be able to add a KMessageBox to KolourPaint, for when one clicks "File / Scan..." and libkscan is not installed. Currently, it just ignores the user's mouse click :) > Bug fixes are allowed and after some time we'll do another > maintenance update 3.5.8 - e.g. in september. I think this is a good idea, irrespective of whether string changes will be allowed. Thanks, Clarence ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 3.5 Branch
On Saturday 26 May 2007 09:28, Cyrille Berger wrote: > On Friday 25 May 2007, Clarence Dang wrote: > > However, KDE 4 is not going to be released soon and even after it's > > released, > > KDE4 isn't going to be released if people don't start to code for it. Sure. What I'm suggesting is keep the 3.5 branch open for commits and when enough bugfixes have been done or X months have passed (where X is large), just do another release. However, don't open the 3.5 branch for adding more features again :) Clarence ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 3.5 Branch
On Friday 25 May 2007 08:26, Allen Winter wrote: > On Thursday 24 May 2007 1:04:26 pm Stephan Kulow wrote: > > Am Thursday 24 May 2007 schrieb Allen Winter: > > > Is the 3.5 branch open for new i18n strings yet? > > > > I personally would leave the 3.5 branch frozen for the next couple of > > years. > > A fair answer. > But something we should discuss and decide as soon as possible. > > If 3.5.8 won't be released until 2009, then why bother with it? I think Coolo is saying that he doesn't want another 3.5 release, ever. > Let's tell the enterprise folks that the 3.5.x series is done, put > a lock on the branch repository, and move all our development > resources into trunk. However, KDE 4 is not going to be released soon and even after it's released, I think uptake will be slow. IMHO, it makes sense to do another 3.5 release sometime. > I have a few i18n string changes for 3.5.x in my to-do queue. > So I'd like to know how we plan to proceed with that branch. As I wrote before, I'd also like the string freeze to be lifted. Clarence ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 10 Days Until Next Milestone
On Wednesday 23 May 2007 00:12, Allen Winter wrote: > On Tuesday 22 May 2007 5:45:03 am Dirk Mueller wrote: > > On Tuesday, 22. May 2007, Aaron J. Seigo wrote: > > > > + The KDE main modules are frozen for new features. > > > > > > at this point, this is rediculously optimistic. there are three > > > realities ahead of us: > > > > I would s,new features,new applications, > > How about: > 1. 1 June is changed from new feature freeze to new application freeze > 2. We move the feature freeze to the start of the second beta (approx 25 > July). As this is also when the string freeze occurs > ? Yes, please. Else, I'll only have time to make KolourPaint work (it doesn't at the moment) - not implement any wishes. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
3.5 branch message freeze (Re: 3.5.7)
On Monday 14 May 2007 23:17, Stephan Kulow wrote: > I uploaded KDE 3.5.7 for the packagers to grab from stable/3.5.7/src - so > far untested. Given that 3.5.7 is tagged, can there now be a partial lift of the message and documentation freeze for the 3.5 branch? ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
