Welcome, Guest! Log In | Create Account

Find and develop open source software

Jump to main content
Jump to project navigation
Jump to downloads for Inkscape

SourceForge.net > Projects > Inkscape > Mail > Archive

Donate

Inkscape

Email Archive: inkscape-devel (read-only)

[Inkscape-devel] Inkscape 0.47 Proposed Release Plan

From: Joshua A. Andler <scislac@gm...> - 2009-04-18 23:18

Hey All,

In an effort to honor Bryce's work in this department for previous
releases, I've liberally copied & pasted what he wrote last time. :)

I know that it looks incredibly ambitious with the dates on there, but
it IS doable provided people have the time and desire. I'd be interested
to see what would happen if we plan a bug sprint weekend on May 9 & 10.
We can have whoever is up for the challenge commit to it and see what we
can pull off in two days.

The following is based on previous release plans. Let me know if
there's anything missing.

1. Open development.
(Complete)

2. Chill. Development focuses on wrapping up.
(In progress) No further refactoring.
Identify 'make distcheck' issues
Triage bug reports
Run an About Screen contest
First draft of Release Notes.
Update tutorials and other docs

3. Frost. Most development complete.
(May 1, 2009) Release Notes should be >90% filled in.
Bug Hunt: 500 points
Post inkscape-0.47-alpha.tar.gz

4. Feature Freeze. No further development work.
(May 15, 2009) Disable features that can't be finished in time.
Focus on critical bug fixing.
Finalize all tutorials, docs, etc.
Finalize all extensions.
Translators create translations.
Inkscape must pass 'make distcheck'
Post inkscape-0.47-beta.tar.gz

5. Hard freeze. Only release wardens can commit to mainline.
(May 25, 2009) No further string changes.
Focus on release-critical bug fixing.
Finalize translations, release notes, etc.
Packagers test creating pkgs of the -beta release.
Post inkscape-0.47-rc1.tar.gz

6. Branch. Establish the Stable Branch for release
(June 5, 2009) Complete any late-late-late work.
Final verification of packaging, release notes,
docs, etc.
Publish more release candidates until ready for
release.
Plan 0.47.1+ release(s), if needed

7. Release. Post inkscape-0.47.tar.gz
(June 15, 2009) Post packages
Post official announcements

8. Open development.

I know it is a radically short timeframe, especially given how long 0.46
took. However, our last few releases have been dragged out to a painful
degree. Honestly, it seems like most people loathe the process now.
So... let's rip the bandaid off and just make it happen. We can modify
the schedule at any point of course, but we need to address our biggest
issues IMMEDIATELY to attempt to keep the dates as close as possible.

This is doable. We're good, we're smart, we're competent, and we have
the resources... we just need to be focused to make this happen.

Cheers,
Josh

P.S. As all can see, I'm attacking the bug tracker... I hope other
non-coders will contribute to preparing the bug tracker for the bug hunt
too (let's free up the bug fixers time to actually fix things, rather
than wade through the current mess).

Thread View

Thread	Author	Date
[Inkscape-devel] Inkscape 0.47 Proposed Release Plan	Joshua A. Andler <scislac@gm...>

Re: [Inkscape-devel] Inkscape 0.47 Proposed Release Plan

From: the Adib <theadib@go...> - 2009-04-18 23:27

Hi Josh,

we have a lot of bugs assigned to 0.47.
We need a new release target 0.48 in launchpad in order to properly
move the bugs to the next release if needed.

HTH, Adib.
...

On Sun, Apr 19, 2009 at 1:18 AM, Joshua A. Andler <scislac@gm...> wrote:
> Hey All,
>
> In an effort to honor Bryce's work in this department for previous
> releases, I've liberally copied & pasted what he wrote last time. :)
>
> I know that it looks incredibly ambitious with the dates on there, but
> it IS doable provided people have the time and desire. I'd be interested
> to see what would happen if we plan a bug sprint weekend on May 9 & 10.
> We can have whoever is up for the challenge commit to it and see what we
> can pull off in two days.
>
> The following is based on previous release plans. Let me know if
> there's anything missing.
>
> 1. Open development.
> (Complete)
>
> 2. Chill. Development focuses on wrapping up.
> (In progress) No further refactoring.
> Identify 'make distcheck' issues
> Triage bug reports
> Run an About Screen contest
> First draft of Release Notes.
> Update tutorials and other docs
>
> 3. Frost. Most development complete.
> (May 1, 2009) Release Notes should be >90% filled in.
> Bug Hunt: 500 points
> Post inkscape-0.47-alpha.tar.gz
>
> 4. Feature Freeze. No further development work.
> (May 15, 2009) Disable features that can't be finished in time.
> Focus on critical bug fixing.
> Finalize all tutorials, docs, etc.
> Finalize all extensions.
> Translators create translations.
> Inkscape must pass 'make distcheck'
> Post inkscape-0.47-beta.tar.gz
>
> 5. Hard freeze. Only release wardens can commit to mainline.
> (May 25, 2009) No further string changes.
> Focus on release-critical bug fixing.
> Finalize translations, release notes, etc.
> Packagers test creating pkgs of the -beta release.
> Post inkscape-0.47-rc1.tar.gz
>
> 6. Branch. Establish the Stable Branch for release
> (June 5, 2009) Complete any late-late-late work.
> Final verification of packaging, release notes,
> docs, etc.
> Publish more release candidates until ready for
> release.
> Plan 0.47.1+ release(s), if needed
>
> 7. Release. Post inkscape-0.47.tar.gz
> (June 15, 2009) Post packages
> Post official announcements
>
> 8. Open development.
>
>
> I know it is a radically short timeframe, especially given how long 0.46
> took. However, our last few releases have been dragged out to a painful
> degree. Honestly, it seems like most people loathe the process now.
> So... let's rip the bandaid off and just make it happen. We can modify
> the schedule at any point of course, but we need to address our biggest
> issues IMMEDIATELY to attempt to keep the dates as close as possible.
>
> This is doable. We're good, we're smart, we're competent, and we have
> the resources... we just need to be focused to make this happen.
>
> Cheers,
> Josh
>
> P.S. As all can see, I'm attacking the bug tracker... I hope other
> non-coders will contribute to preparing the bug tracker for the bug hunt
> too (let's free up the bug fixers time to actually fix things, rather
> than wade through the current mess).
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@li...
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>

Re: [Inkscape-devel] Inkscape 0.47 Proposed Release Plan

From: Joshua A. Andler <scislac@gm...> - 2009-04-18 23:48

Adib,

Well, let's not let any carry over then. ;) Thanks for pointing this
out. As soon as I can figure out how to add it, it will be there. :D

Cheers,
Josh

On Sun, 2009-04-19 at 01:27 +0200, the Adib wrote:
> Hi Josh,
>
> we have a lot of bugs assigned to 0.47.
> We need a new release target 0.48 in launchpad in order to properly
> move the bugs to the next release if needed.
>
> HTH, Adib.
> ...
>
> On Sun, Apr 19, 2009 at 1:18 AM, Joshua A. Andler <scislac@gm...> wrote:
> > Hey All,
> >
> > In an effort to honor Bryce's work in this department for previous
> > releases, I've liberally copied & pasted what he wrote last time. :)
> >
> > I know that it looks incredibly ambitious with the dates on there, but
> > it IS doable provided people have the time and desire. I'd be interested
> > to see what would happen if we plan a bug sprint weekend on May 9 & 10.
> > We can have whoever is up for the challenge commit to it and see what we
> > can pull off in two days.
> >
> > The following is based on previous release plans. Let me know if
> > there's anything missing.
> >
> > 1. Open development.
> > (Complete)
> >
> > 2. Chill. Development focuses on wrapping up.
> > (In progress) No further refactoring.
> > Identify 'make distcheck' issues
> > Triage bug reports
> > Run an About Screen contest
> > First draft of Release Notes.
> > Update tutorials and other docs
> >
> > 3. Frost. Most development complete.
> > (May 1, 2009) Release Notes should be >90% filled in.
> > Bug Hunt: 500 points
> > Post inkscape-0.47-alpha.tar.gz
> >
> > 4. Feature Freeze. No further development work.
> > (May 15, 2009) Disable features that can't be finished in time.
> > Focus on critical bug fixing.
> > Finalize all tutorials, docs, etc.
> > Finalize all extensions.
> > Translators create translations.
> > Inkscape must pass 'make distcheck'
> > Post inkscape-0.47-beta.tar.gz
> >
> > 5. Hard freeze. Only release wardens can commit to mainline.
> > (May 25, 2009) No further string changes.
> > Focus on release-critical bug fixing.
> > Finalize translations, release notes, etc.
> > Packagers test creating pkgs of the -beta release.
> > Post inkscape-0.47-rc1.tar.gz
> >
> > 6. Branch. Establish the Stable Branch for release
> > (June 5, 2009) Complete any late-late-late work.
> > Final verification of packaging, release notes,
> > docs, etc.
> > Publish more release candidates until ready for
> > release.
> > Plan 0.47.1+ release(s), if needed
> >
> > 7. Release. Post inkscape-0.47.tar.gz
> > (June 15, 2009) Post packages
> > Post official announcements
> >
> > 8. Open development.
> >
> >
> > I know it is a radically short timeframe, especially given how long 0.46
> > took. However, our last few releases have been dragged out to a painful
> > degree. Honestly, it seems like most people loathe the process now.
> > So... let's rip the bandaid off and just make it happen. We can modify
> > the schedule at any point of course, but we need to address our biggest
> > issues IMMEDIATELY to attempt to keep the dates as close as possible.
> >
> > This is doable. We're good, we're smart, we're competent, and we have
> > the resources... we just need to be focused to make this happen.
> >
> > Cheers,
> > Josh
> >
> > P.S. As all can see, I'm attacking the bug tracker... I hope other
> > non-coders will contribute to preparing the bug tracker for the bug hunt
> > too (let's free up the bug fixers time to actually fix things, rather
> > than wade through the current mess).
> >
> >
> > ------------------------------------------------------------------------------
> > Stay on top of everything new and different, both inside and
> > around Java (TM) technology - register by April 22, and save
> > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> > 300 plus technical and hands-on sessions. Register today.
> > Use priority code J9JMT32. http://p.sf.net/sfu/p
> > _______________________________________________
> > Inkscape-devel mailing list
> > Inkscape-devel@li...
> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> >

Re: [Inkscape-devel] Inkscape 0.47 Proposed Release Plan

From: Alexandre Prokoudine <alexandre.prokoudine@gm...> - 2009-04-19 16:45

On Sun, Apr 19, 2009 at 3:18 AM, Joshua A. Andler wrote:
> Hey All,
>
> In an effort to honor Bryce's work in this department for previous
> releases, I've liberally copied & pasted what he wrote last time. :)
>
> I know that it looks incredibly ambitious with the dates on there, but
> it IS doable provided people have the time and desire. I'd be interested
> to see what would happen if we plan a bug sprint weekend on May 9 & 10.
> We can have whoever is up for the challenge commit to it and see what we
> can pull off in two days.
>
> The following is based on previous release plans. Let me know if
> there's anything missing.

Looks good to me. However we need someone who has a working setup to
update our DocBook tuts. We have a nasty bug in one of them still not
fixed, because nobody could recreate an SVG file from a DocNuke file.

Alexandre

Re: [Inkscape-devel] Inkscape 0.47 Proposed Release Plan

From: Chris Lilley <chris@w3...> - 2009-04-21 12:10

On Sunday, April 19, 2009, 6:45:10 PM, Alexandre wrote:

AP> Looks good to me. However we need someone who has a working setup to
AP> update our DocBook tuts. We have a nasty bug in one of them still not
AP> fixed, because nobody could recreate an SVG file from a DocNuke file.

What is the DocBook SVG issue exactly?

I know Norm Walsh, who is a key DocBook guy so I could ask him, or get samples to/from him, or whatever. If I know what the issue is.

--
Chris Lilley mailto:chris@w3.org
Technical Director, Interaction Domain
W3C Graphics Activity Lead
Co-Chair, W3C Hypertext CG

Re: [Inkscape-devel] Inkscape 0.47 Proposed Release Plan

From: Alexandre Prokoudine <alexandre.prokoudine@gm...> - 2009-04-21 13:50

On Tue, Apr 21, 2009 at 3:43 PM, Chris Lilley wrote:

> AP> Looks good to me. However we need someone who has a working setup to
> AP> update our DocBook tuts. We have a nasty bug in one of them still not
> AP> fixed, because nobody could recreate an SVG file from a DocNuke file.
>
> What is the DocBook SVG issue exactly?
>
> I know Norm Walsh, who is a key DocBook guy so I could ask him, or get samples to/from him, or whatever. If I know what the issue is.

What I mean is that there was a textual error in one of the tutorials
and a new SVG files was never created.

Alexandre

Re: [Inkscape-devel] Inkscape 0.47 Proposed Release Plan

From: Bryce Harrington <bryce@ca...> - 2009-04-21 21:10

I've added this, and a few other milestones, as well as showed Josh how
to add more.

Let him know if there's more needing to be added.

On Sat, Apr 18, 2009 at 04:47:50PM -0700, Joshua A. Andler wrote:
> Adib,
>
> Well, let's not let any carry over then. ;) Thanks for pointing this
> out. As soon as I can figure out how to add it, it will be there. :D
>
> Cheers,
> Josh
>
> On Sun, 2009-04-19 at 01:27 +0200, the Adib wrote:
> > Hi Josh,
> >
> > we have a lot of bugs assigned to 0.47.
> > We need a new release target 0.48 in launchpad in order to properly
> > move the bugs to the next release if needed.
> >
> > HTH, Adib.
> > ...
> >
> > On Sun, Apr 19, 2009 at 1:18 AM, Joshua A. Andler <scislac@gm...> wrote:
> > > Hey All,
> > >
> > > In an effort to honor Bryce's work in this department for previous
> > > releases, I've liberally copied & pasted what he wrote last time. :)
> > >
> > > I know that it looks incredibly ambitious with the dates on there, but
> > > it IS doable provided people have the time and desire. I'd be interested
> > > to see what would happen if we plan a bug sprint weekend on May 9 & 10.
> > > We can have whoever is up for the challenge commit to it and see what we
> > > can pull off in two days.
> > >
> > > The following is based on previous release plans. Let me know if
> > > there's anything missing.
> > >
> > > 1. Open development.
> > > (Complete)
> > >
> > > 2. Chill. Development focuses on wrapping up.
> > > (In progress) No further refactoring.
> > > Identify 'make distcheck' issues
> > > Triage bug reports
> > > Run an About Screen contest
> > > First draft of Release Notes.
> > > Update tutorials and other docs
> > >
> > > 3. Frost. Most development complete.
> > > (May 1, 2009) Release Notes should be >90% filled in.
> > > Bug Hunt: 500 points
> > > Post inkscape-0.47-alpha.tar.gz
> > >
> > > 4. Feature Freeze. No further development work.
> > > (May 15, 2009) Disable features that can't be finished in time.
> > > Focus on critical bug fixing.
> > > Finalize all tutorials, docs, etc.
> > > Finalize all extensions.
> > > Translators create translations.
> > > Inkscape must pass 'make distcheck'
> > > Post inkscape-0.47-beta.tar.gz
> > >
> > > 5. Hard freeze. Only release wardens can commit to mainline.
> > > (May 25, 2009) No further string changes.
> > > Focus on release-critical bug fixing.
> > > Finalize translations, release notes, etc.
> > > Packagers test creating pkgs of the -beta release.
> > > Post inkscape-0.47-rc1.tar.gz
> > >
> > > 6. Branch. Establish the Stable Branch for release
> > > (June 5, 2009) Complete any late-late-late work.
> > > Final verification of packaging, release notes,
> > > docs, etc.
> > > Publish more release candidates until ready for
> > > release.
> > > Plan 0.47.1+ release(s), if needed
> > >
> > > 7. Release. Post inkscape-0.47.tar.gz
> > > (June 15, 2009) Post packages
> > > Post official announcements
> > >
> > > 8. Open development.
> > >
> > >
> > > I know it is a radically short timeframe, especially given how long 0.46
> > > took. However, our last few releases have been dragged out to a painful
> > > degree. Honestly, it seems like most people loathe the process now.
> > > So... let's rip the bandaid off and just make it happen. We can modify
> > > the schedule at any point of course, but we need to address our biggest
> > > issues IMMEDIATELY to attempt to keep the dates as close as possible.
> > >
> > > This is doable. We're good, we're smart, we're competent, and we have
> > > the resources... we just need to be focused to make this happen.
> > >
> > > Cheers,
> > > Josh
> > >
> > > P.S. As all can see, I'm attacking the bug tracker... I hope other
> > > non-coders will contribute to preparing the bug tracker for the bug hunt
> > > too (let's free up the bug fixers time to actually fix things, rather
> > > than wade through the current mess).
> > >
> > >
> > > ------------------------------------------------------------------------------
> > > Stay on top of everything new and different, both inside and
> > > around Java (TM) technology - register by April 22, and save
> > > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> > > 300 plus technical and hands-on sessions. Register today.
> > > Use priority code J9JMT32. http://p.sf.net/sfu/p
> > > _______________________________________________
> > > Inkscape-devel mailing list
> > > Inkscape-devel@li...
> > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> > >
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@li...
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel

About SourceForge

Find Software

Develop Software

Community

Help

Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use