On 2/20/2012 10:50 AM, Remy Blank wrote:
- Our feeling that a major release must contain something radically new
/ improved / shiny / (insert your pet characteristic here), and
therefore our unwillingness to "let go" of something that we think is
only an incremental improvement.
Very true... "Worth a major upgrade and risk to break existing plugins"
would be my pet characteristic :-)
Frankly, I don't think that making our release process more complex (by
introducing one more type of release) is going to be any help. If
anything, we should rather try and make it simpler.
Well, those pre-releases would allow us to keep only two lines of
development (-stable and trunk), so it's not really more complex or
changing our habits, whereas:
Here's my counter-proposal:
- One minor release every 3 months, or as needed (e.g. security fixes,
blockers).
- One major release every 6 months.
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? If not, then I'm also very much willing to try
this alternative.
-- Christian
--
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.
