Kdevelop Beta

[Andreas Pakulat]

Hi,

seems like our tagged and tarballe'd beta is not going to work very well on
multi-core/multi-processor machines due to parts of kdelibs being
non-threadsafe. We're working on a fix for that.

My problem is: The beta (3.9.90) has already been tagged and tarballe'd and
I'm not sure wether I should

a) merge the fix into the tag and ask dirk to replace the existing 3.9.90
tarballs
b) create a new 3.9.90.1 tag and get tarballs for that
c) create a 3.9.91 tag+tarballs.

Any suggestions? Ideally I'd do a), but as the tarballs are already on
ftp.kde.org I fear that people might already use them and not notice the
change when they're replaced. There's not been an announcement yet for the
beta, but that might still be a case.

Andreas

-- 
After your lover has gone you will still have PEANUT BUTTER!
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Kdevelop Beta

[Ingmar Vanhassel]

On Wed, Jan 28, 2009 at 02:25:51PM +0100, Andreas Pakulat wrote:
 a) merge the fix into the tag and ask dirk to replace the existing 3.9.90
 tarballs
 b) create a new 3.9.90.1 tag and get tarballs for that
 c) create a 3.9.91 tag+tarballs.
 
 Any suggestions? Ideally I'd do a), but as the tarballs are already on
 ftp.kde.org I fear that people might already use them and not notice the
 change when they're replaced. There's not been an announcement yet for the
 beta, but that might still be a case.
 
 Andreas

Making changes to already public tarballs is quite annoying for
packagers, so please don't do a).
A source distribution like Gentoo has Manifests for all downloaded
sources, specifically so that they catch switched tarballs before
they're installed on users' systems. They still do neeed to be downloaded
though, and it still causes hassle downstream.

Regards,
Ingmar

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team