[cosmo-dev] steps to push new cosmo release out

[Nitin Gupta]

Hi Randy,

If you need, I can request one resource from my team for the testing of the
Cosmo releases. My team does not have QA specialists but we do have some
freshers who would be interested in learning different testing technologies.
I hope that should help both of us. We get the knowledge and you get the
work.

Best Regards,
Nitin

-----Original Message-----
From: cosmo-dev-bounces at lists.osafoundation.org
[mailto:cosmo-dev-bounces at lists.osafoundation.org] On Behalf Of Randy
Letness
Sent: Friday, January 18, 2008 1:18 AM
To: Cosmo Dev Mailing List
Subject: [cosmo-dev] steps to push new cosmo release out

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.

-Randy


_______________________________________________
cosmo-dev mailing list
cosmo-dev at lists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-dev