22.10.2012 20:11, Bart Oldeman пишет: > my reasoning goes like this: current "git" is much better than 1.4.0 > even if there are a few minor regressions we don't know about. So if > 1.4.0 is "stable" then what is released now should also be stable, > so as to not confuse users, who should really not be downloading 1.4.0 > anymore. I was thinking about a kind of a trick, where you don't call 1.5 a development release, so people will take it as stable. But then, if something horrible pops up, you can always say: "hey, but its 1.5!". :))
> If we label 1.5.0 as "devel" we'd be saying: use this for > testing, but use 1.4.0 if you want the trusted code base. > So whether to use 1.6 or 1.4.1 or 2.0, I don't mind, but not 1.5. In this case I'd probably vote for 1.4.1... How else would you destinguish a "quick release", and a normal one? > What I imagine of as 1.5 is if we'd be completely rewriting parts of > DOSEMU, and releasing that often (1.5.0, 1.5.1, 1.5.2, ... 1.5.100 > etc), where lots of things may and do break. I don't see that > happening. See coopthreads_v2 branch. :)) But OK, I see your point either, which is to obsolete 1.4.0. But my idea is to have a quick releases made by Justin or anyone else, and there is then a need to destinguish them. So, 1.4.1 for now? As soon as we have 1.6 or 2.0, the "quick releases" can pick up a new numbering too. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
