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

[Sheila Mooney]

I am also available to help with any end-user testing.

On Jan 17, 2008, at 11:54 AM, Brian Kirsch wrote:

> Hi Randy,
> See comments in-line.
>
> -Brian
>
> On Jan 17, 2008, at 9:47 AM, Randy Letness wrote:
>
>> 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.
>
> I am available to help with verification testing. We are now our own  
> QA team so let me know how I can be of assistance.
>
> It also affords me an opportunity to continue learning about the  
> internals of the Chandler Server (Cosmo).
>
>> 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
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev