[kepler-dev] Code Freeze Today

Chad Berkley berkley at nceas.ucsb.edu
Mon Feb 1 09:40:32 PST 2010


Just the Kepler suite modules I think.



On Feb 1, 2010, at 9:38, Timothy McPhillips <tmcphillips at mac.com> wrote:

> Hi Chad,
>
> What would the SVN branch be over?  Everything in kepler/trunk/,  
> including all modules?
>
> Thanks,
>
> Tim
>
> On Feb 1, 2010, at 8:51 AM, Chad Berkley wrote:
>
>> Hi,
>>
>> I'm just checking in one last time to see if there is any objection  
>> to doing the code freeze today.  The bug list is looking pretty  
>> good and I think we got all of the features in that we meant to.   
>> If there is anything outstanding that you think warrants pushing  
>> the code freeze, please let me know ASAP.
>>
>> Because of our module system, there are two different ways we can  
>> do the release branch.  We can do an old fashioned SVN branch, or  
>> we can just create a kepler-2.0.0 release suite with versioned sub- 
>> modules.  What does everyone think is the best route to go?  I  
>> would probably lean toward an SVN branch, myself, but I think there  
>> are other opinions out there.
>>
>> chad
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>


More information about the Kepler-dev mailing list