Re: [hugin-ptx] 2011.0 Release Plan
On Mon 28-Feb-2011 at 19:36 -0500, Yuval Levy wrote: I was going to say that we shouldn't be supporting anything older than the current stable release, but if we continue releasing at twice the rate of Ubuntu (and Fedora etc...) then there will always be people using the two most recent releases. There is plenty of evidence around that deviating from release early release frequently is nearly lethal, including the recent experience of Gimp, our own experience prior to 2009; the FreeBSD experience with 5.0 in 2000-2003. Yes the fast release schedule has been a good thing, I just couldn't do the work to make it happen. Releasing often gives contributors the chance to see their stuff get general distribution, but also works against half-finished stuff from being pushed into the trunk before it is ready. -- Bruno -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] 2011.0 Release Plan
On February 28, 2011 04:54:37 pm Bruno Postle wrote: On Sun 27-Feb-2011 at 18:05 -0500, Yuval Levy wrote: Specific to the situation now: - default and 2011.0 are in active development - 2010.4 and 2010.2 are supported (i.e. we would issue a patched version if the need arises) - anything older than that is unsupported. Any opinions about this support policy? I was going to say that we shouldn't be supporting anything older than the current stable release, but if we continue releasing at twice the rate of Ubuntu (and Fedora etc...) then there will always be people using the two most recent releases. I wish we can do twice the rate of Ubuntu, Fedora, etc. Right now we are at 1.5x, and we have more or less caught up to the features queue. There is plenty of evidence around that deviating from release early release frequently is nearly lethal, including the recent experience of Gimp, our own experience prior to 2009; the FreeBSD experience with 5.0 in 2000-2003. Yuv signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] 2011.0 Release Plan
On February 26, 2011 06:05:08 pm Bruno Postle wrote: If necessary libpano13-2.9.18_beta1 could be relabeled as 'final' if we need it for a Hugin release (since it seems to be ok). Thanks, that would be very much appreciated. As far as Hugin is concerned, the current cpfind is so much better than anything we had before that I'd almost recommend people use a snapshot rather than 2010.4.0. Yes, the beta tarball is out, and Thomas and Darko are hard at work fixing the rough edges of the new overview. Nothing prevents us from getting ahead of schedule if there is the motivation to do it. I updated the documentation of the release process [0] and I cleaned up the tags in Mercurial (all tags from 2009.2 onward are now consistently named). We close development branches and I was wondering if we should also close unsupported release branches? In my documentation I suggest that: - only the latest release and the active development branches are in active development - only the previous two releases are supported - older releases are obsolete Specific to the situation now: - default and 2011.0 are in active development - 2010.4 and 2010.2 are supported (i.e. we would issue a patched version if the need arises) - anything older than that is unsupported. Any opinions about this support policy? Yuv [0] http://wiki.panotools.org/Development_of_Open_Source_tools#Release signature.asc Description: This is a digitally signed message part.
[hugin-ptx] 2011.0 Release Plan
Hi all, I have just entered the 2011.0 Release Plan into Launchpad [0] and documented release planning [1]. The intention is to make the plan as predictable as possible so that contributors can plan for their own contributions (e.g. translations and bug fixes) and distributors can plan for the binary builds. Like with the last release cycle, it would be great if binary releases follow on the heels of the tarball releases. Feedback to the plan is welcome. I have set the final release well out in the future. It will depend amongst others also on the final release of Libpano 2.9.18 and other factors that are not fully predictable at the moment. As usual, the release will happen when it is ready and the provided time estimates are just an indication and are not guaranteed. Let's get it rolling! Yuv [0] https://launchpad.net/hugin/2011.0 [1] http://wiki.panotools.org/Development_of_Open_Source_tools#Release_Plan signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] 2011.0 Release Plan
On Sat 26-Feb-2011 at 17:11 -0500, Yuval Levy wrote: Feedback to the plan is welcome. I have set the final release well out in the future. It will depend amongst others also on the final release of Libpano 2.9.18 and other factors that are not fully predictable at the moment. If necessary libpano13-2.9.18_beta1 could be relabeled as 'final' if we need it for a Hugin release (since it seems to be ok). It would be nice to merge the new libpano13 test suite, but this needs some work. As far as Hugin is concerned, the current cpfind is so much better than anything we had before that I'd almost recommend people use a snapshot rather than 2010.4.0. -- Bruno -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
