I've created a revised roadmap page (http://wiki.inkscape.org/wiki/index.php?title=Roadmap_revised) with the proposed changes.
Apparently the animation stuff is not going to be a focus for .48 or .49, so I took that and everything else out that seemed extraneous until the refactoring is finished.
If this seem acceptable, I'll continue to work on integrating the points I took out (any ideas what should go where? I mean, should I just insert the Animation and SVG spec stuff in after the refactor, or would we want to add it elsewhere?). Then we can replace the current roadmap with this one?
Please feel free to update this roadmap revision, or let me know if you notice something that needs to be updated or explained (I'll be happy to do it for those who don't have the time). It's obviously a very rough draft, and based solely on what a few people have mentioned they'd like to see done.
Something else which might be handy is to do "assignments" - whoever wants to volunteer to a specific item can put his name with it, just so we have a better idea of what is likely to be done and what is not being addressed. Then keep the progress updated (like the Scribus wiki)?
Thoughts?
JF
Joshua A. Andler wrote:
Hey All,
Kinda lengthy, but, please read and respond if you intend to be involved in the upcoming releases.
In numerous off-list discussions with a handful of devs and contributors it seems like there is a favored route for the upcoming releases. Essentially, make 0.47 "good enough" (avoid point releases if possible). Have a short dev cycle for 0.48 which needs to be pretty solid (even if made so over time by point releases... I will commit to continuing a couple of those). Then we go for another long-ish refactoring cycle for 0.49.
For 0.48 the thought is to... move to a DVCS before any code changes are made in trunk. This needs to be discussed and resolved ASAP, svn is not good enough for our needs any longer, period. Then, we drop in this year's SoC work, the spray tool, any big things that are far enough along in people's working copies, polish up everything and fix all new issues discovered from 0.47... if we're lucky, further text tool work could make it in too. Additionally, if we could get cairo work in a branch (under said DVCS) during this cycle, it would be excellent to possibly get something to drop in for the 0.49 dev cycle... this is part of why the stability and functionality of this release is critical (trunk may need to have issues for a bit after 0.48 drops).
For 0.49 the thought is to attempt to ditch our copy of gdl in favor of submitting the necessary bits upstream and using it as a proper library. It has been said before, it would be really excellent if we could have 2geom be broken out and used as a proper library. I understand the general "it's an experiment" and "we can't promise a stable api" issues, but, the cord needs to be cut at sometime and I think this is fair notice. Also, this is how gimp is being developed with babl and gegl... so it is doable and a non-issue (I use unstable gimp too, so I know from experience of having to update them both when I want to update gimp).
Any objections or concerns that people feel the need to voice? Anything that other people would like to see during these releases?
Cheers, Josh
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel