From: Lukas W. <luk...@gm...> - 2014-01-20 21:30:33
|
I'm not sure if and how this discussion resulted. Anyway, my thoughts on this: I vote against using a year/month/whatever-time-span versioning scheme. For the user, it just doesn't represent how many changes were made or how major the changes are. A lot of time passed doesn't mean a lot of great changes made. At least the first number should represent major changes (to be proud of) and not time. There are other ways of letting the user know how old his build is. 2014/1/19 Stian Jørgensrud <sti...@gm...>: > Keep it simple. > > > > -- > View this message in context: http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Next-releases-tp4884p4973.html > Sent from the lmms-devel mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > LMMS-devel mailing list > LMM...@li... > https://lists.sourceforge.net/lists/listinfo/lmms-devel |