Hi,
I am not an active developer of Inkscape, nor a user of Linux but I use it for a while and I did some work on it. On the other side I have a long experience of building and promoting software in the cad business.
If you can't match deadlines, it is better to adapt deadlines until you can match them without too much stress. Moving from 0.47 to 0.49 implies to most users that you barely fixed a few bugs so it impacts credibility and IMO inkscape as is deserves a better deal.
I like the scheme used by SolidWorks (commercial but they started with a small team) : One release per year, named after the starting year. Say you ship in february 2011 it named Inkscape 2011
Followed by an index indicating the service pack, only bug fixes, I mean regressions, security, very minor enhancements. Instead of being a month it's a number. It can be reset each year (2011.00, 2011.01, 2011.02) or accumulated and in this case follow the .49, so it becomes 2011.49. Both seems excellent to me. For advanced users they will look for the number after the dot, most users will remember the year and go back to the site when they notice it is getting too old and they will remember the best vintage.
So a release cycle of one major per year and 3 patches (one per quarter) would be a mature choice. It implies to have 2 baselines one for next year release, one for current. 3 months before the release cycle a call to everyone to complete and commit new stuff, what is done is done, everything else is for next year. No stress.
Have a nice day, -Bruno
Bruno Winck Email: bwinck@...2632... Blog: http://www.kneaver.com/blog Kneaver Corp http://www.kneaver.com/ Twitter:http://twitter.com/kneaver SKYPE:brunowinck PH: +1 (415) 749 5850 CELL: +1 (415) 513 3160
-----Original Message----- From: Alex Valavanis [mailto:valavanisalex@...400...] Sent: Saturday, June 11, 2011 1:45 AM To: Alexandre Prokoudine Cc: Inkscape Devel List Subject: Re: [Inkscape-devel] versioning scheme, take 2
Well, I'm viewing this from a linux distribution perspective. At the moment, whenever Ubuntu (or other widely-used distro) users upgrade to a new distribution version, they get a new upstream version of Firefox, OpenOffice/LibreOffice etc... this obviously attracts attention from development blogs/press-releases. However, Inkscape releases are less frequent than most linux distro-releases so users have to make do with a few patches that have been introduced by the package maintainer. I think that a fixed time release <= 6 months would ensure that we produce a new upstream release in time for most linux distribution releases. A version number >=1.0 would also give the impression of a >="usable" product, and I think we're certainly at that stage already.
AV
On 10 June 2011 21:52, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Fri, Jun 10, 2011 at 9:35 PM, Josh Andler wrote:
Bryce had also suggested a year/current system hybrid a couple years ago when last discussed, such as 2011.0.49
Please don't. YEAR.MONTH is really good enough.
Alexandre Prokoudine http://libregraphicsworld.org
EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel