Furthermore, about the 2.4.32 release there: On 2018-03-16 08:03, Jim Jagielski wrote: > Just because it is released, doesn't mean we need to announce it. We > can easily release a quick 2.4.33 and announce *that*. 2.4.32 was/is > just an un-announced release. >
Personally, I prefer this approach. I've been holding off on sending the announcement as noted on private@, but I think I'd sooner T&R 2.4.33 and get ready for that one to go out. Again, I volunteer... assuming y'all haven't come to the opinion that I'm cursed as an RM. -- Daniel Ruggeri -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
