On Wed, May 30, 2012 at 12:16:40AM +0200, jb wrote: > So my guess is that we should use the rather standard x.y.z > format where x is increased when a new major release is made, > y is increased when a new minor release is made and z is for > bugfix releases. Is that ok for everyone?
Fine with me. > Second question, in Randa last year we decided to use even > number for stable releases and odd numbers for development > releases. However that was before the move to git, and now > I am not sure it really makes sense. Maybe but only if there are actual users of unstable *releases* since these tend to rely on upstream SCM anyways. Are there any? > The biggest puzzle for me is what version number should be used > for trunk now that there is a 0.9 branch... Depends on what comes out of that "trunk": if the next version getting tagged is 0.9.x, then 0.9; if it would be 0.10.0, then 0.10; if the goal is 1.0.0, then 1.0. See http://collectd.org for one of quite elaborate examples: http://git.verplant.org/?p=collectd.git (one of my favourite upstreams in both functional and packaging senses :) -- ---- WBR, Michael Shigorin <m...@altlinux.ru> ------ Linux.Kiev http://www.linux.kiev.ua/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Kdenlive-devel mailing list Kdenlive-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kdenlive-devel
