life sign & RFC

[Andre Heinecke]

Am Friday, 3. June 2011, 11:25:30 schrieb Thomas Friedrichsmeier:
> On Friday 03 June 2011, Patrick Spendrin wrote:
> > There are two things that are probably most interesting in the coming
> > months:
> > 1) a KDE 4.6 binary release
> > 2) the emerge git transition
> > 
> > The main question is of course in what order these should be done:
> > doing the release first, and switching to git later or switching to git
> > first and doing the release shortly after it.
> 
> Since the emerge transition will have to happen, eventually, I agree, it
> should go first. Since KDE 4.7 is less than two months away, according to
> the schedule, the thought of skipping KDE 4.6, if necessary, does not look
> too catastrophic.
Well imho we are right on Scedule since we only have the manpower atm to do 
one release per major release we should pick the last minor release of a major 
relese. So do 4.7 release when 4.8 comes out. And now do a 4.6 release at 
around the time 4.7 is released.
> A random thought (which probably just goes to show that I'm have not really
> grasped git, yet): If emerge is moved to git, would it become practical to
> clone from the KDE release branch(es), and to work on required patches
> directly inside that clone?
There is no such thing as KDE release branches :) Every repo tags it's release 
and they put together their tarballs to make up the KDE Software Compilation.
What Patrick is proposing is that we do a branch in emerge for each major 
release at the moment we have all parts of it building. So we can avoid 
regressions and incompatibilities and keep that branch stable (So that we can 
maybe do more then one release per major release :) ). I think this comes 
close to what you would like to do.


Regards,
Andre
-- 
Andre Heinecke |  ++49-541-335083-262  |  http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner