You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Konrad Windszus <ko...@gmx.de> on 2021/09/21 15:21:33 UTC

Re: Release Management: Always update to latest parent prior release?

I proposed a small change to https://sling.apache.org/documentation/development/release-management.html in https://github.com/apache/sling-site/pull/69/files
Konrad

> On 7. Aug 2021, at 10:18, Carsten Ziegeler <cz...@apache.org> wrote:
> 
> As others said, depending on how old the current parent pom is, the update is non trivial and requires a lot of careful reworking. It can happen to easy that the module builds and tests pass, but the result is missing OSGi metadata.
> 
> So recommendation: absolutely yes, requiring: no.
> 
> And the good thing is everyone can help with these parent pom updates. You don't need deep knowledge about the details of the module. Make it build and pass the tests and compare the resulting jar with the previous one and check contents and metadata.
> 
> Regards
> Carsten
> -- 
> Carsten Ziegeler
> Adobe
> cziegeler@apache.org