Aaron Mihalik created RYA-164:
---------------------------------
Summary: Move off of Gitflow
Key: RYA-164
URL: https://issues.apache.org/jira/browse/RYA-164
Project: Rya
Issue Type: Wish
Reporter: Aaron Mihalik
Gitflow on an Apache project is a bit annoying. I propose we follow the
pattern of other Apache Projects (eg. NiFi, Spark, Accumulo) and have master
(the default branch) contain the latest major release line under development.
This would have a couple immediate benefits:
1. As committers, we have to manually pester contributors to close their pull
requests after we merge their PRs. Instead we can use the GitHub "closes
#<issue>" semantics to automatically close the PR after a merge.
2. As a community, we would be more aligned with other conventions used in
Apache projects.
3. As developers, we have to be (slightly) more mindful where we point other
developers. We have to make a point of saying "the 'develop' branch... not
that default one"
(I concede I'm really reaching for the last point :) )
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
