celix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roy Lenferink <rlenfer...@apache.org>
Subject [LAZY] Use master as development branch
Date Wed, 22 Apr 2020 17:22:11 GMT
Hi all,

I'd like to propose the idea of using the 'master' branch as our development branch. Why?
- ASF releases are promoted through the ASF mirroring system. Our website is built on top
of this 
allowing the user to select a mirror for downloading the release. Cloning the git repository
is not
the first thing a user does. Even if users plan to use the git repository they can use a specific
- The ASF allows committers to use a so-called .asf.yaml file [1] for changing repository
However, changes to this file are only propagated when made on the master (or trunk) branch.

IMO our current workflow with develop/master just adds extra complexity. Other ASF projects
using the master branch as their development branch as well, e.g. Spark [2], Dubbo [3], Flink
[4] & 

If no objections within 72 hours I'll merge the 'develop' branch to our 'master' branch, update
current open pull requests to have 'master' as base branch, open a ticket to remove branch

protection for the develop branch & update the website to point to the master branch for
instead of the develop branch.

See also [6] for a short discussion on this topic already.


[1] https://s.apache.org/asfyaml
[2] https://github.com/apache/spark
[3] https://github.com/apache/dubbo
[4] https://github.com/apache/flink
[5] https://github.com/apache/hbase
[6] https://github.com/apache/celix/pull/202#issuecomment-616429007

View raw message