Consistency is best in my opinion. -- Mike Stolz Principal Engineer - Gemfire Product Manager Mobile: 631-835-4771
On Dec 12, 2018 9:59 AM, "Jacob Barrett" <jbarr...@pivotal.io> wrote: > Make the default “develop” to be consistent with the rest of our > repositories. Put a statement in the https://urldefense.proofpoint. > com/v2/url?u=http-3A__README.md&d=DwIFaQ&c=lnl9vOaLMzsy2niBC8-h_K- > 7QJuNJEsFrzdndhuJ3Sw&r=us915XVL1kT8_Q-vmxAPAGcdk8eQkhBJKJGVCwFNFlA& > m=2d4Fya8f3YbP-qfZHyIna7bxGf6bav_f6x5ygphVvmw&s= > ATi5iKFzdX8ndZkkBDCbBHeidnwAGhMWjQaB3PMoI4k&e= that these examples for > the 1.9.0-SNAPSHOT (develop). When cutting a release and merging to master > change the say they are for 1.9.0 (rel/v1.9.0). > > > > On Dec 12, 2018, at 9:07 AM, Anthony Baker <aba...@pivotal.io> wrote: > > > > Alexander noticed that some recent PR’s against the geode-examples repo > made against the master branch. That breaks the gitflow approach where > only released code is on master. Should we update the default branch to be > develop? > > > > > > Anthony > > > >
