Now that the release branch is established, the main svn head is back open for regular development. Commit freely!
Bryce
P.S., while you're developing, if you spot a fix that ought to go into the release, please file a bug report with a description and the commit ID, and mark it milestone 0.46. Josh and I will take it from there.
Now that work has begun on 0.47, is it possible for someone to put the release note for that release (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes047) on the front page of the wiki, so people can add things to it?
Thanks Joel
On Sat, 2008-02-23 at 12:19 -0800, bryce@...961... wrote:
Now that the release branch is established, the main svn head is back open for regular development. Commit freely!
Bryce
P.S., while you're developing, if you spot a fix that ought to go into the release, please file a bug report with a description and the commit ID, and mark it milestone 0.46. Josh and I will take it from there.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Feb 23, 2008, at 3:51 PM, Joel Holdsworth wrote:
Now that work has begun on 0.47, is it possible for someone to put the release note for that release (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes047) on the front page of the wiki, so people can add things to it?
Done.
Thanks!
On Sat, 2008-02-23 at 16:14 -0800, Jon A. Cruz wrote:
On Feb 23, 2008, at 3:51 PM, Joel Holdsworth wrote:
Now that work has begun on 0.47, is it possible for someone to put the
release note for that release
(http://wiki.inkscape.org/wiki/index.php/ReleaseNotes047) on the front
page of the wiki, so people can add things to it?
Done.
What status should be assigned to bugs that are fixed after the branch, so that they will be considered for the 0.46 release branch?
If they are marked "fix released" (the usual status for bugs that are fixed in SVN), then there will be no way to search for bugs that have been fixed in SVN, but are not yet in the release branch.
Maybe such bugs could be marked "fix committed", since we don't currently use that status for anything else? Then the 0.46 wranglers can switch them to "fix released" when they make a decision about inclusion in 0.46?
-Tom
On Sat, Feb 23, 2008 at 4:30 PM, Joel Holdsworth <joel@...1709...> wrote:
Thanks!
On Sat, 2008-02-23 at 16:14 -0800, Jon A. Cruz wrote:
On Feb 23, 2008, at 3:51 PM, Joel Holdsworth wrote:
Now that work has begun on 0.47, is it possible for someone to put the
release note for that release
(http://wiki.inkscape.org/wiki/index.php/ReleaseNotes047) on the front
page of the wiki, so people can add things to it?
Done.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Sat, Feb 23, 2008 at 06:43:30PM -0800, Tom Davidson wrote:
What status should be assigned to bugs that are fixed after the branch, so that they will be considered for the 0.46 release branch?
If they are marked "fix released" (the usual status for bugs that are fixed in SVN), then there will be no way to search for bugs that have been fixed in SVN, but are not yet in the release branch.
Maybe such bugs could be marked "fix committed", since we don't currently use that status for anything else? Then the 0.46 wranglers can switch them to "fix released" when they make a decision about inclusion in 0.46?
That would be fine; make sure to mention something like, "Port this fix to the release branch" so it's clear it's fixed and needs backported.
Alternately, I've also set up a "0.46.x Series", which allows marking new fixed bugs for porting into the release tree. This can be done via "Nominate for Release".
We can experiment around a bit and see what procedure feels most convenient and effective.
Bryce
On Sat, Feb 23, 2008 at 4:19 PM, <bryce@...961...> wrote:
Now that the release branch is established, the main svn head is back open for regular development. Commit freely!
I'm slightly concerned that this may distract developers from the remaining bugfixing :) Seriously, we have several very serious showstoppers now: crash in extension effects preview, no printing on windows, PDF export of moderately complex files fails, OCAL imports bitmaps only, and probably more. Let's focus on them now.
On Sat, Feb 23, 2008 at 08:12:16PM -0400, bulia byak wrote:
On Sat, Feb 23, 2008 at 4:19 PM, <bryce@...961...> wrote:
Now that the release branch is established, the main svn head is back open for regular development. Commit freely!
I'm slightly concerned that this may distract developers from the remaining bugfixing :) Seriously, we have several very serious showstoppers now: crash in extension effects preview, no printing on windows, PDF export of moderately complex files fails, OCAL imports bitmaps only, and probably more. Let's focus on them now.
Honestly, I think we can trust the developers to manage their time and focus on the work they know needs to get done.
In past hard freezes, the way we've gotten the last remaining bug fixes done less because of restricting developer's ability to do regular work, but because they took the bugs as priorities and worked on solving them.
Perhaps the additional energy from having the main tree open for development will enable experimentation that will result in more bug fixes than we could get otherwise. This early branching is a bit of an experiment and I'm interested in seeing how it affects our process.
Bryce
Bryce Harrington-5 wrote:
Perhaps the additional energy from having the main tree open for development will enable experimentation that will result in more bug fixes than we could get otherwise. This early branching is a bit of an experiment and I'm interested in seeing how it affects our process.
Sounds like you don't want the windows discouragement to slow you down! Thank you for all your hard work from a windows slave who can't hack, but does contribute to wikis and otherwise.
Rygle
participants (7)
-
unknown＠example.com -
Bryce Harrington -
bulia byak -
Joel Holdsworth -
Jon A. Cruz -
rygle -
Tom Davidson