Thanks Oliver for the feedback and in retrospect I agree regarding the name, jcr.repository is redundant. What's the best approach here? Should I cancel this vote and reopen for:
Proposed Github Repo name: sling-org-apache-sling-jcr-maintenance Proposed artifact id (group id: org.apache.sling) - org.apache.sling.jcr.maintenance Or can we do a "no objection" vote? On Wed, Jan 13, 2021 at 3:55 PM Oliver Lietz <[email protected]> wrote: > On Tuesday, January 12, 2021 3:15:08 AM CET Daniel Klco wrote: > > Hi, > > Hi Dan, > > > This is a vote to promote the org.apache.sling.jcr.repositorymaintenance > to > > its own Sling Module. This module contains three jobs to kick off > > repository maintenance for the JCR repository: > > > > - Datastore Garbage Collection > > - Blobstore Garbage collection > > - Version Cleanup > > > > The project includes the bundle as well as two Sling OSGi features, one > for > > just the base needs and one which schedules the jobs at 2:00 AM every > day. > > > > 1. Code Location: in the ‘sling-whiteboard’ under > > 'sling-org-apache-sling-jcr-repositorymaintenance` folder > > 2. Proposed Github Repo name: > > - sling-org-apache-sling-jcr-repositorymaintenance > > 3. Proposed artifact id (group id: org.apache.sling) > > - org.apache.sling.jcr.repositorymaintenance > > > > The idea would be to incorporate these into the starter and CMS as per: > > https://issues.apache.org/jira/browse/SLING-9985 > > There are still several typos related to maintenance and I would prefer a > less > bulky name. For me org.apache.sling.jcr.maintenance would work fine as we > have > "repository" already in JCR. > I guess we became less picky when it comes to JCR vs Jackrabbit vs Oak. > > > Please cast your votes > > > > [ ] +1 Approve the promotion > > [ ] 0 Don't care > > [ ] -1 Don't promote, because ... > > > > Votes will be open for at least 72h. > > Otherwise +1 > > O. > > > -Dan > > > > >
