The lime-packages repository has currently a huge amount of branches making it rather hard
to spot active ones. I'd propose to use the following structure (stolen from
* Use one branch for developing (currently called "development", may better be
unified to " master").
* One brach per release
This is great because new people don't start developing on master and eventually find
out its "outdated". The structure is used on literally every other GH project
I'm working on, even on other LibreMesh repos.
All pull requests should come from forked repos.
Additionally, the dev branch is currently (partly) protected so that most devs can't
directly push there but need an approved PR, which is good. However, the master branch aka
current stable release lacks this security measurement.
Show replies by date