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

[Travis Vachon]

Ok, I've run the windmill tests on OSX Firefox, but should probably do  
some testing in other environments as well. I ran into a little  
wonkiness that I'm going to look into tomorrow, but based on the run I  
saw I think a collaborative testing session this week would be time  
well spent.

-Travis

On Jan 22, 2008, at 3:26 PM, Jared Rhine wrote:

>> I'd like to have all current automated tests passing before the  
>> session to shake out any obvious bugs.
>
> Yes, solid idea.  We've seen a number of instances where a  
> collaborative session is kinda ruined because there are known bugs,  
> or where 5 minutes in we find a blocker and nobody is really able to  
> test well.  In those instances, we end up repeating.  So wherever  
> possible, we should have the automated tests pass before any IRC  
> session.  It's also best to have even the manual checks finished  
> before IRC sessions, for the same reason.
>
>> 1. Verify snarf works as is with no configuration changes using  
>> embedded Derby database.
>> 2. Make configuration changes in $OSAFSRV_HOME/tomcat/conf/Catalina/ 
>> localhost/chandler.xml (change db to mysql for instance) and verify  
>> things work
>>
>> We should do a checkpoint build of the server bundle to verify 1  
>> and 2.   Any ideas on how to do that?
>
> Not really.  It's probably close to the same process as an RC, but  
> we haven't run through that yet.  Lemme go look at docs.  I'd guess  
> that it's mostly the same as just building regularly, and you use  
> the tarball artifact as the release itself.  If so, I think basic  
> validation of the tarball could be done against trunk.
>
> -- Jared
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev