I'm not a (good) C++ programmer nor am I part of the Inkscape team, though I imagine several items on the current roadmap to be huge. SVG 2 support, Hardware acceleration or animation support for example sound like things that could take a long time to be fully implemented.
So as Bryce said, in order to shorten Inkscape's release cycle you should focus on just a few (smaller) features for the next release(s). All (bigger) features should be developed in parallel on their own branch and merged when they are ready. They should not block a release. Surely keeping these branches synchronized with the main branch may sometimes be quite difficult, but worth doing to keep a clear roadmap and don't let users wait too long for new versions. To do so maybe a few people could focus on these bigger things while the others work on the parts for the next release. Though that depends on the number of contributors you have, of course.
Sebastian
On 23 November 2014 at 20:49, Josh Andler <scislac@...400...> wrote:
Bryce,
Thanks for getting the discussion started on this! The list is already looking like a great place to start. I'm hoping that this can give us some good direction moving forward with the next handful of releases.
Cheers, Josh
On Sat, Nov 22, 2014 at 11:45 PM, Bryce Harrington <bryce@...961...> wrote:
With 0.91 finally coming to a wrap soon, there are many different ideas on what to focus on next. One thing we all agree on is turning the next few releases out more rapidly, 0.92 especially.
To do this, we'll need to carefully select which new features to undertake each release; the more discriminating we are, the less risk of delay we'll face in these. The less we undertake in parallel, the more quickly we can perfect what we do tackle. The more we collaborate together as a team, the better the end result will be.
The Inkscape roadmap has proven instrumental in prioritizing and organizing our effort in the past. We can to use it again to help chart our course of development for the next several releases.
http://wiki.inkscape.org/wiki/index.php/RoadmapI'd like to tackle this in three steps: First, brainstorm and gather ideas into a big list. Second, filter the list down to our most pressing needs. And third, prioritize that list across the next half-dozen releases.
I figure we should strive for one primary objective each release, with one secondary and perhaps a few tertiary items. Of course, as we go we'll also have some surprises, early deliveries and the like; no need to turn those away. But the idea is to focus Inkscape on what we as a project want to achieve each release.
What do you think should be listed in our Roadmap?
Bryce
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.cl...
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.cl... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel