Re: next cyrus-sasl release

Hello =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=
=D0=BE=D0=B2,

Thanks for your message about a new Cyrus-SASL release!

It is linked to:
- https://github.com/cyrusimap/cyrus-sasl/issues/729
- https://github.com/cyrusimap/cyrus-sasl/issues/835
- https://cyrus.topicbox.com/groups/sasl/T9e94a007b3b4a95d
- https://cyrus.topicbox.com/groups/sasl/T4bfea6b1dc01d766

Like you speak about your PR, there is a DCO problem:
- https://github.com/cyrusimap/cyrus-sasl/pull/864/checks?check_run_id=3D32=
381454042

I have published a comment here:
- https://github.com/cyrusimap/cyrus-sasl/pull/864#issuecomment-2817183483
- https://github.com/cyrusimap/cyrus-sasl/pull/864#issuecomment-3184233441

Can you solve it?

Thanks in advance.

Regards,

Neustradamus
________________________________________
From: =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=
=D0=BE=D0=B2 <[email protected]>
Sent: Wednesday, October 29, 2025 19:28
To: SASL
Subject: Re: next cyrus-sasl release

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 =E2=80=9Cstaticly=E2=80=9D with =E2=80=9Cstatically=E2=80=9D=
 - https://github.com/cyrusimap/cyrus-sasl/pull/864 .

Greetings // =D0=94=D0=B8=D0=BB=D1=8F=D0=BD

-----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 ship=
ping 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 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.

--
rjbs

Cyrus / SASL / seediscussions +participants +delivery options
Permalink

------------------------------------------
Cyrus: SASL
Permalink: https://cyrus.topicbox.com/groups/sasl/T4bfea6b1dc01d766-M069c78=
4c5b84065b3bc2914d
Delivery options: https://cyrus.topicbox.com/groups/sasl/subscription