Home
The Toolkit for Online Communities
17598 Community Members, 0 members online, 5020 visitors today
Log In Register
OpenACS Home : Forums : OpenACS Development : Release Management

Forum OpenACS Development: Release Management

Icon of envelope Request notifications

Collapse
Posted by Joel Aufrecht on
I'd like to better come up to speed with the release management process. Because I added files in an uncordinated way during the end of the release cycle, there are some problems with docs in 4.6.2 final.

Do you use some sort of release checklist? A cursory inspection on the web site didn't uncover anything, but I seem to remember seeing stuff like that before.

In the past I've used sign-off sheets where each group (test, doc, dev, etc) approves a release before it can proceed. Something like that within ETP might be helpful, possibly with email alerts. Here's an incomplete list of steps:

  1. Target date set by release manager
  2. Cvs checkin freeze
  3. Test team verifies no blocking bugs
  4. Documenter verifies docs updated
  5. Candidate tarball rolled
  6. Full install and smoke test of tarball using documented install instructions
  7. Tarball released to web
  8. Docs updated on web
  9. Announcement posted

Obviously an automated install and smoke test on a daily basis would be nice and would drastically improve build quality but I'm contracting at a billion-dollar software company that can't manage to do that well so I guess us Open-Source volunteers can take another few months to get to that point.

Collapse
2: Re: Release Management (response to 1)
Posted by Jeff Davis on
There was a thread on it with my checklist (which was more final release tasks/QA than full release management)
Collapse
3: Re: Release Management (response to 1)
Posted by Lamar Owen on
FWIW, the PostgreSQL group still has difficulty with this, since things are pretty ad hoc there too.  But is that really a problem for a 'hobby' package?  Well, I realize we're not a 'hobby' package per se; yet we're not a commercial toolkit either.  Volunteer help comes at a cost -- that of a general lack of accountability.  You do get what you pay for: TANSTAAFL.  But I enjoy the freedom I have and am willing to stake my Intranet sites on this toolkit, even if I have to wring out the bugs myself.