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/issues?q=state%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 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 Permalink: https://cyrus.topicbox.com/groups/sasl/T4bfea6b1dc01d766-Mda0d7f50d768dc7427679673 Delivery options: https://cyrus.topicbox.com/groups/sasl/subscription
