On Tue, Mar 4, 2008 at 11:37 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > But if you s/stop/slow down/ what I said, it may start to resemble a more > serious question. Given that git dev has such a frantic pace... would it make sense to give way to some "version inflation"? This would give end users a more clear sense of how much things have changed -- a 1.4.x to 1.5.x doesn't seem like much. But a 1.5 to 2.0 with a "new features summary" will grab a bit of attention, get its slashdot article, and be a more frank communication of the work that's happened, and what the user can expect. In other words, the 'linux versioning' scheme sucks when dealing with people who aren't sub'd to the mailing list. Yes, from git v0.99 to today we haven't broken anything too significant, but from an end user POV, several of the smaller changes carry enough incompatibility that v1.4.x and v1.5.x are not actually compatible (all the remote heads handling changes, for example). So say rock on, but label the next feature release 2.0 or at least 1.6 and declare it is "mostly compatible, but you'll do well in re-cloning your projects to keep things simple" -- in practice, I've had to do that anyway on the 1.3->1.4->1.5 transitions. cheers, martin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
