Stefan, Thanks for the note. At one point my thought was that there should be a SPI exposed for extending the logic for Version Purging, but until required, YAGNI. I missed consolidating the packages during refactoring, but as stated since they're not exposed it could be done at any point.
On Tue, Feb 2, 2021 at 4:57 PM Stefan Seifert <stefan.seif...@diva-e.com.invalid> wrote: > +1 > > one cosmetic note: the name of the package > org.apache.sling.jcr.maintenance vs. > org.apache.sling.jcr.maintenance.internal seems to imply the first package > is exported via OSGi, the second not. but both are not exported (which is > probably by intention). the package names are a bit confusing - but they > can be changed later as they are not exported. > > stefan > > > >-----Original Message----- > >From: Daniel Klco <dk...@apache.org> > >Sent: Tuesday, February 2, 2021 5:35 AM > >To: dev@sling.apache.org > >Subject: [VOTE] Release Apache Sling JCR Maintenance version 1.0.0 > > > >Hi, > > > >We solved 2 issues in this release: > >https://issues.apache.org/jira/projects/SLING/versions/12349606 > > > >Staging repository: > >https://repository.apache.org/content/repositories/orgapachesling-2403/ > > > >You can use this UNIX script to download the release and verify the > >signatures: > >https://gitbox.apache.org/repos/asf?p=sling-tooling- > >release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > > >Usage: > >sh check_staged_release.sh 2403 /tmp/sling-staging > > > >Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] 0 Don't care > > [ ] -1 Don't release, because ... > > > >This majority vote is open for at least 72 hours. >
