[cosmo-dev] steps to push new cosmo release out
andre_mueninghoff at fastmail.fm
Thu Jan 17 12:31:27 PST 2008
I would be willing to some functional "smoke-testing" after the
automated tests are passing, if that would be helpful.
On Thu, 17 Jan 2008 13:47:35 -0600, "Randy Letness"
<randy at osafoundation.org> said:
> There have been a few bugs fixed, mostly ones seen on during hub usage,
> and some security fixes, so its seems worthwhile to push out a cosmo
> 0.12 release, which would be a bug fix only release, no new features, no
> schema changes. Now that we have reduced resources, we need to figure
> out what that involves. In the past, we would branch the trunk and
> spin a release candidate from the branch. That candidate would be
> tested by verifying any bugs fixed in the release, running any automated
> tests, and holding irc qa sessions, before being certified for release.
> We no longer have qa resources, so what steps should we take to verify
> the code is ready for release? At a minimum we verify fixed bugs and
> get all automated tests passing. That should probably be enough for a
> bugfix release like 0.12. Any other ideas? I know in the past all
> testing was done on lab.osaf.us, which is setup exactly like hub. I
> need to figure out how to update the server with a build.
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
More information about the cosmo-dev