Of course everyone’s welcome to participate. Best way to start is to introduce 
yourself over at d...@geode.apache.org and ask your questions there. 

Anthony 

> On Mar 12, 2020, at 12:51 PM, Claude Edney <claude.ed...@yahoo.com.invalid> 
> wrote:
> 
>  Hey Anthony, Can we as engineers take alook at it before it releases? Are 
> there any links to view you can send me, or source code files we can 
> see?Thanks
>    On Thursday, March 12, 2020, 12:55:51 PM EDT, Anthony Baker 
> <aba...@pivotal.io> wrote:  
> 
> Geode nominally follows a quarterly release cycle, in conjunction with “don’t 
> release until it’s ready”.  Based on past experience we allow a period of 
> stabilization time to shake out issues on the release branch before we create 
> release candidates for voting.
> 
> Anthony
> 
> 
>> On Mar 12, 2020, at 4:54 AM, Jarek Potiuk <ja...@potiuk.com> wrote:
>> 
>> I think so far it is "release when we are ready" schedule. This is
>> something that we will be discussing on improving for our Airflow 2.0
>> schedule most likely so maybe that will be a good time to discuss it. We
>> will likely do some analysis of current approach, pros and cons of
>> different approaches - maybe you can join the discussion then? Just watch
>> the devlist.
>> 
>> J.
>> 
>> 
>>> On Thu, Mar 12, 2020 at 11:10 AM Teia Gatling <tgatl...@gwmail.gwu.edu>
>>> wrote:
>>> 
>>> ALCON,
>>> 
>>> I am currently a doctoral candidate with the George Washington University
>>> working towards a Doctorate in Engineering Management.  My current research
>>> topic surrounds the release time of software updates.  Is there a method
>>> used to determine the current release schedules in support of Apache
>>> products that can be shared?
>>> 
>>> If available, I would be interested in discussing my topic further with
>>> you.  Please let me know if this is possible.
>>> 
>>> Thanks,
>>> Teia Gatling
>>> GWU SEAS
>>> Engineering Management
>>> 
>> 
>> 
>> -- 
>> +48 660 796 129
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to