Re: 10 Days Until Next Milestone
On Tuesday 22 May 2007 19:15:20 Tom Albers wrote: Other point, it was said that the agressive 4.0 release schedule was also to allow devs to developp and port applications for 4.x. What is the purpose without kdevelop and win/osx port? I would love a win/osx port and the people working on that seem to do a great job as far as i can see. Maybe they should be on this list? Although that would probably blur the focus, there will be no KDE 4.0 (in the sense of a desktop) for OSX or Windows, only applications. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Remember, God could only create the world in 6 days because he didn't have an established user base. 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: 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
Re: 10 Days Until Next Milestone
I propose a 25 July feature freeze for the sub-module which *really* need it, and keep the 1june for others, like kdegames, to focus on quality (usability, artwork...). At least, some KDE4.0 parts could give a polished image to 4.0, and some frozen dev could even help the latecomer sub-modules to be good enought. Since kdegames is in good shape, I guess they have time left for new features. So freezing the modules that are in good shape seems silly to me now that I think of it. On the other hand, without a module freeze we can not really shift our focus to stabilizing and really finishing all the games. There is always the temptation to rescue that game that did not make the cut for 4.0, and maybe adding that big feature that we know will not be fully matured in the next 150 days or so. I support Johann's idea, of only extending the feature freeze for the modules and apps that really need it. In our case, I guess the proposal made by Allen seems nice: 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. So each individual game could perhaps use this time to implement a missing feature, but we would not add new games to the module after June 1st. Regards, Mauricio Piacentini ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 10 Days Until Next Milestone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Kügler wrote: Maybe they should be on this list? Although that would probably blur the focus, there will be no KDE 4.0 (in the sense of a desktop) for OSX or Windows, only applications. I'm on the list (I work on the OSX packaging), just haven't had much to chime in with. :) My packaging stuff is mostly automated, as long as the tree builds, so I shouldn't have too much issue with getting a release put together. I did just start a new job and haven't had time to keep up with the state of KDE-on-OSX for the last month or so, so I don't know what the state of the build is, but I intend to do some catching up shortly. - -- Benjamin Reed a.k.a. Ranger Rick Fink, KDE, and Mac OS X development http://www.racoonfink.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGVC2JUu+jZtP2Zf4RApTaAKCa6tq0IbNmDZOaGfVEoDOa9tkSfgCeM92P meKSXP6kOQdM3V9xU7RtZYg= =TDt6 -END PGP SIGNATURE- ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 10 Days Until Next Milestone
On Tuesday 22 May 2007 10:12:45 am 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 ? Seems that we are in agreement. I will make the changes to our release docs on techbase and inform the developers. -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 10 Days Until Next Milestone
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 ? I'd be much more happy about letting another big feature slip in 4.0 at a later point though if we at least have it usable rather soon. We can do whatever we want. -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 10 Days Until Next Milestone
Op di 22 mei 2007 16:12 schreef u: 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 I think this is a good solution. That means two months from now for new features, and after that still 3 months left in freeze. I tried recompiling sunday evening, which failed so I had to do it yesterday, which of course also failed because it was monday. So I'm a bit biased here, but until which date do we keep this 'bic mondays'? Is that June 25 (beta1, full kdelibs api freeze). Do we want to keep it that way? In any case I think we should state it in the schedule more clearly. Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 10 Days Until Next Milestone
Op di 22 mei 2007 17:57 schreef u: For KDEgames, we are now in time, and i like to focus now on quality now, for example harmonize usability between games... But i'm not against a delay, because as aaron said, some KDE part still need work and time to mature or be ready (i'm thinking to plasma that seems starting to work, but need to mature more before to be freezed (aaron, fix me if i'm wrong), kcontrol that doesn't seems to do anything, kicker? ...). Because if we are keep actual date, with our current status, we risk to disappoint our users and be flamed. Even worse, put a regression/useless/buggy image on KDE 4.x, because it is hard to communicate that 4.0 and 4.x is not the same thing. Yes, that's true. We indicated already on this list that expectations for 4.0 should not be set to high. I think we should communicate that better. I don't know how though. Other point, it was said that the agressive 4.0 release schedule was also to allow devs to developp and port applications for 4.x. What is the purpose without kdevelop and win/osx port? I would love a win/osx port and the people working on that seem to do a great job as far as i can see. The point about kdevelop I dont understand. You can develop with kdevelop from kde3, non? The somewhat aggressive schedule was partly because I think we can keep the 4.0 short and do a 4.1 with new stuff relatively soon. I propose a 25 July feature freeze for the sub-module which *really* need it, and keep the 1june for others, like kdegames, to focus on quality (usability, artwork...). At least, some KDE4.0 parts could give a polished image to 4.0, and some frozen dev could even help the latecomer sub-modules to be good enought. Since kdegames is in good shape, I guess they have time left for new features. So freezing the modules that are in good shape seems silly to me now that I think of it. gr. Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 10 Days Until Next Milestone
On 22.05.07 19:15:20, Tom Albers wrote: Op di 22 mei 2007 17:57 schreef u: Other point, it was said that the agressive 4.0 release schedule was also to allow devs to developp and port applications for 4.x. What is the purpose without kdevelop and win/osx port? I would love a win/osx port and the people working on that seem to do a great job as far as i can see. Well, its still a far way until the win32 port is publicly usable, even though the installer already works relatively well. The point about kdevelop I dont understand. You can develop with kdevelop from kde3, non? Right and thats exactly what we kdevelop developers do. Its working pretty well and even if the 4.0 schedule would be move 2 months KDevelop probably wouldn't make it, its just too much work to do still and too few developers - as is the case for the rest of KDE :) (I wonder what will happen with KDE5 if KDE doesn't acquire tons of new developers) Andreas -- You have a deep appreciation of the arts and music. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
10 Days Until Next Milestone
Howdy, A gentle reminder... Milestone: Feature Freeze Date: 1 June 2007 Goals: + Any new application from kdereview must be in place in its KDE main module. + The KDE main modules are frozen for new features. + The focus is on stabilizing the applications, fixing bugs, and improving art and documentation. + The main module maintainers must indicate if they will follow the release schedule or will divert and not be released together with KDE 4.0. You might be surprised to hear that the pim team is leaning toward releasing kdepim with KDE 4.0. Our biggest concern at the moment is the lack of progress with korganizer. But we are optimistic. How are the other modules doing? Are there modules that are considering not releasing with 4.0? -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
