I would not be opposed to requiring (or at least recommending) to update to the latest parent before each release. Especially if doing so doesn't require any substantial additional work.
It's not a good experience to keep running into modules that won't build with Java 11, so anything that encourages moving to a compatible parent would be good. On Fri, Aug 6, 2021 at 5:29 AM Robert Munteanu <[email protected]> wrote: > Hi Konrad, > > On Fri, 2021-08-06 at 13:36 +0200, Konrad Windszus wrote: > > > > What do you think about adding a check to the release management page > > in > > > https://sling.apache.org/documentation/development/release-management.html#prerequisites > > < > > > https://sling.apache.org/documentation/development/release-management.html#prerequisites > > > that the module must reference the latest Sling Parent? > > Updating to the latest parent module version is not always easy, > especially with the maven-bundle-plugin → bnd-maven-plugin migration > and switching from the Felix annotations to the official OSGi ones. > > I would be very happy to see all modules updated to the latest parent > pom, but I think it's not going to be always feasible. > > Thanks, > Robert > >
