Just a weekly check-in on the alpha release activities. Are there any updates 
on:
- GEODE-77 [Bruce]: Any ETA established for this?
- GEODE-18 [Anthony] Any update from the patch that was submitted?

Thanks,
Nitin
________________________________________
From: Anthony Baker <[email protected]>
Sent: Friday, October 9, 2015 2:08 PM
To: [email protected]
Subject: Re: Geode Release 1.0.0

Per gitflow, we establish a release-X branch for stabilization from develop.  
Once we are ready we merge release-X to master (and develop).  The actual 
release tag is done on master.

Anthony

> On Oct 9, 2015, at 1:59 PM, Nitin Lamba <[email protected]> wrote:
>
> Works for me. I've updated the Agile board to create a (alpha1) release and 
> staging sprint.
>
> One question on git branching - should we mark alpha1 from develop or master? 
> I'm guessing we'll wait for GEODE-77 merge before we can start that process...
>
> -Nitin
>
> ________________________________________
> From: Anthony Baker <[email protected]>
> Sent: Friday, October 9, 2015 1:46 PM
> To: [email protected]
> Subject: Re: Geode Release 1.0.0
>
> Can you change the sprint name to match the version we discussed previously 
> (alpha1)?.  I think we’re going to have a series of alpha releases so this 
> gives us room to grow.
>
> I suggest working towards a monthly release cadence.  To that end, let’s pare 
> scope down to the bare minimum.  The first release will get us through IP 
> issues and flex some Apache processes we haven’t exercised before.  We can 
> always fix things (website, javadocs, etc) in subsequent releases.  Things we 
> have to fix, IMO:
>
>        GEODE-77
>        GEODE-18
>
> Everything else can get pushed to alpha2.  Thoughts?
>
> Anthony
>
>
>> On Oct 9, 2015, at 12:09 PM, Nitin Lamba <[email protected]> wrote:
>>
>> Thanks Dan,
>>
>> All,
>>
>> The Agile Dashboard is LIVE!!!
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92&view=planning
>>
>> I've created a placeholder sprint for the ALPHA release and moved certain 
>> issues that are targeted for it (GEODE-77/ 18/ 386). Please comment on the 
>> Wiki or suggest any other items missing from scope.
>>
>> I'll start a weekly update thread where committers/ contributors can 
>> chime-on on progress made, and preferably ETA for when this will get 
>> completed. We have to pick one of two options for releases:
>> - Time-based: Once a month/quarter until TLP, more spaced-out subsequently
>> - Scope-based: Cut a release once scoped features are completed
>>
>> Thoughts/ suggestions?
>>
>> -Nitin
>>
>> ________________________________________
>> From: Dan Smith <[email protected]>
>> Sent: Tuesday, October 6, 2015 2:59 PM
>> To: [email protected]
>> Subject: Re: Geode Release 1.0.0
>>
>> I added another item to this list that I just noticed.
>>
>> GEODE-386 - Change xsd namespace to apache.
>>
>> -Dan
>>
>> On Wed, Sep 30, 2015 at 12:24 AM, Nitin Lamba <[email protected]> wrote:
>>
>>> Thanks Anthony! I've fixed the reference.
>>>
>>> Please feel free to add any other items that you think are missing...
>>>
>>> Nitin
>>> ________________________________________
>>> From: Anthony Baker <[email protected]>
>>> Sent: Tuesday, September 29, 2015 11:39 PM
>>> To: [email protected]
>>> Subject: Re: Geode Release 1.0.0
>>>
>>> Thanks Nitin, that looks great!
>>>
>>> I think the row for “License check (RAT tool)”  should be referring to
>>> GEODE-18 not GEODE-61 though.
>>>
>>> Anthony
>>>
>>>> On Sep 30, 2015, at 8:06 AM, Nitin Lamba <[email protected]> wrote:
>>>>
>>>> All,
>>>>
>>>> As a follow-up of the release thread few weeks ago, I've created a
>>> release page for 1.0.0:
>>>>
>>> https://cwiki.apache.org/confluence/display/GEODE/1.0.0+%28First%29+Release
>>>>
>>>> Plan to keep adding items to this list and eventually JIRA tasks. We
>>> should probably discuss the coordination process briefly in the Geode
>>> Clubhouse this week.
>>>>
>>>> Comments/ suggestions welcome!
>>>>
>>>> Thanks,
>>>> Nitin
>>>>
>>>
>

Reply via email to