RE: The next release (v1.1.0)
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
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 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
RE: The next release (v1.1.0)
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 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 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
Re: The next release (v1.1.0)
+1 to getting this stuff cleaned up. I'd really like to see us get into a more regular release cadence. I renamed 1.1.0-incubating to 1.1.0 in JIRA. Dor - I don't think any of the active committers are planning on leaving. We're working on this project because we want it to thrive, and graduation is one more thing that will help it grow! -Dan On Wed, Nov 23, 2016 at 1:03 AM, Dor Ben Dov 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 > 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 > 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 >
Re: The next release (v1.1.0)
+1... We all want this project to be the best it can be. On 11/23/16 09:07, Dan Smith wrote: Dor - I don't think any of the active committers are planning on leaving. We're working on this project because we want it to thrive, and graduation is one more thing that will help it grow!
Re: The next release (v1.1.0)
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 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 > 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 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
Re: The next release (v1.1.0)
Hi Anthony Thanks for the answer. Dor Original Message Subject: Re: The next release (v1.1.0) From: Anthony Baker Date: 25 בנוב' 2016, 16:44 To: dev@geode.apache.org 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 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 > 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 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
Re: The next release (v1.1.0)
I did some JIRA housekeeping today [1]: - Closed 1.0.0-incubating.M3 sprint - Created 1.1.0 sprint and moved JIRAs identified with 'Fix Versions' into scope - Created a new Quick Filter for CI Failures Is there a separate thread for discussing 1.1.0 scope or should we start a new one? Thanks, Nitin [1] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92&view=planning.nodetail On Fri, Nov 25, 2016 at 12:45 PM, Dor Ben Dov wrote: > Hi Anthony > > Thanks for the answer. > > Dor > > Original Message ---- > > Subject: Re: The next release (v1.1.0) > > From: Anthony Baker > > Date: 25 בנוב' 2016, 16:44 > > To: dev@geode.apache.org > > 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 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 > > 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 > 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 > >
Re: The next release (v1.1.0)
FYI, I started work on GEODE-2156 to remove references to “incubating”. Feel free to jump in on the feature branch (feature/GEODE-2156). I don’t plan to merge this to develop until the infrastructure changes are ready (see INFRA-12937). Anthony > On Nov 25, 2016, at 7:44 PM, Nitin Lamba wrote: > > I did some JIRA housekeeping today [1]: > - Closed 1.0.0-incubating.M3 sprint > - Created 1.1.0 sprint and moved JIRAs identified with 'Fix Versions' into > scope > - Created a new Quick Filter for CI Failures > > Is there a separate thread for discussing 1.1.0 scope or should we start a > new one? > > Thanks, > Nitin > [1] > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92&view=planning.nodetail
Re: The next release (v1.1.0)
Our last release was on October 25. I think we’re past due for another one! We’ve had lots of great contributions since 1.0.0-incubating and now that we’re are a top-level project we can drop the “-incubating” qualifier. I reviewed our open JIRA issues and would like to include the following in the release: GEODE-2142 - JSON license incompatibility We can update the NOTICE files and leave the JSON dependency alone (as long as we do another release before April 30). GEODE-1965 - backwards compatibility tests I’d like to make sure we haven’t broken anything since our last release. GEODE-2031 - versioned documentation Seems relatively straightforward? The remaining issues that are tagged with v1.1.0 [1] could be pushed to a following release IMO. Thoughts? Regarding the release manager, I can do the dirty work if no one else wants to volunteer :-) Anthony [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: > > 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 >
Re: The next release (v1.1.0)
Updates: 1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0. 2) Any volunteers to look at GEODE-2031 or GEODE-1965? 3) Are there other open issues that should be included in the release? 4) Last call for a release manager… :-) Thanks, Anthony > On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: > > Our last release was on October 25. I think we’re past due for another one! > We’ve had lots of great contributions since 1.0.0-incubating and now that > we’re are a top-level project we can drop the “-incubating” qualifier. > > I reviewed our open JIRA issues and would like to include the following in > the release: > > GEODE-2142 - JSON license incompatibility > We can update the NOTICE files and leave the JSON dependency alone (as > long as we do another release before April 30). > > GEODE-1965 - backwards compatibility tests > I’d like to make sure we haven’t broken anything since our last release. > > GEODE-2031 - versioned documentation > Seems relatively straightforward? > > The remaining issues that are tagged with v1.1.0 [1] could be pushed to a > following release IMO. Thoughts? > > Regarding the release manager, I can do the dirty work if no one else wants > to volunteer :-) > > Anthony > > [1] > https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: >> >> 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 >> >
Re: The next release (v1.1.0)
Re: 2) I'll take a look at GEODE-2031, versioning the documentation. On Mon, Jan 9, 2017 at 9:50 AM Anthony Baker wrote: > Updates: > > 1) I did a first round of changes on GEODE-2142, should be enough for > v1.1.0. > 2) Any volunteers to look at GEODE-2031 or GEODE-1965? > 3) Are there other open issues that should be included in the release? > 4) Last call for a release manager… :-) > > Thanks, > Anthony > > > > On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: > > > > Our last release was on October 25. I think we’re past due for another > one! We’ve had lots of great contributions since 1.0.0-incubating and now > that we’re are a top-level project we can drop the “-incubating” qualifier. > > > > I reviewed our open JIRA issues and would like to include the following > in the release: > > > > GEODE-2142 - JSON license incompatibility > > We can update the NOTICE files and leave the JSON dependency alone > (as long as we do another release before April 30). > > > > GEODE-1965 - backwards compatibility tests > > I’d like to make sure we haven’t broken anything since our last > release. > > > > GEODE-2031 - versioned documentation > > Seems relatively straightforward? > > > > The remaining issues that are tagged with v1.1.0 [1] could be pushed to > a following release IMO. Thoughts? > > > > Regarding the release manager, I can do the dirty work if no one else > wants to volunteer :-) > > > > Anthony > > > > [1] > https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: > >> > >> 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 > >> > > > >
Re: The next release (v1.1.0)
let me try it out this time. Any instruction to follow? Thanks.HItesh From: Anthony Baker To: dev@geode.apache.org Sent: Monday, January 9, 2017 9:49 AM Subject: Re: The next release (v1.1.0) Updates: 1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0. 2) Any volunteers to look at GEODE-2031 or GEODE-1965? 3) Are there other open issues that should be included in the release? 4) Last call for a release manager… :-) Thanks, Anthony > On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: > > Our last release was on October 25. I think we’re past due for another one! > We’ve had lots of great contributions since 1.0.0-incubating and now that > we’re are a top-level project we can drop the “-incubating” qualifier. > > I reviewed our open JIRA issues and would like to include the following in > the release: > > GEODE-2142 - JSON license incompatibility > We can update the NOTICE files and leave the JSON dependency alone (as > long as we do another release before April 30). > > GEODE-1965 - backwards compatibility tests > I’d like to make sure we haven’t broken anything since our last release. > > GEODE-2031 - versioned documentation > Seems relatively straightforward? > > The remaining issues that are tagged with v1.1.0 [1] could be pushed to a > following release IMO. Thoughts? > > Regarding the release manager, I can do the dirty work if no one else wants > to volunteer :-) > > Anthony > > [1] > https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: >> >> 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 >> >
Re: The next release (v1.1.0)
Thanks Hitesh! You will need to follow the instructions at https://cwiki.apache.org/confluence/display/GEODE/Release+Steps. The instructions will need to be updated since we do not need to go through the IPMC vote. Please make sure you have a GPG key as noted in the instructions. Anthony > On Jan 9, 2017, at 10:53 AM, Hitesh Khamesra > wrote: > > let me try it out this time. Any instruction to follow? > Thanks.HItesh > > > From: Anthony Baker > To: dev@geode.apache.org > Sent: Monday, January 9, 2017 9:49 AM > Subject: Re: The next release (v1.1.0) > > Updates: > > 1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0. > 2) Any volunteers to look at GEODE-2031 or GEODE-1965? > 3) Are there other open issues that should be included in the release? > 4) Last call for a release manager… :-) > > Thanks, > Anthony > > >> On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: >> >> Our last release was on October 25. I think we’re past due for another one! >> We’ve had lots of great contributions since 1.0.0-incubating and now that >> we’re are a top-level project we can drop the “-incubating” qualifier. >> >> I reviewed our open JIRA issues and would like to include the following in >> the release: >> >> GEODE-2142 - JSON license incompatibility >> We can update the NOTICE files and leave the JSON dependency alone (as >> long as we do another release before April 30). >> >> GEODE-1965 - backwards compatibility tests >> I’d like to make sure we haven’t broken anything since our last release. >> >> GEODE-2031 - versioned documentation >> Seems relatively straightforward? >> >> The remaining issues that are tagged with v1.1.0 [1] could be pushed to a >> following release IMO. Thoughts? >> >> Regarding the release manager, I can do the dirty work if no one else wants >> to volunteer :-) >> >> Anthony >> >> [1] >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC >> >>> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: >>> >>> 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 >>> >> > >
Re: The next release (v1.1.0)
Update: We are waiting on following tickets for first release candidate. 1. GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User Exception 2. GEODE-2277 client cache fails to deserialize a PdxInstance due to InternalGemFireError 3. GEODE-2031 Host documentation for releases 4. GEODE-1965 Create backward-compatibility unit test framework Thanks.HItesh From: Anthony Baker To: dev@geode.apache.org Sent: Monday, January 9, 2017 9:49 AM Subject: Re: The next release (v1.1.0) Updates: 1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0. 2) Any volunteers to look at GEODE-2031 or GEODE-1965? 3) Are there other open issues that should be included in the release? 4) Last call for a release manager… :-) Thanks, Anthony > On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: > > Our last release was on October 25. I think we’re past due for another one! > We’ve had lots of great contributions since 1.0.0-incubating and now that > we’re are a top-level project we can drop the “-incubating” qualifier. > > I reviewed our open JIRA issues and would like to include the following in > the release: > > GEODE-2142 - JSON license incompatibility > We can update the NOTICE files and leave the JSON dependency alone (as > long as we do another release before April 30). > > GEODE-1965 - backwards compatibility tests > I’d like to make sure we haven’t broken anything since our last release. > > GEODE-2031 - versioned documentation > Seems relatively straightforward? > > The remaining issues that are tagged with v1.1.0 [1] could be pushed to a > following release IMO. Thoughts? > > Regarding the release manager, I can do the dirty work if no one else wants > to volunteer :-) > > Anthony > > [1] > https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: >> >> 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 >> >
Re: The next release (v1.1.0)
Update: Three more ticket for first release candidate.. GEODE-2300 Document default names for start locator/server GEODE-2353 Verify no clear-text passwords in documentation GEODE-2282 Provide ability to sort field while creating pdxType for jSON document(Need to document system property) Thanks.HItesh From: Hitesh Khamesra To: "dev@geode.apache.org" Sent: Monday, January 16, 2017 12:35 PM Subject: Re: The next release (v1.1.0) Update: We are waiting on following tickets for first release candidate. 1. GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User Exception 2. GEODE-2277 client cache fails to deserialize a PdxInstance due to InternalGemFireError 3. GEODE-2031 Host documentation for releases 4. GEODE-1965 Create backward-compatibility unit test framework Thanks.HItesh From: Anthony Baker To: dev@geode.apache.org Sent: Monday, January 9, 2017 9:49 AM Subject: Re: The next release (v1.1.0) Updates: 1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0. 2) Any volunteers to look at GEODE-2031 or GEODE-1965? 3) Are there other open issues that should be included in the release? 4) Last call for a release manager… :-) Thanks, Anthony > On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: > > Our last release was on October 25. I think we’re past due for another one! > We’ve had lots of great contributions since 1.0.0-incubating and now that > we’re are a top-level project we can drop the “-incubating” qualifier. > > I reviewed our open JIRA issues and would like to include the following in > the release: > > GEODE-2142 - JSON license incompatibility > We can update the NOTICE files and leave the JSON dependency alone (as > long as we do another release before April 30). > > GEODE-1965 - backwards compatibility tests > I’d like to make sure we haven’t broken anything since our last release. > > GEODE-2031 - versioned documentation > Seems relatively straightforward? > > The remaining issues that are tagged with v1.1.0 [1] could be pushed to a > following release IMO. Thoughts? > > Regarding the release manager, I can do the dirty work if no one else wants > to volunteer :-) > > Anthony > > [1] > https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: >> >> 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 >> >
Re: The next release (v1.1.0)
Do we think we can get these done and get a release before the next board meeting (2/15)? I think it would be an excellent point on our report. Best Regards, --Mark On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra < hitesh...@yahoo.com.invalid> wrote: > Update: Three more ticket for first release candidate.. > > GEODE-2300 Document default names for start locator/server > GEODE-2353 Verify no clear-text passwords in documentation > GEODE-2282 Provide ability to sort field while creating pdxType for jSON > document(Need to document system property) > > Thanks.HItesh > > > > From: Hitesh Khamesra > To: "dev@geode.apache.org" > Sent: Monday, January 16, 2017 12:35 PM > Subject: Re: The next release (v1.1.0) > > Update: We are waiting on following tickets for first release candidate. > > 1. GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User > Exception > 2. GEODE-2277 client cache fails to deserialize a PdxInstance due to > InternalGemFireError > 3. GEODE-2031 Host documentation for releases > 4. GEODE-1965 Create backward-compatibility unit test framework > > Thanks.HItesh > > From: Anthony Baker > To: dev@geode.apache.org > Sent: Monday, January 9, 2017 9:49 AM > Subject: Re: The next release (v1.1.0) > > Updates: > > 1) I did a first round of changes on GEODE-2142, should be enough for > v1.1.0. > 2) Any volunteers to look at GEODE-2031 or GEODE-1965? > 3) Are there other open issues that should be included in the release? > 4) Last call for a release manager… :-) > > Thanks, > Anthony > > > > On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: > > > > Our last release was on October 25. I think we’re past due for another > one! We’ve had lots of great contributions since 1.0.0-incubating and now > that we’re are a top-level project we can drop the “-incubating” qualifier. > > > > I reviewed our open JIRA issues and would like to include the following > in the release: > > > > GEODE-2142 - JSON license incompatibility > > We can update the NOTICE files and leave the JSON dependency alone > (as long as we do another release before April 30). > > > > GEODE-1965 - backwards compatibility tests > > I’d like to make sure we haven’t broken anything since our last > release. > > > > GEODE-2031 - versioned documentation > > Seems relatively straightforward? > > > > The remaining issues that are tagged with v1.1.0 [1] could be pushed to > a following release IMO. Thoughts? > > > > Regarding the release manager, I can do the dirty work if no one else > wants to volunteer :-) > > > > Anthony > > > > [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G > EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20% > 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority% > 20DESC%2C%20created%20ASC > > > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: > >> > >> 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 > >> > > > > > > > >
Re: The next release (v1.1.0)
The first two are doc tasks - should be no problem to get them done by 2/15. On Tue, Jan 24, 2017 at 1:14 PM, Mark Bretl wrote: > Do we think we can get these done and get a release before the next board > meeting (2/15)? I think it would be an excellent point on our report. > > Best Regards, > > --Mark > > On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra < > hitesh...@yahoo.com.invalid> wrote: > > > Update: Three more ticket for first release candidate.. > > > > GEODE-2300 Document default names for start locator/server > > GEODE-2353 Verify no clear-text passwords in documentation > > GEODE-2282 Provide ability to sort field while creating pdxType for jSON > > document(Need to document system property) > > > > Thanks.HItesh > > > > > > > > From: Hitesh Khamesra > > To: "dev@geode.apache.org" > > Sent: Monday, January 16, 2017 12:35 PM > > Subject: Re: The next release (v1.1.0) > > > > Update: We are waiting on following tickets for first release candidate. > > > > 1. GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse > User > > Exception > > 2. GEODE-2277 client cache fails to deserialize a PdxInstance due to > > InternalGemFireError > > 3. GEODE-2031 Host documentation for releases > > 4. GEODE-1965 Create backward-compatibility unit test framework > > > > Thanks.HItesh > > > > From: Anthony Baker > > To: dev@geode.apache.org > > Sent: Monday, January 9, 2017 9:49 AM > > Subject: Re: The next release (v1.1.0) > > > > Updates: > > > > 1) I did a first round of changes on GEODE-2142, should be enough for > > v1.1.0. > > 2) Any volunteers to look at GEODE-2031 or GEODE-1965? > > 3) Are there other open issues that should be included in the release? > > 4) Last call for a release manager… :-) > > > > Thanks, > > Anthony > > > > > > > On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: > > > > > > Our last release was on October 25. I think we’re past due for another > > one! We’ve had lots of great contributions since 1.0.0-incubating and > now > > that we’re are a top-level project we can drop the “-incubating” > qualifier. > > > > > > I reviewed our open JIRA issues and would like to include the following > > in the release: > > > > > > GEODE-2142 - JSON license incompatibility > > > We can update the NOTICE files and leave the JSON dependency alone > > (as long as we do another release before April 30). > > > > > > GEODE-1965 - backwards compatibility tests > > > I’d like to make sure we haven’t broken anything since our last > > release. > > > > > > GEODE-2031 - versioned documentation > > > Seems relatively straightforward? > > > > > > The remaining issues that are tagged with v1.1.0 [1] could be pushed to > > a following release IMO. Thoughts? > > > > > > Regarding the release manager, I can do the dirty work if no one else > > wants to volunteer :-) > > > > > > Anthony > > > > > > [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G > > EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20% > > 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority% > > 20DESC%2C%20created%20ASC > > > > > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: > > >> > > >> 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 > > >> > > > > > > > > > > > > > > > >
Re: The next release (v1.1.0)
Sorry, I was reading too quickly. The third one should be do-able, as well. On Tue, Jan 24, 2017 at 1:23 PM, Dave Barnes wrote: > The first two are doc tasks - should be no problem to get them done by > 2/15. > > On Tue, Jan 24, 2017 at 1:14 PM, Mark Bretl wrote: > >> Do we think we can get these done and get a release before the next board >> meeting (2/15)? I think it would be an excellent point on our report. >> >> Best Regards, >> >> --Mark >> >> On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra < >> hitesh...@yahoo.com.invalid> wrote: >> >> > Update: Three more ticket for first release candidate.. >> > >> > GEODE-2300 Document default names for start locator/server >> > GEODE-2353 Verify no clear-text passwords in documentation >> > GEODE-2282 Provide ability to sort field while creating pdxType for jSON >> > document(Need to document system property) >> > >> > Thanks.HItesh >> > >> > >> > >> > From: Hitesh Khamesra >> > To: "dev@geode.apache.org" >> > Sent: Monday, January 16, 2017 12:35 PM >> > Subject: Re: The next release (v1.1.0) >> > >> > Update: We are waiting on following tickets for first release candidate. >> > >> > 1. GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse >> User >> > Exception >> > 2. GEODE-2277 client cache fails to deserialize a PdxInstance due to >> > InternalGemFireError >> > 3. GEODE-2031 Host documentation for releases >> > 4. GEODE-1965 Create backward-compatibility unit test framework >> > >> > Thanks.HItesh >> > >> > From: Anthony Baker >> > To: dev@geode.apache.org >> > Sent: Monday, January 9, 2017 9:49 AM >> > Subject: Re: The next release (v1.1.0) >> > >> > Updates: >> > >> > 1) I did a first round of changes on GEODE-2142, should be enough for >> > v1.1.0. >> > 2) Any volunteers to look at GEODE-2031 or GEODE-1965? >> > 3) Are there other open issues that should be included in the release? >> > 4) Last call for a release manager… :-) >> > >> > Thanks, >> > Anthony >> > >> > >> > > On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: >> > > >> > > Our last release was on October 25. I think we’re past due for >> another >> > one! We’ve had lots of great contributions since 1.0.0-incubating and >> now >> > that we’re are a top-level project we can drop the “-incubating” >> qualifier. >> > > >> > > I reviewed our open JIRA issues and would like to include the >> following >> > in the release: >> > > >> > > GEODE-2142 - JSON license incompatibility >> > > We can update the NOTICE files and leave the JSON dependency alone >> > (as long as we do another release before April 30). >> > > >> > > GEODE-1965 - backwards compatibility tests >> > > I’d like to make sure we haven’t broken anything since our last >> > release. >> > > >> > > GEODE-2031 - versioned documentation >> > > Seems relatively straightforward? >> > > >> > > The remaining issues that are tagged with v1.1.0 [1] could be pushed >> to >> > a following release IMO. Thoughts? >> > > >> > > Regarding the release manager, I can do the dirty work if no one else >> > wants to volunteer :-) >> > > >> > > Anthony >> > > >> > > [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G >> > EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20% >> > 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority% >> > 20DESC%2C%20created%20ASC >> > > >> > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker >> wrote: >> > >> >> > >> 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 >> > >> >> > > >> > >> > >> > >> > >> > >> > >> > >
Re: The next release (v1.1.0)
Looks like all the JIRA’s for v1.1.0 have been wrapped up [1]. I say let’s cut a release branch and move ahead. Anthony [1] https://issues.apache.org/jira/browse/GEODE/fixforversion/12338352/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel > On Jan 24, 2017, at 1:14 PM, Mark Bretl wrote: > > Do we think we can get these done and get a release before the next board > meeting (2/15)? I think it would be an excellent point on our report. > > Best Regards, > > --Mark > > On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra < > hitesh...@yahoo.com.invalid> wrote: > >> Update: Three more ticket for first release candidate.. >> >> GEODE-2300 Document default names for start locator/server >> GEODE-2353 Verify no clear-text passwords in documentation >> GEODE-2282 Provide ability to sort field while creating pdxType for jSON >> document(Need to document system property) >> >> Thanks.HItesh >> >> >> >> From: Hitesh Khamesra >> To: "dev@geode.apache.org" >> Sent: Monday, January 16, 2017 12:35 PM >> Subject: Re: The next release (v1.1.0) >> >> Update: We are waiting on following tickets for first release candidate. >> >> 1. GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User >> Exception >> 2. GEODE-2277 client cache fails to deserialize a PdxInstance due to >> InternalGemFireError >> 3. GEODE-2031 Host documentation for releases >> 4. GEODE-1965 Create backward-compatibility unit test framework >> >> Thanks.HItesh >> >> From: Anthony Baker >> To: dev@geode.apache.org >> Sent: Monday, January 9, 2017 9:49 AM >> Subject: Re: The next release (v1.1.0) >> >> Updates: >> >> 1) I did a first round of changes on GEODE-2142, should be enough for >> v1.1.0. >> 2) Any volunteers to look at GEODE-2031 or GEODE-1965? >> 3) Are there other open issues that should be included in the release? >> 4) Last call for a release manager… :-) >> >> Thanks, >> Anthony >> >> >>> On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: >>> >>> Our last release was on October 25. I think we’re past due for another >> one! We’ve had lots of great contributions since 1.0.0-incubating and now >> that we’re are a top-level project we can drop the “-incubating” qualifier. >>> >>> I reviewed our open JIRA issues and would like to include the following >> in the release: >>> >>> GEODE-2142 - JSON license incompatibility >>>We can update the NOTICE files and leave the JSON dependency alone >> (as long as we do another release before April 30). >>> >>> GEODE-1965 - backwards compatibility tests >>>I’d like to make sure we haven’t broken anything since our last >> release. >>> >>> GEODE-2031 - versioned documentation >>>Seems relatively straightforward? >>> >>> The remaining issues that are tagged with v1.1.0 [1] could be pushed to >> a following release IMO. Thoughts? >>> >>> Regarding the release manager, I can do the dirty work if no one else >> wants to volunteer :-) >>> >>> Anthony >>> >>> [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G >> EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20% >> 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority% >> 20DESC%2C%20created%20ASC >>> >>>> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: >>>> >>>> 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 >>>> >>> >> >> >> >> >> >>
Re: The next release (v1.1.0)
Yay! +1 -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Fri, Jan 27, 2017 at 6:40 AM, Anthony Baker wrote: > Looks like all the JIRA’s for v1.1.0 have been wrapped up [1]. I say > let’s cut a release branch and move ahead. > > Anthony > > [1] https://issues.apache.org/jira/browse/GEODE/fixforversion/12338352/? > selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel > > > On Jan 24, 2017, at 1:14 PM, Mark Bretl wrote: > > > > Do we think we can get these done and get a release before the next board > > meeting (2/15)? I think it would be an excellent point on our report. > > > > Best Regards, > > > > --Mark > > > > On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra < > > hitesh...@yahoo.com.invalid> wrote: > > > >> Update: Three more ticket for first release candidate.. > >> > >> GEODE-2300 Document default names for start locator/server > >> GEODE-2353 Verify no clear-text passwords in documentation > >> GEODE-2282 Provide ability to sort field while creating pdxType for jSON > >> document(Need to document system property) > >> > >> Thanks.HItesh > >> > >> > >> > >> From: Hitesh Khamesra > >> To: "dev@geode.apache.org" > >> Sent: Monday, January 16, 2017 12:35 PM > >> Subject: Re: The next release (v1.1.0) > >> > >> Update: We are waiting on following tickets for first release candidate. > >> > >> 1. GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse > User > >> Exception > >> 2. GEODE-2277 client cache fails to deserialize a PdxInstance due to > >> InternalGemFireError > >> 3. GEODE-2031 Host documentation for releases > >> 4. GEODE-1965 Create backward-compatibility unit test framework > >> > >> Thanks.HItesh > >> > >> From: Anthony Baker > >> To: dev@geode.apache.org > >> Sent: Monday, January 9, 2017 9:49 AM > >> Subject: Re: The next release (v1.1.0) > >> > >> Updates: > >> > >> 1) I did a first round of changes on GEODE-2142, should be enough for > >> v1.1.0. > >> 2) Any volunteers to look at GEODE-2031 or GEODE-1965? > >> 3) Are there other open issues that should be included in the release? > >> 4) Last call for a release manager… :-) > >> > >> Thanks, > >> Anthony > >> > >> > >>> On Jan 6, 2017, at 10:13 AM, Anthony Baker wrote: > >>> > >>> Our last release was on October 25. I think we’re past due for another > >> one! We’ve had lots of great contributions since 1.0.0-incubating and > now > >> that we’re are a top-level project we can drop the “-incubating” > qualifier. > >>> > >>> I reviewed our open JIRA issues and would like to include the following > >> in the release: > >>> > >>> GEODE-2142 - JSON license incompatibility > >>>We can update the NOTICE files and leave the JSON dependency alone > >> (as long as we do another release before April 30). > >>> > >>> GEODE-1965 - backwards compatibility tests > >>>I’d like to make sure we haven’t broken anything since our last > >> release. > >>> > >>> GEODE-2031 - versioned documentation > >>>Seems relatively straightforward? > >>> > >>> The remaining issues that are tagged with v1.1.0 [1] could be pushed to > >> a following release IMO. Thoughts? > >>> > >>> Regarding the release manager, I can do the dirty work if no one else > >> wants to volunteer :-) > >>> > >>> Anthony > >>> > >>> [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G > >> EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20% > >> 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority% > >> 20DESC%2C%20created%20ASC > >>> > >>>> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: > >>>> > >>>> 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 > >>>> > >>> > >> > >> > >> > >> > >> > >> > >
