Hi Dor, I want to stress that the transition was from an Apache Incubator subproject to an Apache TLP. The individual committers and PMC members in the Geode community will continue to drive the project forward.
Anthony > On Nov 23, 2016, at 1:03 AM, Dor Ben Dov <dor.ben-...@amdocs.com> wrote: > > Anthony, > > Are you (all pivotal developers / architects) who are here in the community > will now leave once this being managed by > Itself or are you continuing to contribute? > Regards, > Dor > > -----Original Message----- > From: Anthony Baker [mailto:aba...@pivotal.io] > Sent: יום ג 22 נובמבר 2016 16:44 > To: geode <d...@geode.incubator.apache.org> > Subject: Re: The next release (v1.1.0) > > Transitioning from an incubating project to a top-level project means we keep > doing exactly what we’ve been doing—except that now the project is > responsible for managing itself. We will be transitioning a few resources > such as mailing lists and git repos to reflect that we are no longer an > incubator subproject. > > See http://incubator.apache.org/guides/graduation.html. > > Anthony > >> On Nov 21, 2016, at 11:57 AM, Dor Ben Dov <dor.ben-...@amdocs.com> wrote: >> >> Anthony, >> >> What are the actual implications of this transition to the tlp ? >> >> Regards, >> Dor >> >> -----Original Message----- >> From: Anthony Baker [mailto:aba...@pivotal.io] >> Sent: יום ב 21 נובמבר 2016 19:26 >> To: dev@geode.apache.org >> Subject: The next release (v1.1.0) >> >> Now that graduation is done (!!), we need to organize our next release. I >> propose we focus on completing the transition to TLP and cleaning up >> “incubating" references. The sequence would look something like this: >> >> 1) Transition the git repo, mailing lists, etc. >> 2) Update incubating references in source, docs, website, wiki, … >> 3) Do a release. >> >> Thoughts? >> >> We need a release manager. Any volunteers? >> >> Also, we need to rename the JIRA version from 1.1.0-incubating to 1.1.0. >> Can someone with JIRA karma help? >> >> Anthony >> >> >> This message and the information contained herein is proprietary and >> confidential and subject to the Amdocs policy statement, you may >> review at http://www.amdocs.com/email_disclaimer.asp > > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > you may review at http://www.amdocs.com/email_disclaimer.asp
