"There's no way to get fixes without also getting enhancements" ---- unless ---- you use a non-linear source control like Git. (please switch?) :)
Ok no flames please - but since we have switched to Git nearly 2 years ago we have been blessed with it's abilities to keep a stable branch "master" and a RC branch "next" going with the freedom to try anything in the background (topic branches). Branching is easy, cheap and fun and I create a branch for every new bugfix or feature. It's a thing of beauty and I could never go back to SVN or CVS. I would switch to Hg first (badomp bomp *ching*) :) Just my $0.02 On Apr 16, 6:53 am, Rich Hickey <richhic...@gmail.com> wrote: > - Development process stability > > Currently all new work (fixes and enhancements) occurs in trunk. > There's no way to get fixes without also getting enhancements. I think > this is the major missing piece in offering stable numbered releases. > While I've cut a branch for each of the prior two releases, no one has > ever submitted a bugfix patch for either. If people are going to want > to work with a particular release version for an extended period of > time, someone (other than me) will have to produce patches of (only!) > fixes from the trunk for the release branch, and occasionally produce > point releases (1.0.x) from that branch. I'd like to continue to do > the bulk of my work in trunk, without messing anyone up or forcing > everyone to follow along. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
