Jacob - Ah, sorry to hear that.
On Thu, May 4, 2017 at 2:09 PM, Jacob Barrett wrote:
> John, I wish we could do that but Apache would require that geode-native be
> a fully qualified sub-project with all the headache that goes with that to
> "release" separately.
>
>
> On Thu, May 4, 2017 at 11:
It's the problem we are going to have with two distinctly different modules
sharing the same project release cycle. The best we could do is branch
release/v1.3 form the support/v1.2 branch until we are ready to release the
breaking changes in the geode-native/develop branch.
-Jake
On Thu, May 4,
John, I wish we could do that but Apache would require that geode-native be
a fully qualified sub-project with all the headache that goes with that to
"release" separately.
On Thu, May 4, 2017 at 11:35 AM John Blum wrote:
> A good reason to use separate repos. Individual components of Geode,
>
A good reason to use separate repos. Individual components of Geode,
especially clear boundaries like Native Client, *Gfsh*, or Pulse, etc,
should be separately and independently releasable to provide a smoother
release cadence based on velocity and community need.
Then, using a Maven "BOM", you
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, 2017, at
I don't see how they are different branches? If geode-Native has release/1.2
and Geode has release/1.2?
Sent from my iPhone
> On May 4, 2017, at 10:21 AM, Anthony Baker wrote:
>
> I think it’s confusing to cut a release from different branches for geode,
> geode-examples, and geode-native but
> 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
I think it’s confusing to cut a release from different branches for geode,
geode-examples, and geode-native but I don’t have a better idea.
+0
Anthony
> On May 4, 2017, at 7:29 AM, Jacob Barrett wrote:
>
> All,
>
> I want to start the discussion on releasing Geode Native C++ and .NET
> clien
