On 20.02.2012 17:00, Remy Blank wrote:
Christian Boos wrote:
In this case, how do you see the relationships between minor and major
releases? Won't we end up with either having a very short maintenance
period for a given major release or having more development branches to
maintain concurrently?
Ah, long-term support, always a tricky issue ;)
I had imagined keeping the same "policy": bug fixes on latest *-stable,
enhancements, features on trunk, and possibly critical fixes on older
*-stable. But I see your point: this would reduce our support to only
versions between 6 and 12 months old. Or we would have to actively
support more *-stable branches.
Some projects (e.g. [1]) "solve" this by marking certain releases for
Long Term Support. For example (tweak numbers as you see fit) we could
release one LTS release every 12 months, one major non-LTS release every
6 months and minor releases every 3 months or whenever needed. Only the
latest LTS release would get a maintained *-stable branch with minor
releases.
This way you can keep the number of maintained branches under control,
make more major releases, and provide relatively long term support. But
of course it's still a quite difficult trade-off.
--
Peter
[1] https://wiki.ubuntu.com/LTS
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to trac-dev@googlegroups.com.
To unsubscribe from this group, send email to
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
