Project Neon and stable branches
david at davidedmundson.co.uk
Tue Feb 12 23:15:22 UTC 2013
I have a question to project-neon devs, I'm not sure who's currently
leading this, so I'm spamming the mailing list. (sorry everyone else)
I'm on a purely research gathering mission for a thread in KDE, and
this isn't a formal request or anything.
On a scale of 1 to ridiculous, how much effort would it be to make a
version of project neon that instead of tracking git master tracked
the latest code in the 4.10 branch? Would it be just a copy and paste
job from project neon/backports PPA with pretty low maintenance or is
it just as much work as starting afresh?
There's a current discussion about increasing the testing on KDE
stable branches and making sure we don't introduce regressions between
4.10.1 and 4.10.2 (for example) as currently few people use and test
that branch. It's halfway between stable and unstable branch that
isn't really covered.
(with my KDE Quality team hat on)
More information about the kubuntu-devel