| Summary: | dev-libs/libevent-2.1.5* stabilization request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Deutschmann (RETIRED) <whissi> |
| Component: | Stabilization | Assignee: | Jeroen Roovers (RETIRED) <jer> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | Keywords: | STABLEREQ |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Thomas Deutschmann (RETIRED)
2016-08-24 16:52:04 UTC
You could give a reason why. :) Formal reasons: In tree for >30d without any blocking bugs. My main reason to ask for stabilization of =dev-libs/libevent-2.1.5-r4 is that I am going to stabilize some packages depending on dev-libs/libevent and because I am using 2.1.x for some time now I don't want to keep an eye on 2.0.x as long as this isn't required. So 2.1 is irrelevant? I wasn't planning on stabilising the development branch at all, by the way. https://github.com/libevent/libevent/graphs/contributors looks pretty lively. I said "dead development branch" based on 2.1.x latest release date which was on 2015-01-05. If you _have_ a dedicated dev branch and stop releasing updates for more than 1y... but yes the project had some activity in the past months. OK, feel free to decline and close at the moment. I do understand that you don't want to stabilize a dev branch and libevent-2.0.22-r2 only added libressl USE flag which doesn't need to go stable because there is no stable libressl package at the moment. I'll come back once I find an ebuild which require 2.1.x ;) Dear Maintainer (or who is mainly involved in this stable request), This is an auto-generated message that will move the current component to the new component Stabilization. To ensure that the stabilization will proceed correctly, please fill the fields "Atoms to stabilize" and "Runtime testing required" as described here: https://archives.gentoo.org/gentoo-dev/message/4b2ef0e9aa7588224b8ae799c5fe31fa |