Perfect thanks. Is this considered mature enough to be the default release 
process?
I think at least a hint to that tool would be nice within 
https://sling.apache.org/documentation/development/release-management.html 
<https://sling.apache.org/documentation/development/release-management.html>.
I will definitely try that the next time I do a release.
Konrad

> On 13. Jun 2019, at 16:40, Robert Munteanu <[email protected]> wrote:
> 
> Hi Konrad,
> 
> On Wed, 2019-06-12 at 16:33 +0200, Konrad Windszus wrote:
>> I kind of missed those steps as well in the past. I thought that this
>> would be automatically done as soon as you push something to dist.
>> Can we aim for a better automation here?
>> Also from the script 
>> https://github.com/apache/sling-tooling-release/blob/master/update_reporter.sh
>> <
>> https://github.com/apache/sling-tooling-release/blob/master/update_reporter.sh
>>> it is not clear to me in which format the release file has to be
>> given. Can you provide an example?
>> Is it supposed to contain the full Maven G:A:V or rather the
>> filename?
> 
> I think that for release automation the committer CLI is the solution
> 
>  https://github.com/apache/sling-org-apache-sling-committer-cli
> 
> It allows a release manager to execute various steps in an automated
> manner. It's still WIP, but you can:
> 
> - generate vote emails
> - generate vote result emails
> - create next jira version
> - record release data in reporter.apache.org
> - generate a diff to apply on the website
> 
> Thanks,
> 
> Robert
> 
>> Thanks,
>> Konrad
>> 
>>> On 12. Jun 2019, at 15:38, Robert Munteanu <[email protected]>
>>> wrote:
>>> 
>>> Hi Timothee,
>>> 
>>> On Wed, 2019-06-12 at 15:30 +0200, Timothee Maret wrote:
>>>> Hi Robert,
>>>> 
>>>> I am not sure if this is expected or even relevant but the list
>>>> of
>>>> releases
>>>> does not seem to include all the items from
>>>> https://sling.apache.org/releases.html
>>> 
>>> We should include all releases in the report. Which exactly are you
>>> missing? The release list is automatically generated 
>>> https://reporter.apache.org/ . The reporter relies on the PMC
>>> member
>>> that commits a new release to dist to also add it to
>>> reporter.apache.org . Maybe not all releases are added there, hence
>>> the
>>> discrepancy.
>>> 
>>> Thanks,
>>> 
>>> Robert
>>> 
> 

Reply via email to