Great idea. For those interested in helping the documentation side of this you might find the task oriented documenation that the Rave project developed during incubation useful. This has already been successfully adopted by at least two other podlings.
Of course it is project and build tool specific but as a template for other projects to adopt and adapt it may be useful. http://rave.apache.org/release-management.html On 26 July 2012 15:10, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > Hi, > > The Incubator ships about half a dozen releases each month on average, > but our release process is notoriously lengthy, fraught with problems, > and badly documented. If this was any other project, we'd have had a > well-oiled release process in place already years ago. > > Much of our extra release overhead can of course be attributed to the > high release manager turnaround (ideally nobody would make more than > one or at most a few incubating releases) and the different > requirements (source layout, build process, packaging style, > distribution channels, etc.) of different podlings. However, there's > much that we could do that so far hasn't been done or has been > sidetracked. For example, our current release guide [1] is the result > of quite a bit of work, but without a clear vision accompanied with a > process of incremental improvements it's become a mess that few people > read, let alone understand. > > I'd like to start fixing this by forming a "release task force" of a > handful of volunteers who are ready to invest an hour or two per week > to work on a) helping podlings get their releases out, b) migrating > /dist/incubator to svnpubsub by the end of this year as requested by > infra, c) improving related documentation, and d) proposing updates to > the Incubator release policy if needed to streamline the process. In > concrete terms I'd like the task force to 1) be the first port of call > for podlings who're failing to get enough +1s from their mentors and > 2) to contribute a short updates (one sentence to one paragraph) on > their progress for inclusion in the monthly Incubator board reports. > > Anyone interested? > > [1] http://incubator.apache.org/guides/releasemanagement.html > > BR, > > Jukka Zitting > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
