I see the homepage was updated meanwhile (just required a force reload, probably we should include some Cache-Control response headers).
> On 18. Jan 2025, at 11:22, Konrad Windszus <[email protected]> wrote: > > Hi Stefan, > Thanks a lot for driving this release. Maybe you can share also in the news > section of our homepage (https://sling.apache.org/)? > > Probably the next time we need to tweak the aggregate javadoc some more: > I see some > - non exported packages (e.g. org.apache.sling.auth.form.impl.jaas, in > general all sub package of impl packages seem to be incorrectly included) > - some embedded third party packages (e.g. org.quartz.simpl) in it. > > Konrad > >> On 17. Jan 2025, at 11:49, Stefan Seifert >> <[email protected]> wrote: >> >> sling 13 release is done. it took a bit longer than expected due to several >> tooling issues around further switching to Java 17 and to Java 21 since the >> last release, and I took a bit more time to fix the root causes around the >> tooling problems, and tried to simplify the process at some places. however, >> the whole process was already very well prepared by robert over the last >> years, thanks for this good foundation, robert! >> >> looking forward for Sling 14, it would be nice to include: >> - Supporting Jakarta Servlet Specification >> - Getting rid of javax.json completely and finalizing the switch to >> jakarta.json >> - Rename the remaining related modules/github repos from "launchpad" to >> starter to get rid of the old name >> >> as discussed in the last meetings, we should not wait again 2,5 years with >> the next release. this is not only looking strange from outside, it also >> comes with the risk of accumulating lots of potential problems which then >> makes doing a new release harder. normally, doing a sling starter release >> should not take that much of time with a lot of road blocks removed. so >> maybe 2 releases in a year would be fine from my point of view. >> >> stefan >
