different versions. Many other open
> > source projects operate the same way... Reactor.
> >
> > $0.02
> >
> > -John
> >
> >
> > [1]
> >
> > https://github.com/spring-projects/spring-data-gemfire/
> tree/1.8.4.RELEASE-PATCH01
> >
> &
May 4, 2017 at 11:23 AM Anthony Baker wrote:
> Let’s say we release geode-native along with geode 1.2. When it comes
> time to release 1.3 (and geode-native is not yet ready) we would be
> creating release branches from:
>
> geode: develop
> geode-example:
> Let’s say we release geode-native along with geode 1.2. When it comes
> > time to release 1.3 (and geode-native is not yet ready) we would be
> > creating release branches from:
> >
> > geode: develop
> > geode-example: develop
> > geode-native: rele
>
> geode: develop
> geode-example: develop
> geode-native: release/v1.2.0
>
> Anthony
>
> > On May 4, 2017, at 11:16 AM, Jacob Barrett wrote:
> >
> > I don't see how they are different branches? If geode-Native has
> release/1
Let’s say we release geode-native along with geode 1.2. When it comes time to
release 1.3 (and geode-native is not yet ready) we would be creating release
branches from:
geode: develop
geode-example: develop
geode-native: release/v1.2.0
Anthony
> On May 4, 2
.2 and get it ready for
>> source release. Backport any changes on the release branch to develop. That
>> leaves develop open for marching forward with what would be a 2.0 set of
>> sources. Any release of Geode 1.x would just include the geode-native
>> relea
> On May 4, 2017, at 7:29 AM, Jacob Barrett wrote:
>
> There are a few house keeping items left in the source release JIRA [1]. It
> would be great to get some help completing these tasks.
BTW, I’m happy to help with some of the build issues. I wrote up a gradle
script awhile back to create a
t ready for
> source release. Backport any changes on the release branch to develop. That
> leaves develop open for marching forward with what would be a 2.0 set of
> sources. Any release of Geode 1.x would just include the geode-native
> release/1.x branches until Geode 2.0.
>
>
eady for
source release. Backport any changes on the release branch to develop. That
leaves develop open for marching forward with what would be a 2.0 set of
sources. Any release of Geode 1.x would just include the geode-native
release/1.x branches until Geode 2.0.
Thoughts and feedb
