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.=
=C2=A0 I'm wondering what=C2=A0needs=C2=A0to be done before a new one is ma=
de.

In GitHub I see a milestone called 2.1.29, but nothing in it.=C2=A0 On the =
other hand, there's a 2.2.0 milestone=C2=A0with 10 items undone.=C2=A0 To w=
hat extent does anybody consider these real blockers.=C2=A0 That is:=C2=A0A=
re we better off not shipping=C2=A0anything=C2=A0until these are done, or s=
hipping a new release without these done?=C2=A0 (Don't say "we should ship =
now and it should have all these done".=C2=A0 That's not the question!=C2=
=A0 On the other hand "we should ship but only after=C2=A0these two items a=
re 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.=C2=A0 If there is some active[-enough=
] cyrus-sasl dev who can chime in, I would appreciate it.

--=C2=A0
rjbs

Cyrus / SASL / seediscussions +participants +delivery=C2=A0options
Permalink

------------------------------------------
Cyrus: SASL
Permalink: https://cyrus.topicbox.com/groups/sasl/T4bfea6b1dc01d766-M787c40=
f5a3255745221b07f4
Delivery options: https://cyrus.topicbox.com/groups/sasl/subscription