Hi,

sorry for the late response, have been a bit busy recently...

Yes, we should remove botan (1) from Fedora - that has also been a request
by upstream. The point is, I want to keep monotone, and it needs a bit of
work to switch it over to botan2. There exists a branch that should have
the necessary changes, but no released version.

Anyway, the monotone switch will not make it in time for F40 I guess, but
I'll look into it.

Regarding botan3, I guess no one has volunteered yet to maintain it.

Regards,
Thomas


Am Do., 4. Apr. 2024 um 20:28 Uhr schrieb Jens-Ulrik Petersen <
peter...@redhat.com>:

> https://botan.randombit.net/handbook/support.html#branch-support-status
> can be referenced in the retirement commit:
>
> Branch
>
> First Release
>
> End of Active Development
>
> End of Life
>
> Botan 1.8
>
> 2008-12-08
>
> 2010-08-31
>
> 2016-02-13
>
> Botan 1.10
>
> 2011-06-20
>
> 2012-07-10
>
> 2018-12-31
> (Though 1.11.x also exists, or was that a devel series for botan2?)
> --
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Thomas Moschny <thomas.mosc...@gmail.com>
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to