kdesdk migration

Jeremy Whiting jpwhiting at kde.org
Tue Dec 11 01:21:24 UTC 2012


Yep, no worries, I wont rush it.  The rules have been in the works for
about a year by now :)  A couple of motivated students of Tomaz have
checked them and added to them recently and I think it's all in place.
I'll do an initial conversion to scratch tonight and let all the
application maintainers check the result then do the real migration this
weekend if all is well probably.


On Mon, Dec 10, 2012 at 4:24 PM, Albert Astals Cid <aacid at kde.org> wrote:

> El Dilluns, 10 de desembre de 2012, a les 13:28:45, Jeremy Whiting va
> escriure:
> > Hello release team guys,
> >
> > In preparing the kdesdk rules for migrating kdesdk from svn to git
> Neat!
> > I'm
> > wondering what the best time would be to migrate.  I see 4.10 beta is to
> be
> > tagged next week,
> Your calendar is wrong, we are tagging RC1 next week
> http://techbase.kde.org/Schedules/KDE4/4.10_Release_Schedule#Tuesday.2C_December_18.2C_2012:_KDE_SC_4.10_Release_Candidate_1_Tagging
> > would it be best to get the migration done before then?
> > or wait until after 4.10 is finally released towards the end of January?
> If you can get it before RC1, it works for me, after RC1 I think that
> changing
> the package layout it is too much (since it would not be a Release
> Candidate
> anymore :D).
> But please *do not rush* the job, writing svn->git rules is hard and in
> some
> cases we had to revert the migrations because the job was incomplete. Make
> sure you contact the appropiate people so you get proper review.
> Cheers,
>   Albert
> > Either way I'll do a set of conversions into scratch tonight for the
> > application maintainers to check.
> >
> > thanks,
> > Jeremy
> _______________________________________________
> release-team mailing list
> release-team at kde.org
> https://mail.kde.org/mailman/listinfo/release-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20121210/5e016151/attachment.html>

More information about the release-team mailing list