Den mån 9 maj 2022 kl 14:12 skrev Nathan Hartman <hartman.nat...@gmail.com>:
> On Mon, May 9, 2022 at 7:38 AM Daniel Sahlberg < > daniel.l.sahlb...@gmail.com> wrote: > >> Den sön 8 maj 2022 kl 02:21 skrev Daniel Shahaf <d...@daniel.shahaf.name>: >> >>> Daniel Sahlberg wrote on Sat, 07 May 2022 18:37 +00:00: >>> > Den lör 7 maj 2022 kl 14:17 skrev Daniel Shahaf < >>> d...@daniel.shahaf.name>: >>> > >>> >> Daniel Sahlberg wrote on Sat, 07 May 2022 09:53 +00:00: >>> >> > I've committed the changes in r1900649. >>> >> >>> >> I wonder if this merits a news entry on /index.html? Just "1.10.x is >>> >> EOL; please upgrade to 1.14". >>> >> >>> > >>> > Good point. I also considered this, but I couldn't find any other >>> release >>> > being announced EOL so I elected to not do this. I'm open to >>> reconsider! >>> > >>> >>> Until today, most releases that have gone EOL did so either by virtue of >>> a subsequent .0 release being made (1.0 through 1.8) or at about the >>> same time as a subsequent .0 release being made (1.11 through 1.13 >>> inclusive). In either case, at about the time of a release's going EOL >>> there would have been a news entry (and announce@ post, and possibly >>> a press release) about the new release, and the new release's release >>> notes would have pointed out, at the very end, that previous releases >>> were EOL'ed by the new release. So, to someone who knew our "support two >>> release lines" policy, EOLings were very visible. >>> >> >> Good point. I saw this in the release notes but I can't find anything in >> announce@. Is the new release policy something we want to announce? >> >> I've added a news item in 1900735 et al. >> > > > I think we should announce it. > > The proposed news item looks good. > > One thing I might change is to suggest updating "as soon as practical," or > something to that effect, and point out that 1.10.8, released last month, > is available as a final 1.10 release. > Thanks, sounds like a good idea. I've added this in r1901130. Can I just copy the news item text and post to announce@ (I suppose I will have to configure my @apache.org address as sender). /Daniel
