Hey Johan,
Well, we're not in a freeze, but the condition on us being mostly thawed was that things should be relatively feature complete when committed. I will make note that if people are adding/improving features incrementally, that has shown to be a nice way to gradually make an overall huge change. Also, we explicitly shouldn't commit things with known regressions unless the developer of that feature has the time and motivation to actively work on fixing them. The number one rule still stands... don't break trunk. If you won't have the time to check in again on a commit within 24 hours (to fix anything that may have inadvertently been broken), wait to commit it until you do have that additional time.
As for merging stuff like the grids/guides branch, if you feel okay with merging that as is and if it's complete enough to not break anything, please feel free to merge it. This is a refactoring cycle and we have 11 blockers for a release with some of those probably waiting until late summer for Krzysztof to work on them. I also have to throw out that I still don't believe the cairo folk have added the api hooks to utilize the new pixman bitmap scaling stuff... so we may still be waiting a bit on upstream.
Anyway, that's part of why I'm so open to committing these changes... I don't foresee a release for a while.
Cheers, Josh
On Thu, Mar 28, 2013 at 12:06 PM, Johan Engelen <jbc.engelen@...2592...> wrote:
On 28-3-2013 17:51, Martin Owens wrote:
On Thu, 2013-03-28 at 16:59 +0100, Markus Engel wrote:
Okay, so here's my branch: https://code.launchpad.net/~engelmarkus/inkscape/cppify
Thanks Markus,
Looking at the changes, the scope and breadth of files changed indicates that we should deal with merging this branch quickly. I'm tempted to merge it and deal with the fallout, but I'd like to hear from other devs.
Uhm, aren't we still in some kind of freeze state to get 0.49 out the door?
I agree such work is not suited at all for doing in a branch for more than a week, but it seems like a very dramatic change that could spawn a ton of crasher bugs... so it doesn't sound wise if we still intend to release 0.49 within the next months. If we plan on releasing 0.49 half a year or later from now, I'm fine with doing this work in trunk, *but* we really should first merge other branches that have been waiting for merge. (grids/guides branch is waiting for merge for example)
Ciao, Johan
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel