John Taber wrote:
Bryce Harrington wrote:
On Mon, Apr 17, 2006 at 02:49:42PM -0300, bulia byak wrote:
But first, some food for thought. Judging by SF statistics, 0.43 is the first Inkscape version where we failed to double the number of downloads. Up to 0.42, the approximate doubling rule held (if we count 0.42 and 0.42.2 as one version), but 0.43 got only a bit more downloads than 0.42: 347000 vs . 300000, even though this release was longer. May be a stats glitch, but may be an indication that 0.44 needs to be marketed more aggressively.
just a thought: I'm sure there's others like me that now simply go along with the Ubuntu, etc releases which means waiting ~6 mos for the newest app versions rather than getting into the whole dependency game, which means we are still running 0.42 on our production machines. 0.44 will probably be too late for Dapper but may not have many non-Dapper dependencies so it might be an easy backport that we could put on the download site. Maybe this becomes part of distro testing.
I do think it's worth considering getting on the Gnome release schedule. For starters there wouldn't be any question on when the next release is. I can see a major benefit being that we know we won't go over 6 months without a release. Not exceeding 6 months seems like it would be good for the marketing aspect... we're always reminding people that we're out there and the project is still being very actively developed.
If we want to have another release in-between the 6 month cycle, tis all good. For us to be on the Gnome release schedule we would have the benefit of a current version going into new releases of Ubuntu and Fedora (as well as any other distros that follow Gnome's schedule). A schedule also provides solid deadlines for people to know when their work needs to be finished. To me, it seems like a little more structure would only benefit both us and our users. Eh, just my .02.
-Josh