On Mon, Sep 10, 2018, 5:51 PM Gregg Reynolds <d...@mobileink.com> wrote:
> > > On Wed, Sep 5, 2018, 8:04 PM Nathan Heldt-Sheller < > nathan.heldt-shel...@intel.com> wrote: > >> Hi IoTivity Devs, >> >> >> In the past, we’ve had a relatively unstable master branch, which has >> caused us to stick to release branches perhaps longer than we’d like, to >> avoid battling a constant stream of regressions. These long-lived branches >> entail more work cherry picking release branch changes into master, >> tracking status on two separate branches for longer, etc. >> >> >> >> Comarch has recently finished installing a nightly regression test using >> the OCF Certification Test Tool, and will be running it against master >> every night going forward. We’ll get an email within 24 hours if an OCTT >> regression is introduced. I’m very happy about this J This – along >> with existing Jenkins tests – should keep new regressions to a minimum. >> This in turn means I think we can shorten the lifecycle for our release >> branches. >> >> >> >> For the next release (“Bangkok Point Release”, a.k.a. 2.1.0) I’d like to >> try a much shorter release branch plan. We’d move all development to >> master >> > Before you do this please take some time to study this: > https://nvie.com/posts/a-successful-git-branching-model/ > > Using master for development seems questionable to me. > More pointedly, it is not enough to simply support branches. Branch off of what? > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9936): https://lists.iotivity.org/g/iotivity-dev/message/9936 Mute This Topic: https://lists.iotivity.org/mt/25216172/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
