❦ 14 octobre 2014 12:11 +0200, Michal Trojnara <[email protected]> :
>> On the other hand, because the codebase is relatively small, it is >> easy to maintain as is. As far as I know it can still fill its role >> (but the 0.3 version doesn't have support for EC cryptography). >> >> The big question is: should it be removed now or should it be >> removed in jessie+1? > > Unless you have enough time to take over the upstream, it's probably > best to remove stud before Jessie is frozen. The more you delay it > the better chance of someone else creating dependencies on stud. > https://release.debian.org/jessie/freeze_policy.html I don't want to take over upstream (all the more that stud is not that useful nowadays, people can use either stunnel or haproxy). I was thinking of people already using it to have a chance to migrate to something else during Jessie. However, I see that the popcon is quite low (19). I'll file a removal request. -- Don't use conditional branches as a substitute for a logical expression. - The Elements of Programming Style (Kernighan & Plauger)
signature.asc
Description: PGP signature
