Hello, > It's been about three and a half years since the last cyrus-sasl release.
Who can decide on this? Who can delegate tasks? > I'm wondering what needs to be done before a new one is made. E.g. replacing “staticly” with “statically” - https://github.com/cyrusimap/cyrus-sasl/pull/864 . Greetings // Дилян -----Original Message----- From: Ricardo Signes via SASL <[email protected]> Reply-To: SASL <[email protected]> To: [email protected] Subject: next cyrus-sasl release Date: 24/09/25 20:09:53 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 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 all 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 IMAP downstream users, but it's not immediately clear which things are housekeeping and which are serious problems. If there is some active[-enough] cyrus-sasl dev who can chime in, I would appreciate it. -- rjbs Cyrus / SASL / seediscussions +participants +delivery options Permalink ------------------------------------------ Cyrus: SASL Permalink: https://cyrus.topicbox.com/groups/sasl/T4bfea6b1dc01d766-M787c40f5a3255745221b07f4 Delivery options: https://cyrus.topicbox.com/groups/sasl/subscription
