KDevelop beta3 release mess
Hi, it seems that some friendly helpful soul uploaded 0.9.93 tarballs that I put on upload.kde.org last weekend. At that time they weren't in the right place and Stephan Binner said I should move them to the pub/unstable/kdevelop/version place as soon as I got permission for that. Unfortunately I don't have permission yet (I sent my ssh keys to Dirk on wednesday, but haven't heard back from him). In the meantime it seems someone picked the tarballs and moved them instead of me. As I didn't know about that move, we've meanwhile retagged and wanted to merge two more crash fixes into the beta3 tag in svn. So now we have the tarballs on the ftp mirrors and they don't match the tag that has been created. Question is: Whats the best way to solve this - change the tag back and release a beta4 with a new tag once I have upload privileges? Or should I just replace the tarballs once I have upload privileges and notify kde-packagers, additionally to a dot-announcement, blog and news-item on our website? Andreas -- You'll never be the man your mother was! ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.2.5?
On Friday 29 May 2009 22:51:08 Sune Vuorela wrote: On Friday 29 May 2009 18:26:26 Allen Winter wrote: Howdy, Can we decide now if there will be a 4.2.5 release? If not, then that saves us some unneeded backporting work. Recall we stopped at 4.1.4. IMO we should stop at 4.2.4. Let's decide very soon and I'll communicate the decision to all developers. I would like to request something in between; still do some backports, but only in some special cases, at least until 4.3final is out. The special cases I could imagine would probably be something like: - grave bugs (dataloss too frequent crashes to make the app usable and such) - and maybe with a CCMAIL: kde-packager - gcc 4.4 (and such) compile fixes. - maybe other cases that I haven't yet thought of, but of a similar severity and impact. That way, distributions and others who cares can get blessed backport patches of the problems, which is kind of preferred. Yep, for grave problems, we might want to consider a 4.2.5, otherwise I think we should stop at 4.2.4 and fully concentrate on 4.3. -- 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: KDevelop beta3 release mess
Am Samstag 30 Mai 2009 11:45:31 schrieb Andreas Pakulat: Question is: Whats the best way to solve this - change the tag back and release a beta4 with a new tag once I have upload privileges? Or should I just replace the tarballs once I have upload privileges and notify kde-packagers One should never release different sources with the same name. Better call it 3.9.94 or 3.9.93.1. So there is no doubt which sources people are using when refering to a version number. -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pie...@jabber.archlinux.de WWW http://www.archlinux.de ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
