We had tentatively selected today as the starting date for the Inkscape 0.42 release process. I sense people have been looking forward to this day, and are ready to see a new Inkscape release. :-)
It's been quite a while since our last release, and so many of our newer developers don't have first hand experience with our release processes. Here's a brief run down of what we usually do:
First, we enter a wrap up phase called the "Frost", where developers are encouraged to bring any features they've been working on to a suitable state for formal release, stop adding any new features, and to start focusing on bug fixing. Generally this phase only lasts for a week or two.
Next, we enter a bug fixing phase called the "Feature Freeze". We identify some bug fixing goals, using a scoring system that folks have found to give a fun challenge. A list of "must fix bugs" is also generated, that the developers want to see fixed before a release is allowed; we usually don't get every one of these bugs fixed, but we certainly try to leave as few open as possible. I will be posting daily reports on our bug status as we go. Translations, documentation, release notes, and so forth also need to be updated and finalized. This phase can go on for several weeks, depending on how bad the bugs are.
Once all of the must fix bugs are fixed and all the objectives have been met, we enter the "Hard Freeze" phase. Two "Freeze Wardens" are named and all development is done as patches submitted to the freeze wardens for review and integration. This phase is intended to be quite short - a matter of days. This is intended to give us a final QA focus.
Finally, we tag and branch the codebase, create the packages, and proceed with the release. :-)
For Inkscape 0.42, I estimate that going through this process will take on the order of one to two months. It is driven largely by how quickly the bugs can be fixed, so please plan on contributing some time to this effort this month, and hopefully we can make swift progress towards our goal.
Bryce
Yes... top posting is the devil, sorry. ;)
I just want it to be known that I will take on the task of prioritizing bugs this afternoon/evening. Plus I will "filter" through the bugs & rfes to see if there are any duplicates as well.
I also need to ask, do we have an about screen yet? I haven't seen Andy around too much lately and since he's done them for the past couple releases I figured I would bring it up. The Authors file has grown significantly since the last release as well (speaking of which I'll go make sure that Aaron is listed in there).
-Josh
-----Original Message----- From: inkscape-devel-admin@lists.sourceforge.net
[mailto:inkscape-devel-
admin@lists.sourceforge.net] On Behalf Of Bryce Harrington Sent: Wednesday, June 01, 2005 12:16 PM To: inkscape-devel@...6... Cc: inkscape-user@...6... Subject: [Inkscape-devel] Starting the Inkscape 0.42 release process
We had tentatively selected today as the starting date for the
Inkscape
0.42 release process. I sense people have been looking forward to
this
day, and are ready to see a new Inkscape release. :-)
It's been quite a while since our last release, and so many of our
newer
developers don't have first hand experience with our release
processes.
Here's a brief run down of what we usually do:
First, we enter a wrap up phase called the "Frost", where developers
are
encouraged to bring any features they've been working on to a suitable state for formal release, stop adding any new features, and to start focusing on bug fixing. Generally this phase only lasts for a week or two.
Next, we enter a bug fixing phase called the "Feature Freeze". We identify some bug fixing goals, using a scoring system that folks have found to give a fun challenge. A list of "must fix bugs" is also generated, that the developers want to see fixed before a release is allowed; we usually don't get every one of these bugs fixed, but we certainly try to leave as few open as possible. I will be posting
daily
reports on our bug status as we go. Translations, documentation, release notes, and so forth also need to be updated and finalized.
This
phase can go on for several weeks, depending on how bad the bugs are.
Once all of the must fix bugs are fixed and all the objectives have
been
met, we enter the "Hard Freeze" phase. Two "Freeze Wardens" are named and all development is done as patches submitted to the freeze wardens for review and integration. This phase is intended to be quite short
-
a matter of days. This is intended to give us a final QA focus.
Finally, we tag and branch the codebase, create the packages, and proceed with the release. :-)
For Inkscape 0.42, I estimate that going through this process will
take
on the order of one to two months. It is driven largely by how
quickly
the bugs can be fixed, so please plan on contributing some time to
this
effort this month, and hopefully we can make swift progress towards
our
goal.
Bryce
This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit
http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Quoting "Joshua A. Andler" <joshua@...533...>:
I also need to ask, do we have an about screen yet? I haven't seen Andy around too much lately and since he's done them for the past couple releases I figured I would bring it up.
Not as far as I know. However, I've been toying with some ideas for one lately, if Andy's still indisposed...
-mental
On Wed, Jun 01, 2005 at 01:39:01PM -0700, Joshua A. Andler wrote:
Yes... top posting is the devil, sorry. ;)
I just want it to be known that I will take on the task of prioritizing bugs this afternoon/evening. Plus I will "filter" through the bugs & rfes to see if there are any duplicates as well.
Great, thanks! Your work at doing this for the last release was a big help. Keeping the bugs organized will save folks time.
I also need to ask, do we have an about screen yet? I haven't seen Andy around too much lately and since he's done them for the past couple releases I figured I would bring it up. The Authors file has grown significantly since the last release as well (speaking of which I'll go make sure that Aaron is listed in there).
AFAIK we do not have an about screen. There's no rule that the about screens need to always be done by the same person, so it'd be great if another artist would like to give it a shot. You're right though that this is an item we need to sort out pretty soon. :-)
Josh, if no one else submits an about screen, would you be interested in doing one (or in locating a volunteer?)
Bryce
Josh, if no one else submits an about screen, would you be interested
in
doing one (or in locating a volunteer?)
If no one else mentions working on one by the weekend, I will start working on one. I have a number of thoughts for some very snazzy examples that I can work in to show off some newer features.
-Josh
participants (3)
-
unknown＠example.com -
Bryce Harrington -
Joshua A. Andler