[Cosmo-dev] Cosmo 0.7.1 release plan

[Mikeal Rogers]

A few things.

A bug in linux firefox is blocking the use of the windmill profile  
for launching the browser. We also don't currently have support to  
setting Safari's proxy (it uses the system proxy settings). Both of  
these issues can be worked around on tbox by making the default  
configuration for those browsers on those boxes be setup to use  
windmill with minimal code changes in windmill.

-Mikeal

On Sep 4, 2007, at 5:45 PM, Adam Christian wrote:

> For full automated coverage of the UI, we will need the following:
> 	Another box configured to run the tests against IE 6. (Correct bear?)
>
> 	Two windmill bugs:
> 		http://t0asted.com/trac/ticket/75
> 		http://t0asted.com/trac/ticket/76
> 	
> 	When we reinstate our support of Safari we will need:
> 		http://t0asted.com/trac/ticket/3
>
> Adam
>
> On Sep 4, 2007, at 5:34 PM, Mike wrote:
>
>> I don't think I came across totally clear based on the IRC  
>> convesation I just had with Ted:
>>
>> The 0.7.1 branch will happen tomorrow - the dev team will start  
>> fixing 0.7.1 targeted bugs.
>>
>> When QA starts working on 0.7.1, the 0.7.2 branch will be created.  
>> Any changes to 0.7.1 made after the 0.7.2 branch will need to be  
>> merged forward.
>>
>> Once 0.7.1 is closed the cycle repeats with 0.7.2 and so on
>>
>> Hopefully this is clearer and Im getting what the dev team is  
>> trying to do :)
>>
>> On Sep 4, 2007, at 8:26 PM, Mike wrote:
>>
>>>
>>> On Sep 4, 2007, at 7:55 PM, Ted Leung wrote:
>>>
>>>> - We've only seen one proposal for how to manage branchng, so  
>>>> we're going to do that one, which is to base the 0.7.x branches  
>>>> off of 0.7.   We will merge the changes from 0.7.1 into the  
>>>> trunk when 0.7.1 releases, but we will also merge them into  
>>>> 0.7.2 as soon as QA begins so that 0.7.2 development can  
>>>> proceed.   It is going to be important to keep the .7.x branches  
>>>> and the trunk in buildable/releasable states.
>>>
>>> I will be able to branch 0.7.1 on demand (well, given an hour's  
>>> notice)
>>>
>>> The plan looks doable - with the caveat that we will all be  
>>> tweaking as we go along.
>>>
>>> My thoughts are that as 0.7.x fixes are applied I should also be  
>>> seeing the patches being applied to trunk and that as soon as  
>>> 0.7.x is signed off by QA I will need to create a 0.7.x+1 branch  
>>> and close 0.7.x
>>>
>>> When each branch is created is really up to the dev team.
>> ---
>> Bear
>>
>> Build and Release Engineer
>> Open Source Applications Foundation (OSAF)
>> bear at osafoundation.org
>> http://www.osafoundation.org
>>
>> bear at code-bear.com
>> http://code-bear.com
>>
>> PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29
>>
>>
>> _______________________________________________
>> 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