Re: KDE 3.5.8 uploaded
I added a exit to the .php file because we don't want sites to start linking there before we do the actual release If you want to have a look at the changelog you can see http://www.tsdgeos.com/unofficial/changelog.html Albert --- Andras Mantia escribió: On Tuesday 09 October 2007, Stephan Kulow wrote: Albert was already so nice to create http://www.kde.org/announcements/changelogs/changelog3_5_7to3_5_8.php and we added kdevelop 3.5 to the mix, so there is something to announce. At this time the document is empty. It looks OK in the subversion repository though. Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
KDE 3.5.8 uploaded
Hi! I tagged, packaged and uploaded KDE 3.5.8 to be grabbed by packagers. I would like to know if there is some spare time left to adapt the 3.5.7 release announcement :) I don't think we want to take away any of the shine from the 7th KConfig rewrite, but I guess some people might still be interested in bugs being fixed. Albert was already so nice to create http://www.kde.org/announcements/changelogs/changelog3_5_7to3_5_8.php and we added kdevelop 3.5 to the mix, so there is something to announce. Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8 uploaded
On Tuesday 09 October 2007 08:51:31 Stephan Kulow wrote: I tagged, packaged and uploaded KDE 3.5.8 to be grabbed by packagers. I would like to know if there is some spare time left to adapt the 3.5.7 release announcement :) I'll take care of the announcement. When do you want to release, maybe on Tuesday next week? (That'll give the translators some time to translate the announcement.) I don't think we want to take away any of the shine from the 7th KConfig rewrite, but I guess some people might still be interested in bugs being fixed. Hehe :-) Albert was already so nice to create http://www.kde.org/announcements/changelogs/changelog3_5_7to3_5_8.php and we added kdevelop 3.5 to the mix, so there is something to announce. -- 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 3.5.8 uploaded
A Dimarts 09 Octubre 2007, Andras Mantia va escriure: On Tuesday 09 October 2007, Albert Astals Cid wrote: It's the typical release procedure, we always protect pages until we do the real release. It is not typical for KDE. This is really the first time I see the changelog page protected in KDE (well, I'm not sure for 3.5.7, but before that for many releases I updated regularly the changelog files and it was never protected). I just protected yesterday, that is protect when the release is near. The files are read/writable for anybody having an account and readable for everybody else, so what is the real benefit of tryting to hide it, I don't know. I already explained, remove the confusion caused when smart sites link to the changelog and say kde has been removed. But as you say, they are read/write for anyone, feel free to remove the exit. What if somebody links there? They will see the progress of KDE, that's all. BTW http://websvn.kde.org/trunk/www/sites/www/announcements/announce-3.5.6.php?r1=626589r2=627062 http://websvn.kde.org/trunk/www/sites/www/announcements/announce-3.5.7.php?r1=667120r2=667267 http://websvn.kde.org/trunk/www/sites/www/announcements/changelogs/changelog3_5_6to3_5_7.php?r1=665435r2=667267 Albert Andras ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8 uploaded
On Tuesday 09 October 2007, Albert Astals Cid wrote: I already explained, remove the confusion caused when smart sites link to the changelog and say kde has been removed. But as you say, they are read/write for anyone, feel free to remove the exit. I did so. What if somebody links there? They will see the progress of KDE, that's all. BTW http://websvn.kde.org/trunk/www/sites/www/announcements/announce-3.5. 6.php?r1=626589r2=627062 http://websvn.kde.org/trunk/www/sites/www/announcements/announce-3.5. 7.php?r1=667120r2=667267 I wasn't talking about the announcement (that indeed could introduce confusion). http://websvn.kde.org/trunk/www/sites/www/announcements/changelogs/ch angelog3_5_6to3_5_7.php?r1=665435r2=667267 And I said I don't know how it was for 3.5.7. But you can check the logs for previous versions. ;) Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org 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 3.5.8
On Friday 05 October 2007, Stephan Kulow wrote: Yep, so its better to act surprised after Adobe does a public beta for 3 months. ;) And who acts suprised we're going to release 3.5.8 after 5 months? I didn't act surprised - I've in fact talked to Koos a few weeks ago already about this topic. Its just that nothing has happened yet. Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
Op ma 1 okt 2007 12:53 schreef u: Actually my point was that it should matter if a module is in toplevel directory of KDE or under extragear, what it matters is what policy it follows. KDevelop is one, KOffice is another. Do you want to move KOffice under extragear as well? First, KOffice has allways had his own release schedule separated from KDE. I guess for historical reason it's located as a top svn directory, if it was started today it would probably end up in extragear/office. But that's not the problem. I'm tempted to propose it ;-) Second, as I understand, Tom's point is not about the exact location of KDevelop in svn, it's about wether a module (or an application) is _allways_ released at the same time than KDE or not. If it is, then it can be in the main module. If it's not the case, then it would be easier for the release team to have it in extragear. In KDE4 extragear module will allways be released with KDE4 but including a version tagged by their maintainers, which might or might not be the same tagging date as the one of KDE4. Spot on! Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
Am Freitag 05 Oktober 2007 schrieb Dirk Mueller: On Thursday, 4. October 2007, Rex Dieter wrote: +1, imo, flash-fix is post 3.5.8 territory. Besides, afaik, this only affect the flash beta, not the stable/released version (9.0.48.0 atm). Yep, so its better to act surprised after Adobe does a public beta for 3 months. ;) And who acts suprised we're going to release 3.5.8 after 5 months? Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
Stephan Kulow wrote: Am Mittwoch 03 Oktober 2007 schrieb Sebastian Kügler: 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? Delaying 3.5.8 would be a big mistake +1, imo, flash-fix is post 3.5.8 territory. Besides, afaik, this only affect the flash beta, not the stable/released version (9.0.48.0 atm). -- Rex ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
On Thursday, 4. October 2007, Rex Dieter wrote: +1, imo, flash-fix is post 3.5.8 territory. Besides, afaik, this only affect the flash beta, not the stable/released version (9.0.48.0 atm). Yep, so its better to act surprised after Adobe does a public beta for 3 months. ;) Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
On Wednesday, 3. October 2007, Stephan Kulow wrote: I don't think it makes sense to release KDE 3.5.8 without working flash support, this has to be fixed first. Without what? flash support. Flashplayer has moved to XEmbed, nspluginviewer no longer works. Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
Am Mittwoch 03 Oktober 2007 schrieb Dirk Mueller: On Wednesday, 3. October 2007, Stephan Kulow wrote: I don't think it makes sense to release KDE 3.5.8 without working flash support, this has to be fixed first. Without what? flash support. Flashplayer has moved to XEmbed, nspluginviewer no longer works. Why does it work with 3.5.7 then? Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
Sebastian Kügler wrote: It doesn't. The old flash plugin does, the new flash plugin uses different technologies. So the point really is if we want / can release an updated KDE that has konqueror supporting the new flash plugin. Notably Koos of KMPlayer fame has added support for loading the XEmbed-style Beta Flash plugin to the KMPlayer KPart, so Konqueror can current- ly get at that Flash version through KMPlayer: http://www.kde-apps.org/content/show.php?content=10004 That may not be good enough to consider this blocker done for, but maybe his code can be adapted for 3.5.8. -- Regards, Eike Hein, [EMAIL PROTECTED] ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
On Wednesday 03 October 2007 15:53:21 Dirk Mueller wrote: On Wednesday, 3. October 2007, Eike Hein wrote: http://www.kde-apps.org/content/show.php?content=10004 That may not be good enough to consider this blocker done for, but maybe his code can be adapted for 3.5.8. Indeed, this was my plan (to adapt his embedding code for nspluginviewer) or move the code into a separate project into kdebase. 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? -- 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 3.5.8
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. -- Regards, Eike Hein, [EMAIL PROTECTED] ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
Am Montag 01 Oktober 2007 schrieb Andreas Pakulat: On 26.09.07 13:50:51, Andreas Pakulat wrote: On 21.09.07 10:02:43, Stephan Kulow wrote: Hi! 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 :) About KDevelop :) We recently moved to a branch (please no flames anymore, got enough of that already) and some of us developers would like to merge that branch back into KDE/3.5 before this release. The thing is, that a) that branch has new strings (I already changed scripty to update from the branch instead of KDE/3.5 a few weeks ago) b) it has new features I know 3.5 is in full freeze, thats why I'm asking wether we are allowed to move back at all. If not, please don't release the kdevelop module from KDE/3.5 when releasing KDE 3.5.8. We will do a release of KDevelop 3.5.0 at the time of the KDE release ourselves in that case. (Should kdevelop 3.4.1 be removed from KDE/3.5 in that case?) Would somebody please give us (the kdevelop team) at least any response? (no I will not do the move unless it is approved, but still its kinda rude to get no answer whatsoever) Oops, I overlooked the mail somehow. I was aware of the issue though. So the thing is: if you already changed scripty, then merging back is the safer variant. Otherwise 3.5.8's kde-i18n might create a more untranslated kdevelop than with the branch. I wonder why you guys don't ask forehand. Now all I could do is remove kdevelop from kde-i18n and 3.5.8 completely ;( But backmerge, I don't care. The idea in freezing KDE 3.5 was to keep people on KDE4 development, if it doesn't work for kdevelop and the development team is using dirty tricks to circumvent the freeze, I can't help. Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
On Monday 01 October 2007, Tom Albers wrote: I don't want want to flame as you request, but could you consider moving kdevelop to extragear-sdk? In that case you can determine for each release if you want to be part of it. We will just tag what is in there at that moment so you can swap around whatever you see fit. There is no need to move it anywhere, it just about deciding if KDevelop should or not be released together with a certain version of KDE. If the KDevelop developers tell in *advance* that we added new string, features, please don't include the current kdevelop module in KDE 3.5.8, I don't think anybody will complain. The same the other way around, if they say that the only changes compared to the last released version are bugfixes, it can be included in the upcoming KDE pack. Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org 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 3.5.8
Am Montag 01 Oktober 2007 schrieb Andras Mantia: On Monday 01 October 2007, Tom Albers wrote: I don't want want to flame as you request, but could you consider moving kdevelop to extragear-sdk? In that case you can determine for each release if you want to be part of it. We will just tag what is in there at that moment so you can swap around whatever you see fit. There is no need to move it anywhere, it just about deciding if KDevelop should or not be released together with a certain version of KDE. If the KDevelop developers tell in *advance* that we added new string, features, please don't include the current kdevelop module in KDE 3.5.8, I don't think anybody will complain. The same the other way around, if they say that the only changes compared to the last released version are bugfixes, it can be included in the upcoming KDE pack. No. There _is_ a problem. And that is that KDE module's translations are packaged in kde-i18n. So you can't simply translate kdevelop 7.0 in KDE 3.5's kde-i18n and then expect a working 3.5.8 to be released Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
At Monday 01 October 2007 10:09, you wrote: On Monday 01 October 2007, Tom Albers wrote: I don't want want to flame as you request, but could you consider moving kdevelop to extragear-sdk? In that case you can determine for each release if you want to be part of it. We will just tag what is in there at that moment so you can swap around whatever you see fit. There is no need to move it anywhere, it just about deciding if KDevelop should or not be released together with a certain version of KDE. If the KDevelop developers tell in *advance* that we added new string, features, please don't include the current kdevelop module in KDE 3.5.8, I don't think anybody will complain. The same the other way around, if they say that the only changes compared to the last released version are bugfixes, it can be included in the upcoming KDE pack. For the next release we will make releases of extragear application at the same time the other modules are released. So your workflow fits way better in extragear (release on reqest at the same time as KDE) then a main module (always release). Toma -- http://www.mailody.net___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
On Monday 01 October 2007, Stephan Kulow wrote: Am Montag 01 Oktober 2007 schrieb Andras Mantia: On Monday 01 October 2007, Tom Albers wrote: I don't want want to flame as you request, but could you consider moving kdevelop to extragear-sdk? In that case you can determine for each release if you want to be part of it. We will just tag what is in there at that moment so you can swap around whatever you see fit. There is no need to move it anywhere, it just about deciding if KDevelop should or not be released together with a certain version of KDE. If the KDevelop developers tell in *advance* that we added new string, features, please don't include the current kdevelop module in KDE 3.5.8, I don't think anybody will complain. The same the other way around, if they say that the only changes compared to the last released version are bugfixes, it can be included in the upcoming KDE pack. No. There _is_ a problem. And that is that KDE module's translations are packaged in kde-i18n. So you can't simply translate kdevelop 7.0 in KDE 3.5's kde-i18n and then expect a working 3.5.8 to be released So this would mean a need in scripty script each time a module (be it kdevelop, koffice or whatever) is packaged together or separately? Can't the kde-i18n packages be created per module? So let's say KDE 4.0 has kdelibs, kdepimlibs, kdebase and kdegames. There will be kde-i18n-kdelibs, kde-i18n-kdepimlibs and so on. If KDE 4.1 has one more module, the corresponding kde-i18n-* is also released. If a module is not released together with 4.2, the i18n module for that is not released. And to avoid chaos: those module maintainers whose modules will be added/removed from the next release should inform (and ask permission) the release team and translation teams well in advance. If this was discussed on kde-i18n list, I just shut up now. :) Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org 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 3.5.8
On 01.10.07 09:40:57, Tom Albers wrote: At Monday 01 October 2007 02:17, you wrote: We recently moved to a branch (please no flames anymore, got enough of that already) and some of us developers would like to merge that branch back into KDE/3.5 before this release. The thing is, that I don't want want to flame as you request, but could you consider moving kdevelop to extragear-sdk? In that case you can determine for each release if you want to be part of it. We will just tag what is in there at that moment so you can swap around whatever you see fit. Again, just an idea, please don't kill me. Thats exactly what I want as well, for KDevelop4. KDevelop3 development might get an occasional change here or there but is also considered abdandoned. This recent move out/change scripty was caused by two things: a) a lot of changes that we had lying on our harddisks but couldn't share with the community due to full freeze b) the release team not answering our request for freeze exception Anyway, as Stephan said he doesn't care about keeping the full freeze I will merge back today. Andreas -- You will triumph over your enemy. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
Am Montag 01 Oktober 2007 schrieb Andras Mantia: So this would mean a need in scripty script each time a module (be it kdevelop, koffice or whatever) is packaged together or separately? Can't the kde-i18n packages be created per module? So let's say KDE 4.0 has kdelibs, kdepimlibs, kdebase and kdegames. There will be kde-i18n-kdelibs, kde-i18n-kdepimlibs and so on. If KDE 4.1 has one more module, the corresponding kde-i18n-* is also released. If a module is not released together with 4.2, the i18n module for that is not released. And to avoid chaos: those module maintainers whose modules will be added/removed from the next release should inform (and ask permission) the release team and translation teams well in advance. This might work for kdevelop perhaps. But e.g. not for the kopete case, that jumps back in and out. The way we package translations is a compromise and the condition is that we move into one direction, otherwise we create a mess. If this is should be more flexible for KDE 4, we need to do the split a massive one and package applications including _all_ translations (as GNOME basically does). Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
Actually my point was that it should matter if a module is in toplevel directory of KDE or under extragear, what it matters is what policy it follows. KDevelop is one, KOffice is another. Do you want to move KOffice under extragear as well? First, KOffice has allways had his own release schedule separated from KDE. I guess for historical reason it's located as a top svn directory, if it was started today it would probably end up in extragear/office. But that's not the problem. Second, as I understand, Tom's point is not about the exact location of KDevelop in svn, it's about wether a module (or an application) is _allways_ released at the same time than KDE or not. If it is, then it can be in the main module. If it's not the case, then it would be easier for the release team to have it in extragear. In KDE4 extragear module will allways be released with KDE4 but including a version tagged by their maintainers, which might or might not be the same tagging date as the one of KDE4. -- Cyrille Berger ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Sebastian, Wasn't sure if there was a point - but figured it might be better to point it out, rather than going oh, surprise!. Had it been earlier, we would have grabbed a freeze exception for it - it's certainly important enough. Good luck on KDE 4 - it's starting to look good! Hobbsee Sebastian Kügler wrote: Hi Sarah, On Wednesday 26 September 2007 07:03:21 Sarah Hobbs wrote: Just a FYI, this will almost definitely miss Kubuntu Gutsy - but we're aware that you guys don't want to push it earlier, either. (https://wiki.ubuntu.com/GutsyReleaseSchedule) It misses Gutsy by about two months (assuming that the Feature Freeze is applying here). So I don't really see a point in pointing this out -- 3.5.8 might miss other distro's releases as well (prominently OpenSuse 10.3, I suppose), we could have released it earlier, but there was no pressing reason to do so. For the 3.x series we're in maintenance mode, and only flushing out bugfixes that went into the codebase every so often, and that time span is increasing. We do understand that it's nice to keep releasing the stable version, but we really need to focus on getting KDE 4.0 release ready. Working too much on the 3.5 branch steals focus there. Cheers, ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+19M7/o1b30rzoURAtssAKDeTorJRkryhUv4zHyffK0oXWNGVACfdYBH LrS6qwTnJHF5ungRkOqfUR0= =OQ+q -END PGP SIGNATURE- ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just a FYI, this will almost definitely miss Kubuntu Gutsy - but we're aware that you guys don't want to push it earlier, either. (https://wiki.ubuntu.com/GutsyReleaseSchedule) Hobbsee Stephan Kulow wrote: Hi! 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 :) Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+egZ7/o1b30rzoURAhEDAKCfPXr9OH5ygaKiy6oEEBJh+4F2dQCg0rmr X89P8YLV5C0EundIWey2Dmk= =dXI+ -END PGP SIGNATURE- ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
On 21.09.07 10:02:43, Stephan Kulow wrote: Hi! 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 :) About KDevelop :) We recently moved to a branch (please no flames anymore, got enough of that already) and some of us developers would like to merge that branch back into KDE/3.5 before this release. The thing is, that a) that branch has new strings (I already changed scripty to update from the branch instead of KDE/3.5 a few weeks ago) b) it has new features I know 3.5 is in full freeze, thats why I'm asking wether we are allowed to move back at all. If not, please don't release the kdevelop module from KDE/3.5 when releasing KDE 3.5.8. We will do a release of KDevelop 3.5.0 at the time of the KDE release ourselves in that case. (Should kdevelop 3.4.1 be removed from KDE/3.5 in that case?) Andreas -- You will give someone a piece of your mind, which you can ill afford. ___ 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: KDE 3.5.8
Am Samstag 22 September 2007 schrieb Clarence Dang: 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. No, we're way too late anyway. Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
On Sunday 23 September 2007, Albert Astals Cid wrote: A Divendres 21 Setembre 2007, Stephan Kulow va escriure: Hi! 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 :) As a matter of saying i agree i created the changelog page up to r715588 http://www.kde.org/announcements/changelogs/changelog3_5_7to3_5_8.php Nice! There's a bug with the core libs changes though. The first bugfix says See SVN commit 669594. and this is a link to http://websvn.kde.org/branches/KDE/3.5/kdelibs/core libs/?rev=669594view=rev which doesn't exist (see the core libs in there :) Too much automation in the xml-php transformation it seems? -- David Faure, [EMAIL PROTECTED], sponsored by Trolltech to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
A Dilluns 24 Setembre 2007, David Faure va escriure: On Sunday 23 September 2007, Albert Astals Cid wrote: A Divendres 21 Setembre 2007, Stephan Kulow va escriure: Hi! 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 :) As a matter of saying i agree i created the changelog page up to r715588 http://www.kde.org/announcements/changelogs/changelog3_5_7to3_5_8.php Nice! There's a bug with the core libs changes though. The first bugfix says See SVN commit 669594. and this is a link to http://websvn.kde.org/branches/KDE/3.5/kdelibs/core libs/?rev=669594view=rev which doesn't exist (see the core libs in there :) Too much automation in the xml-php transformation it seems? Yeah, it seems i tried to be too much smart, i'll fix it when i have time. Thanks for pointing out. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 3.5.8
A Divendres 21 Setembre 2007, Stephan Kulow va escriure: Hi! 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 :) As a matter of saying i agree i created the changelog page up to r715588 http://www.kde.org/announcements/changelogs/changelog3_5_7to3_5_8.php Albert P.S: We should hide it in few time or pages will start linking to it saying 3.5.8 is out, though. Greetings, Stephan ___ 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
KDE 3.5.8
Hi! 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 :) Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
