New git branch policy
by Anaczkowski, Lukasz
Hello there,
In order to simplify branch management and decrease
git maintenance effort, we have come up with a plan
to move development from 'dev' onto 'master' branch
directly.
What does it mean?
It means that 'master' branch may contain code that has
not been 'blessed' with official memkind release.
In order to checkout release version, you'll need to use
git tags mechanism. Documentation will be updated with
details.
What will change?
'dev' branch will be abandoned - it will stay there to not
break your git clones, however, sources will be removed
and replaced with a text file describing what is going on.
Stable/production releases will be tagged as it is done
currently.
Overall, workflow will be similar to the one that is done
by Linus Torvalds for Linux Kernel (we don't plan RCs, though).
Switch will be done on Feb 1st.
Let me know any comments, concerns.
Cheers,
Lukasz
5 years, 5 months
