On Mon, 2013-09-23 at 19:27 +0000, Bryce W. Harrington wrote:
What needs done, just get latest pixman and cairo into the ppa? I can take care of that if no one else is. What fix is needed for the build system, just checking the pixman/cairo version in autoconf?
I believe it is a matter of taking pixman/cairo (unreleased) version 1.13 (right?) making sure we have that available in our package and making sure our builds require it.
Has anyone talked about doing an alpha release? Esp. with the just landed GSoC work, would be a good way to get it out in front of people to shake out any bugs that crept in through that.
Technically every version of Inkscape so far has been alpha. No v1.0 because we're not feature complete. And I'd also hazard that the trunk build ppa system is equivalent to an alpha build.
What perhaps we need is a mellow freeze and a beta release. Thoughts?
Martin,
On 23-9-2013 22:55, Martin Owens wrote:
On Mon, 2013-09-23 at 19:27 +0000, Bryce W. Harrington wrote:
Has anyone talked about doing an alpha release? Esp. with the just landed GSoC work, would be a good way to get it out in front of people to shake out any bugs that crept in through that.
Technically every version of Inkscape so far has been alpha. No v1.0 because we're not feature complete. And I'd also hazard that the trunk build ppa system is equivalent to an alpha build.
I think Bryce has a good point that it is worthwhile to bring latest trunk under the attention of many users. Indeed, trunk build seems fine to me. We can post a recent build for all popular platforms (more prominently) on our main page, and send a mail about it to the inkscape-user list. What do you think ~suv?
(sidenote: the comment that "technically" every version of Inkscape has been alpha, I think that's not true)
cheers, Johan
On Mon, Sep 23, 2013 at 2:19 PM, Johan Engelen <jbc.engelen@...2592...> wrote:
(sidenote: the comment that "technically" every version of Inkscape has been alpha, I think that's not true)
This is one of the reasons why I've brought up changing our outward facing version number a handful of times. Different perceptions and understanding of the significance of the number.
Cheers, Josh
On Mon, 2013-09-23 at 14:22 -0700, Josh Andler wrote:
This is one of the reasons why I've brought up changing our outward facing version number a handful of times. Different perceptions and understanding of the significance of the number.
I guess after 0.49 we can decide if we want 1.0, 5.0, 0.50 or what ever number else. I believe the argument against is because we're not complete in our support of svg... although this is a bit like the wine project that only got to 1.0 when they decided to stop aiming for perfect windows api coverage.
But this isn't important right now. Thanks for the good list of items, I think we should start an about screen contest right away.
Martin,
I think we should have whatever GSoC work we're going to land this cycle in trunk, get the test builds for Win & OSX (if doable) up in a public place and then we can start the contest.
Cheers, Josh
On Mon, Sep 23, 2013 at 2:41 PM, Martin Owens <doctormo@...400...> wrote:
On Mon, 2013-09-23 at 14:22 -0700, Josh Andler wrote:
This is one of the reasons why I've brought up changing our outward facing version number a handful of times. Different perceptions and understanding of the significance of the number.
I guess after 0.49 we can decide if we want 1.0, 5.0, 0.50 or what ever number else. I believe the argument against is because we're not complete in our support of svg... although this is a bit like the wine project that only got to 1.0 when they decided to stop aiming for perfect windows api coverage.
But this isn't important right now. Thanks for the good list of items, I think we should start an about screen contest right away.
Martin,
Here is roughly how the previous releases were done (I just looked up an old email):
1. Open development.
2. Chill. Development focuses on wrapping up. 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. Release Notes should be >90% filled in. Bug Hunt: 500 points Post inkscape-0.XX-alpha.tar.gz
4. Feature Freeze. No further development work. 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.XX-beta.tar.gz
5. Hard freeze. Only release wardens can commit to mainline. 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.XX-rc1.tar.gz
6. Branch. Establish the Stable Branch for release Complete any late-late-late work. Final verification of packaging, release notes, docs, etc. Publish more release candidates until ready for release. Plan 0.XX.1+ release(s), if needed
7. Release. Post inkscape-0.XX.tar.gz Post packages Post official announcements
8. Open development.
Obviously, there may be better ways to go about it, but this is the outline we've followed.
Cheers, Josh
On Mon, Sep 23, 2013 at 1:55 PM, Martin Owens <doctormo@...400...> wrote:
On Mon, 2013-09-23 at 19:27 +0000, Bryce W. Harrington wrote:
What needs done, just get latest pixman and cairo into the ppa? I can take care of that if no one else is. What fix is needed for the build system, just checking the pixman/cairo version in autoconf?
I believe it is a matter of taking pixman/cairo (unreleased) version 1.13 (right?) making sure we have that available in our package and making sure our builds require it.
Has anyone talked about doing an alpha release? Esp. with the just landed GSoC work, would be a good way to get it out in front of people to shake out any bugs that crept in through that.
Technically every version of Inkscape so far has been alpha. No v1.0 because we're not feature complete. And I'd also hazard that the trunk build ppa system is equivalent to an alpha build.
What perhaps we need is a mellow freeze and a beta release. Thoughts?
Martin,
October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (3)
-
Johan Engelen -
Josh Andler -
Martin Owens