Considering I’m one of the only people who adds @since tags (or Javadocs in general), I think we’ll need some tooling to help with this. In Jenkins, we had some sort of script for this so that we could add “@since TODO” to new files, and the script would replace them all before tagging a release (which is more relevant when you have weekly releases).
> On Oct 23, 2023, at 6:28 AM, Volkan Yazıcı <vol...@yazi.ci> wrote: > > Agreed, we should use `@since` tags. Though this doesn't warrant a new > website folder for each release, does it? Given we never disclosed these > folders, I want to understand the value it delivered in the past that can't > be achieved if we switch to using a single folder. > > On Mon, Oct 23, 2023 at 12:49 PM Piotr P. Karwasz <piotr.karw...@gmail.com> > wrote: > >> Hi Volkan, >> >> On Mon, 23 Oct 2023 at 10:40, Volkan Yazıcı <vol...@yazi.ci> wrote: >>> >>>> it [doesn't] fully documents what was in prior releases >>> >>> Why is this a problem? We document newly added features with "starting >> from >>> version X, Log4j ships Y...". Doesn't this address your concern? >> >> I prefer to document each new public/protected class or method with a >> `@since` tag. We often don't do that (e.g. even in 2.21.0 there are a >> couple of new methods). >> >> Maybe there is an automatic scanner that can do it. >> >> Piotr >>
