Re: [Inkscape-devel] 0.45 release work (was Re: stirring it Inkscape-devel Digest, Vol 5, Issue 4
From: Bryce Harrington <bryce@...961...>
Is anyone in the middle of any development work that must be finished before we freeze?
The axonometric grid still needs a lot of work. I have to reorganize grid classes and grid snapping stuff. I am on it, but haven't got that much time; I can definitely not complete it soon. Almost everytime I log on to IRC, someone mentions a bug/feature which I instantly want to fix to keep me from working on it! :P Shall I insert compiler directives to easily disable all axonometric grid code? (simply removing the UI radiobuttons to enable is easier but stupid :)
Since this is the first release I am actively involved in, how exactly does it work? You freeze the code at a certain moment (by creating a 0.45 branch?); then new development can still continue on the SVN trunk, and bughunting is done on the 0.45 branch?
Cheers, Johan
Johan Engelen wrote:
Since this is the first release I am actively involved in, how exactly does it work? You freeze the code at a certain moment (by creating a 0.45 branch?); then new development can still continue on the SVN trunk, and bughunting is done on the 0.45 branch?
If I recall correctly, for the 0.44 release, first the features wanted in the release were identified. We then had a week to stop working on anything else and complete 50% of the release features. Then in two weeks time we already had gathered a buglist and went into feature freeze. Then we released a series of release candidates and in three weeks time we had a hard freeze and concentrated only on open bugs. At about the same time 0.44 development was moved into a dedicated branch. We released the final 0.44 version ten days after that.
Although the time plan was delayed a few times, 0.44 transformed from an idea into a stable release in something less than two months.
BTW, any detailed plans/dates for 0.45?
- Spyros Blanas
I just noticed this thread on the list. I hope you guys aren't going to do a cutoff for at least a few weeks.
I haven't contributed code for the last few weeks, but I've done a LOT of code for this cycle in two areas, and it would be a shame for no visible results to appear in this cut:
1. JS-DOM binding. This is in the midst of debugging, and can finally give us scripting of Inkscape internals. I would at least like to be able to do in-memory scripting with this before the release.
2. The export dialog. Ted added the code recently that is needed for passing parameters from an export dialog to the Ouput extensions. It would be a shame to not have a working general-purpose export dialog, for things other than merely PNG. A first cut of the dialog already exists, and the existing PNG export has been decoupled from both its dialog and file.cpp. And of course Miklos has recently added the Cairo equivalents for PDF and PNG export. So building the bridges between would only require the typical code/test/debug/code/blah.... cycle.
I would not mind if anyone wants to hack on the export dialog to get some of this implemented. I don't really care about its appearance. I am more interested in the "under the hood" infrastructure.
bob
On 10/3/06, Bob Jamison <rwjj@...127...> wrote:
I would not mind if anyone wants to hack on the export dialog to get some of this implemented. I don't really care about its appearance. I am more interested in the "under the hood" infrastructure.
I'll have a look at the new dialog.
Meanwhile, after a GTK upgrade I noticed a funny thing: now our file dialogs have two filepath entry fields :) One was coded by you, and the other was apparently reintroduced in GTK (better late than never). So, can you please look into removing this old hack? The only problem I found with the new native filepath field is that it does not honor pressing Enter; can you please also check if this is fixable?
Also, did you have any luck with Tor's dll? I just got a message from Tor asking about it.
Thanks!
On Tue, 2006-10-03 at 18:35 -0500, Bob Jamison wrote:
I just noticed this thread on the list. I hope you guys aren't going to do a cutoff for at least a few weeks.
I haven't contributed code for the last few weeks, but I've done a LOT of code for this cycle in two areas, and it would be a shame for no visible results to appear in this cut:
- JS-DOM binding. This is in the midst of debugging,
and can finally give us scripting of Inkscape internals. I would at least like to be able to do in-memory scripting with this before the release.
Bob, I'm curious how we can get other people involved in this task to help you out and to spread out energy. Also, our bus count is low in this area (no offense, because I don't ever want to see a bus hit any of us) and it would be great to provide some hooks for developers. What do you think?
- The export dialog. Ted added the code recently
that is needed for passing parameters from an export dialog to the Ouput extensions. It would be a shame to not have a working general-purpose export dialog, for things other than merely PNG. A first cut of the dialog already exists, and the existing PNG export has been decoupled from both its dialog and file.cpp. And of course Miklos has recently added the Cairo equivalents for PDF and PNG export. So building the bridges between would only require the typical code/test/debug/code/blah.... cycle.
Yet again, it would be great to see some details as to how some developers could plug into this...even if just a little write-up on the wiki or on this list...
I would not mind if anyone wants to hack on the export dialog to get some of this implemented. I don't really care about its appearance. I am more interested in the "under the hood" infrastructure.
Cool...this is going to be another great release!
Jon
bob
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=D... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Tue, Oct 03, 2006 at 06:35:48PM -0500, Bob Jamison wrote:
I just noticed this thread on the list. I hope you guys aren't going to do a cutoff for at least a few weeks.
Now that we've backburnered for a few weeks, how are things looking? I think we'll still have sufficient time before the release to get these finalized, but I hope they're nearing a good stopping point?
I haven't contributed code for the last few weeks, but I've done a LOT of code for this cycle in two areas, and it would be a shame for no visible results to appear in this cut:
- JS-DOM binding. This is in the midst of debugging,
and can finally give us scripting of Inkscape internals. I would at least like to be able to do in-memory scripting with this before the release.
- The export dialog. Ted added the code recently
that is needed for passing parameters from an export dialog to the Ouput extensions. It would be a shame to not have a working general-purpose export dialog, for things other than merely PNG. A first cut of the dialog already exists, and the existing PNG export has been decoupled from both its dialog and file.cpp. And of course Miklos has recently added the Cairo equivalents for PDF and PNG export. So building the bridges between would only require the typical code/test/debug/code/blah.... cycle.
I would not mind if anyone wants to hack on the export dialog to get some of this implemented. I don't really care about its appearance. I am more interested in the "under the hood" infrastructure.
Thanks, Bryce
On Fri, 2006-10-20 at 16:30 -0700, Bryce Harrington wrote:
On Tue, Oct 03, 2006 at 06:35:48PM -0500, Bob Jamison wrote:
I just noticed this thread on the list. I hope you guys aren't going to do a cutoff for at least a few weeks.
Now that we've backburnered for a few weeks, how are things looking? I think we'll still have sufficient time before the release to get these finalized, but I hope they're nearing a good stopping point?
However, I think the primary thing we should be trying to get out is our Summer of Code code...why can't we just launch this and then do a 0.46 for the rest...In looking at my crystal ball, it seems like all these other tasks will push our release back until after christmas...which is okay, but think it would be good to get out a release for our Summer of Code and to highlight that work...
I love all the new work, just think a quicker release here and there isn't a bad thing...
Jon
I haven't contributed code for the last few weeks, but I've done a LOT of code for this cycle in two areas, and it would be a shame for no visible results to appear in this cut:
- JS-DOM binding. This is in the midst of debugging,
and can finally give us scripting of Inkscape internals. I would at least like to be able to do in-memory scripting with this before the release.
- The export dialog. Ted added the code recently
that is needed for passing parameters from an export dialog to the Ouput extensions. It would be a shame to not have a working general-purpose export dialog, for things other than merely PNG. A first cut of the dialog already exists, and the existing PNG export has been decoupled from both its dialog and file.cpp. And of course Miklos has recently added the Cairo equivalents for PDF and PNG export. So building the bridges between would only require the typical code/test/debug/code/blah.... cycle.
I would not mind if anyone wants to hack on the export dialog to get some of this implemented. I don't really care about its appearance. I am more interested in the "under the hood" infrastructure.
Thanks, Bryce
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (6)
-
Bob Jamison -
Bryce Harrington -
bulia byak -
Johan Engelen -
Jon Phillips -
Spyros Blanas