[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: Fwd: Re: Fwd: KDE Frameworks Release Cycle
From:       Àlex Fiestas <afiestas () kde ! org>
Date:       2014-04-30 9:28:26
Message-ID: 2495377.J3FMTiSoeu () monsterbad
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 30 April 2014 10:41:30 Raymond Wooninck wrote:
> For openSUSE it will definitely bring problems as that we wouldn't be able
> to release any maintenance updates anymore for the KDE Desktop with this
> Release Cycle.  As Sune indicated, if KF5 is updated then the other
> components like Plasma-Next and the Applications needs to be rebuild. This
> is not the current setup of the openSUSE maintenance process, nor will this
> change just for KF5. This means that the only way for us is to start
> back-porting the bugfixes and release those as maintenance updates in order
> to provide a stable experience for our users.
> 
> If the other components would select a similar Release Cycle, then this
> would mean that the non-rolling distro's have to focus on a constant
> back-porting of bug-fixes and we would not provide our users with newer
> functionality.  This would eliminate the main goal that this Release Cycle
> is targeting (To introduce new functionality gradually) as that the main
> distributions would skip several KF5 releases before a new distribution
> version is released to the users.
This is not totally true, let me explain.

Having a release every month will allow distributions to package fresher 
versions of frameworks since we will virtually remove the synchronization 
problem.
As an example, Opensuse released 13.1 with KDE 4.8.5 iirc, which already had 
no support from upstream. You had to do that because our 6 months release 
schedule did not synchronize with yours. Having releases every month fixes the 
problem.

As for the backporting, you could use bugzilla (even via api) to get a list of 
everything that has been fixed, get the SHA and backport it automatically, that 
will ease a lot the process.

Also ideally, we should break with this tendency of "upstream/downstream" and 
you should become upstream, I would love to see opensuse (and others) keeping 
the release you picked maintained in a branch.
Even going further, you could (and I think you should) release point releases 
of that Frameworks version.

["signature.asc" (application/pgp-signature)]

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


[prev in list] [next in list] [prev in thread] [next in thread]