You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Robert Munteanu <ro...@apache.org> on 2019/06/12 07:56:45 UTC
June board report draft
Hi,
Please find the draft board report below. I plan to submit it this
afternoon (CEST), comments welcome.
Thanks,
Robert
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We continue to make individual module releases.
adapt.to - the "Apache Sling and friends" conference will take place
this
year in Berlin between the 2nd and the 4th of September 2019.
## Health report:
Good activity level overall, contributions from different people
continue.
## PMC changes:
- Currently 26 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andrei Dulvac on Mon Jul 30 2018
## Committer base changes:
- Currently 43 committers.
- No new committers added in the last 3 months
- Last committer addition was A. J. David Bosschaert at Fri Mar 09
2018
## Releases:
- Apache Sling Bundle Parent 35 was released on Mon Apr 22 2019
- Apache Sling Context-Aware Configuration Impl 1.4.16 was released on
Mon
May 06 2019
- Apache Sling Feature Analyser 1.0.0, Apache Sling Feature Launcher
1.0.0,
Apache Sling Feature Model Converter 1.0.0, Apache Sling Feature
Maven
Plugin 1.0.0 was released on Thu Apr 04 2019
- Apache Sling Feature Content Extension 1.0.0, Apache Sling Feature
API
Regions Extension 1.0.0, Apache Sling Feature API Regions Runtime
1.0.0, was
released on Mon Apr 15 2019
- Apache Sling File System Resource Provider 2.1.16, Sling Maven
Plugin
2.4.2 was released on Thu Jun 06 2019
- Apache Sling Installer Health Checks 2.0.2 was released on Fri May
24 2019
- Apache Sling Launchpad Base 6.0.2-2.6.36 was released on Tue Apr 02
2019
- Apache Sling Parent 35 was released on Mon Apr 22 2019
- Apache Sling Project Archetype 1.0.0 was released on Tue Apr 30
2019
- Apache Sling Repoinit JCR 1.1.10 was released on Thu May 02 2019
- Apache Sling Repoinit Parser 1.2.4 was released on Thu May 02 2019
- Apache Sling Scripting Core 2.0.58 was released on Mon May 27 2019
- Apache Sling Service User WebConsole 1.0.2 was released on Thu May
02 2019
- Apache Sling Servlet Helpers 1.2.0, Testing Sling Mock 2.3.12,
Testing
Sling Mock Oak 2.1.6 was released on Tue Jun 11 2019
- Apache Sling Testing Sling Mock 2.3.10 was released on Thu May 09
2019
- Apache Sling Testing Sling Mock 2.3.8, Sling Mock Oak 2.1.4 was
released
on Mon May 06 2019
- Apache Sling XSS Protection API 2.1.6 was released on Mon Apr 01
2019
- Apache Sling XSS Protection API 2.1.8 was released on Wed Apr 24
2019
- Apache Testing Sling Mock 2.3.6 was released on Mon Apr 01 2019
## JIRA activity:
- 166 JIRA tickets created in the last 3 months
- 161 JIRA tickets closed/resolved in the last 3 months
Re: Release automation (was: June board report draft)
Posted by Robert Munteanu <ro...@apache.org>.
On Thu, 2019-06-13 at 17:59 +0200, Konrad Windszus wrote:
> 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.
That's a good point, I've added a note. The docker image does not yet
perform all the steps, so I would not call recommend using it as the
default release tool.
However, it's good enough to be tested more.
Robert
> Konrad
>
> > On 13. Jun 2019, at 16:40, Robert Munteanu <ro...@apache.org>
> > 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 <ro...@apache.org>
> > > > 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
> > > >
Re: Release automation (was: June board report draft)
Posted by Konrad Windszus <ko...@gmx.de>.
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 <ro...@apache.org> 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 <ro...@apache.org>
>>> 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
>>>
>
Release automation (was: June board report draft)
Posted by Robert Munteanu <ro...@apache.org>.
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 <ro...@apache.org>
> > 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
> >
Re: June board report draft
Posted by Konrad Windszus <ko...@gmx.de>.
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?
Thanks,
Konrad
> On 12. Jun 2019, at 15:38, Robert Munteanu <ro...@apache.org> 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
>
Re: June board report draft
Posted by Robert Munteanu <ro...@apache.org>.
On Wed, 2019-06-12 at 16:27 +0200, Timothee Maret wrote:
> Hi Robert,
>
> Assuming the latest report was published on March 20th 2019 [0], then
> the
> following releases may need to be included.
>
> - Testing Sling Mock Oak 2.1.6
> - Webconsole Security Provider 1.2.2
> - Sling Maven Plugin 2.4.2
> - Testing PaxExam 3.0.0
> - Sling Default POST Servlets 2.3.30
> - Sling Form Based Authentication Handler 1.0.14
> - Sling Starter Content 1.0.4
> - Sling Project Archetype 1.0.1
> - Content Distribution Journal Messages 0.1.0
> - Content Distribution Journal Core 0.1.0
> - Content Distribution Journal Kafka 0.1.0
> - Content Distribution Journal ITs 0.1.0
> - Health Check API 1.0.4
> - Health Check Support Components 1.0.6
> - Installer Factory Configuration 1.2.2
> - Testing OSGi Mock 2.4.8
> - Servlet Helpers 1.1.10
> - Testing JCR Mock 1.4.4
> - Testing ResourceResolver Mock 1.1.24
>
> I compiled the diff myself. I can't access
> https://reporter.apache.org thus
> can't help you validate further what may be missing with the
> automated
> process.
Thanks, Timothee. That's a pretty large list ... I will include it in
the report manually.
I hope that the committer CLI referenced in my reply to Konrad will
make such things harder to overlook.
Thanks,
Robert
Re: June board report draft
Posted by Timothee Maret <tm...@apache.org>.
Thanks Robert! I can confirm I have access to the sling specific url.
Regards,
Timothee
Le jeu. 13 juin 2019 à 16:47, Robert Munteanu <ro...@apache.org> a écrit :
> On Wed, 2019-06-12 at 16:27 +0200, Timothee Maret wrote:
> > I can't access https://reporter.apache.org thus
> > can't help you validate further what may be missing with the
> > automated
> > process.
>
> I _think_ you should be able to access at least
> https://reporter.apache.org/addrelease.html?sling , which shows the
> currently recorded releases and a form to add new ones.
>
> I am currently adding the missing releases so this is just for you to
> check how the tool looks.
>
> Thanks,
>
> Robert
>
>
Re: June board report draft
Posted by Robert Munteanu <ro...@apache.org>.
On Wed, 2019-06-12 at 16:27 +0200, Timothee Maret wrote:
> I can't access https://reporter.apache.org thus
> can't help you validate further what may be missing with the
> automated
> process.
I _think_ you should be able to access at least
https://reporter.apache.org/addrelease.html?sling , which shows the
currently recorded releases and a form to add new ones.
I am currently adding the missing releases so this is just for you to
check how the tool looks.
Thanks,
Robert
Re: June board report draft
Posted by Timothee Maret <tm...@apache.org>.
Hi Robert,
Assuming the latest report was published on March 20th 2019 [0], then the
following releases may need to be included.
- Testing Sling Mock Oak 2.1.6
- Webconsole Security Provider 1.2.2
- Sling Maven Plugin 2.4.2
- Testing PaxExam 3.0.0
- Sling Default POST Servlets 2.3.30
- Sling Form Based Authentication Handler 1.0.14
- Sling Starter Content 1.0.4
- Sling Project Archetype 1.0.1
- Content Distribution Journal Messages 0.1.0
- Content Distribution Journal Core 0.1.0
- Content Distribution Journal Kafka 0.1.0
- Content Distribution Journal ITs 0.1.0
- Health Check API 1.0.4
- Health Check Support Components 1.0.6
- Installer Factory Configuration 1.2.2
- Testing OSGi Mock 2.4.8
- Servlet Helpers 1.1.10
- Testing JCR Mock 1.4.4
- Testing ResourceResolver Mock 1.1.24
I compiled the diff myself. I can't access https://reporter.apache.org thus
can't help you validate further what may be missing with the automated
process.
Regards,
Timothee
[0] https://whimsy.apache.org/board/minutes/Sling.html
Le mer. 12 juin 2019 à 15:38, Robert Munteanu <ro...@apache.org> a écrit :
> 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
>
>
Re: June board report draft
Posted by Robert Munteanu <ro...@apache.org>.
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
Re: June board report draft
Posted by Timothee Maret <tm...@apache.org>.
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
Regards,
Timothee
Le mer. 12 juin 2019 à 09:56, Robert Munteanu <ro...@apache.org> a écrit :
> Hi,
>
> Please find the draft board report below. I plan to submit it this
> afternoon (CEST), comments welcome.
>
> Thanks,
>
> Robert
>
>
> ## Description:
>
> Apache Sling™ is a framework for RESTful web-applications based on an
> extensible content tree.
>
> ## Issues:
>
> There are no issues requiring board attention at this time.
>
> ## Activity:
>
> We continue to make individual module releases.
>
> adapt.to - the "Apache Sling and friends" conference will take place
> this
> year in Berlin between the 2nd and the 4th of September 2019.
>
> ## Health report:
>
> Good activity level overall, contributions from different people
> continue.
>
> ## PMC changes:
>
> - Currently 26 PMC members.
> - No new PMC members added in the last 3 months
> - Last PMC addition was Andrei Dulvac on Mon Jul 30 2018
>
> ## Committer base changes:
>
> - Currently 43 committers.
> - No new committers added in the last 3 months
> - Last committer addition was A. J. David Bosschaert at Fri Mar 09
> 2018
>
> ## Releases:
>
> - Apache Sling Bundle Parent 35 was released on Mon Apr 22 2019
> - Apache Sling Context-Aware Configuration Impl 1.4.16 was released on
> Mon
> May 06 2019
> - Apache Sling Feature Analyser 1.0.0, Apache Sling Feature Launcher
> 1.0.0,
> Apache Sling Feature Model Converter 1.0.0, Apache Sling Feature
> Maven
> Plugin 1.0.0 was released on Thu Apr 04 2019
> - Apache Sling Feature Content Extension 1.0.0, Apache Sling Feature
> API
> Regions Extension 1.0.0, Apache Sling Feature API Regions Runtime
> 1.0.0, was
> released on Mon Apr 15 2019
> - Apache Sling File System Resource Provider 2.1.16, Sling Maven
> Plugin
> 2.4.2 was released on Thu Jun 06 2019
> - Apache Sling Installer Health Checks 2.0.2 was released on Fri May
> 24 2019
> - Apache Sling Launchpad Base 6.0.2-2.6.36 was released on Tue Apr 02
> 2019
> - Apache Sling Parent 35 was released on Mon Apr 22 2019
> - Apache Sling Project Archetype 1.0.0 was released on Tue Apr 30
> 2019
> - Apache Sling Repoinit JCR 1.1.10 was released on Thu May 02 2019
> - Apache Sling Repoinit Parser 1.2.4 was released on Thu May 02 2019
> - Apache Sling Scripting Core 2.0.58 was released on Mon May 27 2019
> - Apache Sling Service User WebConsole 1.0.2 was released on Thu May
> 02 2019
> - Apache Sling Servlet Helpers 1.2.0, Testing Sling Mock 2.3.12,
> Testing
> Sling Mock Oak 2.1.6 was released on Tue Jun 11 2019
> - Apache Sling Testing Sling Mock 2.3.10 was released on Thu May 09
> 2019
> - Apache Sling Testing Sling Mock 2.3.8, Sling Mock Oak 2.1.4 was
> released
> on Mon May 06 2019
> - Apache Sling XSS Protection API 2.1.6 was released on Mon Apr 01
> 2019
> - Apache Sling XSS Protection API 2.1.8 was released on Wed Apr 24
> 2019
> - Apache Testing Sling Mock 2.3.6 was released on Mon Apr 01 2019
>
> ## JIRA activity:
>
> - 166 JIRA tickets created in the last 3 months
> - 161 JIRA tickets closed/resolved in the last 3 months
>
>