On 05/06/12 08:05, C wrote:
On Mon, Jun 4, 2012 at 11:10 PM, Sven Burmeister <sven.burmeister@gmx.net> wrote:
Am Montag, 4. Juni 2012, 22:54:51 schrieb Will Stephenson:
Do we create KR49 repo in advance and package tarballs there, do we use KUSC snapshots right up until release day, or do we use KDE released tarballs as KUSC sources? This would be my preferred technique, as this provides testing of prerelease milestones, rather than arbitrary snapshots from git. It also does not add additional load to the team or OBS. Last time KUSC was used to prepare a release this caused some confusion and Raymond did not like it since it breaks its actual purpose. I agree with that.
https://bugzilla.novell.com/show_bug.cgi?id=706813#c1
So I would suggest to simply create a KR49 repo and mediate via wiki, mailinglist etc. that this repo is (obviously) not stable until upstream releases 4.9.0 and the package names contain 4.9 and not 4.8.85 etc.
Alternatively KUSC could stay as it is. With RC1, packages can be moved to KR49 and everything missing gets added. My vote is for a KR49 repo that lives alongside the KR48 and 47 etc repos. Treat it the same as any other release. I'll be testing it on a live system as soon as it's available in the repo.
C. I'd like to see continuity and have Release49 also Thanks -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org