Re: Best practices for cyrus-sasl development

2020-02-18 Thread Quanah Gibson-Mount
--On Tuesday, February 18, 2020 1:45 PM -0500 Ken Murchison wrote: I agree that we should sync 2.1 with master and use it for future 2.1 releases and use master fir development. Ok. I tested a merge of origin/master, and it's clean. Would you like me to push that? That would definite

Re: Best practices for cyrus-sasl development

2020-02-18 Thread Ken Murchison
On 2/18/20 1:50 PM, Quanah Gibson-Mount wrote: --On Tuesday, February 18, 2020 1:45 PM -0500 Ken Murchison wrote: I agree that we should sync 2.1 with master and use it for future 2.1 releases and use master fir development. Ok.  I tested a merge of origin/master, and it's clean.  Woul

Re: Best practices for cyrus-sasl development

2020-02-18 Thread Ken Murchison
I agree that we should sync 2.1 with master and use it for future 2.1 releases and use master fir development. On 2/18/20 1:42 PM, Quanah Gibson-Mount wrote: --On Tuesday, February 18, 2020 12:59 PM -0500 Ken Murchison wrote: I can tell you that 2.1.27 was built from master.  The 2.1 br

Re: Best practices for cyrus-sasl development

2020-02-18 Thread Quanah Gibson-Mount
--On Tuesday, February 18, 2020 12:59 PM -0500 Ken Murchison wrote: 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. Looking at the branches in git, I do

Re: Best practices for cyrus-sasl development

2020-02-18 Thread Ken Murchison
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