On Fri, 8 Jul 2011 at 8:22:56 +0200, Martin Dietze wrote:
>
> Now we 'just' need to answer the question on how we get features
> from 'next' to 'crm'. Maybe we need an integration branch from
> which we merge revisions into 'crm' once they have been tested
> long enough? This would go well enough with Debian's policy, we
> would put a lower version into 'testing' and a slightly higher
> version into 'unstable'.
Well, the branch 'next' is not really a place to get new features which
then propagate to 'master' after enough testing.
'next' was meant to be a place where I could make mistakes without
affecting the main branch directly. So people are supposed to look
into 'next' and see whether I've been sane or not ("look, that patch xyz
that is on 'next' doesn't make sense because of zyx, please don't propagate
to 'master').
So 'next' has nothing to do with 'development', and we could even live without
it (it would at least not confuse people).
wmaker-crm is primarily a place to send bug fixes, and occasionaly new
non-disrupting features. Stability is the main purpose.
I started wmaker-crm because there was _no_ central place where fixes
to wmaker were being collected, no cvs, no developers no nothing was
available. One needed to go to the distros to see some stabilization.
Now we have a place where wmaker can approach absolute stability.
So if Debian wants to take wmaker-crm, just grab the 'master' branch
and forget about 'next'.
--
To unsubscribe, send mail to [email protected].
