Re: Release automation (was: June board report draft)

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 > < >

Re: June board report draft

Thanks Robert! I can confirm I have access to the sling specific url. Regards, Timothee Le jeu. 13 juin 2019 à 16:47, Robert Munteanu 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

Re: Release automation (was: June board report draft)

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 .

Re: June board report draft

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 ,

Re: June board report draft

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

Release automation (was: June board report draft)

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 >

Re: June board report draft

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

Re: June board report draft

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

Re: June board report draft

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

Re: June board report draft

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 a écrit : > Hi, > > Please find the draft board report

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

June board report draft

Hi, Please find the draft board report below. I will update it later on if we get additional info items until the report is due. Comments welcome. Thanks, Robert ## Description: Apache Sling™ is a framework for RESTful web-applications based on an extensible content tree. ## Issues: