I can tell you that 2.1.27 was built from master. The 2.1 branch might
have been created in anticipation of master becoming the dev branch for
2.2, but I don't know that for certain.
I have just forwarded an email that was sent regarding Cyrus IMAPd
release process to this list for discussion.
On 2/18/20 12:36 PM, Quanah Gibson-Mount wrote:
Hello,
I'm starting to go through the issues queue and pending pull requests,
and would like to start merging in some fixes. However, I'd like to
know what procedure(s) etc should be followed, if they exist. Also, I
have questions on the overall state of the git repo.
There is a cyrus-sasl-2.1 branch that seems to have not been touched
since 2011. It appears that cyrus-sasl-2.1.27 was cut off of the
master branch?
This seems like an odd development path, I would have expected 2.1.27
to come from the 2.1 release branch generally.
Can anyone provide information on what the intention is with the repo?
Should all work simply be done against master, and all releases cut
from it? Should the 2.1 release branch be caught up with master and
then used for releases after that point?
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--
Ken Murchison
Cyrus Development Team
Fastmail US LLC
