Hi J-S, On Sun, Jun 1, 2008 at 9:37 PM, Jean-Sébastien Guay <[EMAIL PROTECTED]> wrote: > So I think in addition to all you said in the previous message (and with > which I agree), making a few point releases between stable releases would > help people keep up to date more easily.
This easy part is deciding that 2.stable.patch releases are valuable. The harder part is having the manpower to build and maintain them - I am way overstretched as is, taking on more work is not viable for me personally. If we can find volunteers to take on 2.stable.patch release maintenance then it'll make this possible, and should make the project run more smoothly once we are all settled in the new roles. If we are to make these new 2.stable.patch releases with the assistance of volunteers then we'll need to make this role as easy as possible. For instance Documentation of the steps that we take to make a release, sharing scripts that make releases (build them in to CMake even?). Other items like build farms that test the build of the various branches would be useful would make it easier - something that a maintainer can leverage (rather than maintain). We needn't go the whole hog right away, but take baby steps in this direction. My thought that the maintainer should each stable series should be something that could alternate, so one engineer takes on 2.4.x, another takes on 2.6.x when it comes out etc, but I guess if could be tackled by one person that takes on several stable releases if the load is low. In general I'd expect the load to be relatively light compared to the work required maintaining trunk and converging to the initial stable release. The existence of stable.patch releases does also involve the community in testing, and maintainers of the binaries for different platforms, so perhaps one should just be a team, with a different member taking the lead as the overall maintainer of a stable releases, or perhaps the stable release maintainer is an outside who provides the base for the platform maintainers. I'd like feedback from the community on how we can make this all happen. The initial stab at doing this will require coordination from me and the first volunteer/group of volunteers, so please ask your questions about what the role would involve - we can put up a page on the wiki for this. To this end I've created two new pages on the wiki, under the Community/Tasks section : http://www.openscenegraph.org/projects/osg/wiki/Community/Tasks/StableReleases and http://www.openscenegraph.org/projects/osg/wiki/Community/Tasks/DeveloperReleases I've filled in a little of the StableReleases. Robert. Robert. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
