On Fri, 2019-03-29 at 10:31 +0100, Bertrand Delacretaz wrote: > On Fri, Mar 29, 2019 at 10:13 AM Robert Munteanu <romb...@apache.org> > wrote: > > ...I suggest we use 'org.apache.sling.cli' as the artifactId and > > 'sling- > > org-apache-sling-cli' as the repository... > > IIUC this tool is specifically about automating release, so how about > a more specific name? > > org-apache-sling-release-cli ?
Hi Bertrand, I'm a bit undecided about this. Currently this is about releases, supporting the 'release' command and some other subcommands, e.g. release list release prepare-email release tally-votes release update-local-site I am thinking that this CLI may the the basis for other commands. One which I would benefit personally from would be a code grep one, which searches the Sling repos. Additionally some github integration would be useful such as pull-request list to list all open pull requests, which could be the basis of solving PRB-CONTRIB from [1]. Anyway, org-apache-sling-release-cli sounds OK to me, at least initially, and we can rename it later. Thanks, Robert [1]: https://cwiki.apache.org/confluence/display/SLING/Scaling+Sling+Development
