You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Anthony Baker <ab...@pivotal.io> on 2016/02/08 18:34:18 UTC
1.0.0-incubating.M1
Hi,
After a successful IPMC VOTE [1] on the 1.0.0-incubating.M1 I believe we have completed the release finalization steps. Nitin is planning to send the ANNOUNCE email as noted in [2]. The release bits have propagated to the mirrors and Maven Central [3]. The release branch has been merged to develop and master.
There are a few more things to complete:
1) Update the website with a download link [4]
2) Generate a docker image for 1.0.0-incubating.M1
3) Change the version in gradle.properties to 1.0.0-incubating.M2-SNAPSHOT
There was a bunch of discussion around release naming that hasn’t been completely resolved yet. For now, I think the simplest thing is to continue releasing M# versions until we are ready to move to a full 1.0.0-incubating release.
Thoughts?
Anthony
[1] http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3cBY2PR10MB0615E556CBADC20906D3240FB6D30@BY2PR10MB0615.namprd10.prod.outlook.com%3e
[2] https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
[3] http://search.maven.org/#search%7Cga%7C1%7Cgeode
[4] http://www.apache.org/dyn/closer.cgi/incubator/geode/1.0.0-incubating.M1
Re: 1.0.0-incubating.M1
Posted by Anthony Baker <ab...@pivotal.io>.
This has now been committed as dcf6bef40ce84a77037399be6eaf1b0a9ee6b598.
Anthony
> On Feb 9, 2016, at 6:10 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
> Any further discussion? Downstream projects like SpringDataGemFire will need to update their maven coordinates once we change the version but think that should be expected.
>
>
>> On Feb 8, 2016, at 9:34 AM, Anthony Baker <ab...@pivotal.io> wrote:
>>
>> 3) Change the version in gradle.properties to 1.0.0-incubating.M2-SNAPSHOT
>>
>> There was a bunch of discussion around release naming that hasn’t been completely resolved yet. For now, I think the simplest thing is to continue releasing M# versions until we are ready to move to a full 1.0.0-incubating release.
>
Re: 1.0.0-incubating.M1
Posted by John Blum <jb...@pivotal.io>.
I was thinking about this and I am tempted to leave *Spring Data GemFire*
with *Apache Geode* support (apache-geode) on build snapshots until the
first official (GA) release. Typically, Spring projects do not consume
dependencies unless those dependencies are GA versions.
We could, in effect, cut a M1 release of *Spring Data GemFire* with *Apache
Geode* support that depends on 1.0.0.incubating.M1, however, I will need to
talk with the Spring infrastructure team about cutting a release since the
process has changed significantly.
But, think the SDG apache-geode branch should continue with Apache Geode
build snapshots.
Let me know if there are any other thoughts.
Thanks,
John
On Tue, Feb 9, 2016 at 6:10 AM, Anthony Baker <ab...@pivotal.io> wrote:
> Any further discussion? Downstream projects like SpringDataGemFire will
> need to update their maven coordinates once we change the version but think
> that should be expected.
>
>
> > On Feb 8, 2016, at 9:34 AM, Anthony Baker <ab...@pivotal.io> wrote:
> >
> > 3) Change the version in gradle.properties to
> 1.0.0-incubating.M2-SNAPSHOT
> >
> > There was a bunch of discussion around release naming that hasn’t been
> completely resolved yet. For now, I think the simplest thing is to
> continue releasing M# versions until we are ready to move to a full
> 1.0.0-incubating release.
>
>
--
-John
503-504-8657
john.blum10101 (skype)
Re: 1.0.0-incubating.M1
Posted by Anthony Baker <ab...@pivotal.io>.
Any further discussion? Downstream projects like SpringDataGemFire will need to update their maven coordinates once we change the version but think that should be expected.
> On Feb 8, 2016, at 9:34 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
> 3) Change the version in gradle.properties to 1.0.0-incubating.M2-SNAPSHOT
>
> There was a bunch of discussion around release naming that hasn’t been completely resolved yet. For now, I think the simplest thing is to continue releasing M# versions until we are ready to move to a full 1.0.0-incubating release.
Re: 1.0.0-incubating.M1
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
First of all -- congrats on your first release -- this is a pretty big
milestone!
On Mon, Feb 8, 2016 at 9:36 AM, Kirk Lund <kl...@pivotal.io> wrote:
> Is a 1.0.0-incubating.M1 release something that we can advertise outside of
> the dev@geode list, blog about, etc?
Yes, absolutely! Make sure to update the website to provide Download link
to the bits.
Thanks,
Roman.
Re: 1.0.0-incubating.M1
Posted by Kirk Lund <kl...@pivotal.io>.
Is a 1.0.0-incubating.M1 release something that we can advertise outside of
the dev@geode list, blog about, etc?
-Kirk
On Mon, Feb 8, 2016 at 9:34 AM, Anthony Baker <ab...@pivotal.io> wrote:
> Hi,
>
> After a successful IPMC VOTE [1] on the 1.0.0-incubating.M1 I believe we
> have completed the release finalization steps. Nitin is planning to send
> the ANNOUNCE email as noted in [2]. The release bits have propagated to
> the mirrors and Maven Central [3]. The release branch has been merged to
> develop and master.
>
> There are a few more things to complete:
>
> 1) Update the website with a download link [4]
> 2) Generate a docker image for 1.0.0-incubating.M1
> 3) Change the version in gradle.properties to 1.0.0-incubating.M2-SNAPSHOT
>
> There was a bunch of discussion around release naming that hasn’t been
> completely resolved yet. For now, I think the simplest thing is to
> continue releasing M# versions until we are ready to move to a full
> 1.0.0-incubating release.
>
> Thoughts?
>
> Anthony
>
> [1]
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3cBY2PR10MB0615E556CBADC20906D3240FB6D30@BY2PR10MB0615.namprd10.prod.outlook.com%3e
> [2] https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> [3] http://search.maven.org/#search%7Cga%7C1%7Cgeode
> [4]
> http://www.apache.org/dyn/closer.cgi/incubator/geode/1.0.0-incubating.M1
>
>