next cyrus-sasl release
"Ricardo Signes via SASL" <[email protected]> Wed, 24 Sep 2025 13:09:53 -0400
| Newsgroups | gmane.comp.security.cyrus.sasl |
|---|---|
| Message-ID | <[email protected]> |
--1f7bacaae55e4d8994947b202f43d69e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Heya, It's been about three and a half years since the last cyrus-sasl release. = I'm wondering what *needs* to be done before a new one is made. In GitHub I see a milestone called 2.1.29, but nothing in it. On the other= hand, there's a 2.2.0 milestone <https://github.com/cyrusimap/cyrus-sasl/i= ssues?q=3Dstate%3Aopen%20milestone%3A2.2.0> with 10 items undone. To what = extent does anybody consider these real blockers. That is: *Are we better = off not shipping *anything* until these are done, or shipping a new release= without these done?* (Don't say "we should ship now and it should have al= l these done". That's not the question! On the other hand "we should ship= but only after *these two items are done*" is useful.) I can get some development time to throw at this, for the sake of Cyrus IMA= P downstream users, but it's not immediately clear which things are houseke= eping and which are serious problems. If there is some active[-enough] cyr= us-sasl dev who can chime in, I would appreciate it. --=20 rjbs ------------------------------------------ Cyrus: SASL Permalink: https://cyrus.topicbox.com/groups/sasl/T4bfea6b1dc01d766-Mda0d7f= 50d768dc7427679673 Delivery options: https://cyrus.topicbox.com/groups/sasl/subscription --1f7bacaae55e4d8994947b202f43d69e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html> <html><html><html><head><title></title></head><body><div>Heya,</div><div><b= r /></div><div>It's been about three and a half years since the last cy= rus-sasl release. I'm wondering what <i>needs</i> to be= done before a new one is made.</div><div><br /></div><div>In GitHub I see = a milestone called 2.1.29, but nothing in it. On the other hand, ther= e's a <a href=3D"https://github.com/cyrusimap/cyrus-sasl/issues?q=3Dsta= te%3Aopen%20milestone%3A2.2.0">2.2.0 milestone</a> with 10 items undon= e. To what extent does anybody consider these real blockers. Th= at is: <b>Are we better off not shipping <i>anything</i> unt= il these are done, or shipping a new release without these done?</b> = (Don't say "we should ship now and it should have all these done&q= uot;. That's not the question! On the other hand "we s= hould ship but only after <i>these two items are done</i>" is use= ful.)</div><div><br /></div><div>I can get some development time to throw a= t this, for the sake of Cyrus IMAP downstream users, but it's not immed= iately clear which things are housekeeping and which are serious problems.&= nbsp; If there is some active[-enough] cyrus-sasl dev who can chime in, I w= ould appreciate it.</div><div><br /></div><div id=3D"sig25795005"><div clas= s=3D"signature">-- </div><div class=3D"signature">rjbs</div></div><div= ><br /></div><div id=3D"topicbox-footer" style=3D"margin:10px 0 0;border-to= p:1px solid #ddd;border-color:rgba(0,0,0,.15);padding:7px 0;"> <strong><a href=3D"https://cyrus.topicbox.com/latest" style=3D"color:inheri= t;text-decoration:none">Cyrus</a></strong> / SASL / see <a href=3D"https://cyrus.topicbox.com/groups/sasl">discussions</a> + <a href=3D"https://cyrus.topicbox.com/groups/sasl/members">participants</a> + <a href=3D"https://cyrus.topicbox.com/groups/sasl/subscription">delivery&nb= sp;options</a> <a href=3D"https://cyrus.topicbox.com/groups/sasl/T4bfea6b1dc01d766-Mda0d7f= 50d768dc7427679673" style=3D"float:right">Permalink</a> </div> </body></html></html></html>= --1f7bacaae55e4d8994947b202f43d69e--