Re: Ease of release process and exit criteria

On Fri, Aug 19, 2016 at 2:23 AM, Mark Thomas wrote: > Hi, > > I've noticed a pattern in some the board reports of PMCs who are > beginning to experience difficulties. In a notable number of cases a > significant part of the problem is difficulty in producing a release. > The sorts of phrases I am

Re: Ease of release process and exit criteria

In the JDO project, we have detailed build/release instructions, yet after several years, every time we put out a release, there is something different. I think it’s the nature of software, not only because the project changes ever so slightly but the dependencies also change underneath you. So

[Result] [VOTE] Releasing Apache Metron 0.2.0BETA-RC3

Vote passes with 3 +1 binding votes: - Taylor Goetz - Billie Rinaldi - Josh Elser And One non-binding vote - Debo Dutta Thanks to everyone who voted James On 8/17/16, 9:39 AM, "Josh Elser" wrote: >Casey, > >Thanks so much for the quick turn-around on JIRA issues. Great to see :) > >Re:

Re: [VOTE] Release Apache Ranger 0.6.1 (incubating) - rc2

+1 (binding) * xsums/sigs OK * Verified licensing issues from 0.6.0 were addressed (Thanks again, PPMC!) * Unit Tests passed * Could build from source * Verified tag in SCM * KEYS file is present Branding commentary: The website, notably the FAQ page[1], could use mention that the other ASF pr

RE: [VOTE] Apache Annotator

Thanks everyone for the votes! I’m told (by our Mentor), that we’re ready to move into the Incubator based on these results! I’m excited for this new error of collaboration for this project and to introduce so many amazing people to the Apache Software Foundation and it’s collaborative pro

Re: Ease of release process and exit criteria

As a data point, for Apache Geode we have a detailed release page: https://cwiki.apache.org/confluence/display/GEODE/Release+Steps We’ve been rotating RM’s for each release and the notes get enhanced each time through the process. Feedback welcome! Thanks, Anthony > On Aug 19, 2016, at 7:33 A

Re: Ease of release process and exit criteria

I know of a podling like that where the release manager gave me push back until I told him I could not vote +1 without build instructions I could at least follow on my own local. That was some years ago. The podling graduated. The instructions were not updated. The RM left. Now there is a bind.

Re: [VOTE] Release Apache Ranger 0.6.1 (incubating) - rc2

Great! Thanks for letting me know, Selva. Will take a look at 0.6.1 with that in mind. Selvamohan Neethiraj wrote: The License issues found in 0.6.0 IPMC vote has been resolved - https://issues.apache.org/jira/browse/RANGER-1109 and these changes are available as part of the 0.6.1 codebase. P

Re: Ease of release process and exit criteria

On Fri, Aug 19, 2016 at 6:18 AM Mark Struberg wrote: > Good links. > > I’d like to add some information for projects who use GIT with maven: > > First and important: configure the maven-release-plugin to operate > ‚locally‘ > https://github.com/apache/deltaspike/blob/master/pom.xml#L123 > > The i

RE: Ease of release process and exit criteria

+1 to this, including the posts from Mark and Bertrand. I know of a project where this would have made a serious difference for graduation and subsequent sustainability. - Dennis > -Original Message- > From: Shane Curcuru [mailto:a...@shanecurcuru.org] > Sent: Friday, August 19, 2016 0

RE: Ease of release process and exit criteria

> -Original Message- > From: Mark Struberg [mailto:strub...@yahoo.de.INVALID] > Sent: Friday, August 19, 2016 03:19 > To: general@incubator.apache.org > Subject: Re: Ease of release process and exit criteria > > Good links. > > I’d like to add some information for projects who use GIT w

Re: [VOTE] Release Apache Ranger 0.6.1 (incubating) - rc2

The License issues found in 0.6.0 IPMC vote has been resolved - https://issues.apache.org/jira/browse/RANGER-1109 and these changes are available as part of the 0.6.1 codebase. Please let me know if you need any further information on this. Thanks, Selva- From: Josh Elser Reply-To: "d...@ran

Re: [VOTE] Release Apache Ranger 0.6.1 (incubating) - rc2

Hi Selva, Were the licensing issues identified in the 0.6.0 IPMC vote resolved? [1] [2] If not, please do share the podling's plan to address the issue and when we can expect to see them fixed. Thanks! - Josh [1] https://s.apache.org/MSPd [2] https://s.apache.org/Cms1 Selvamohan Neethiraj

Re: Ease of release process and exit criteria

On 8/19/16, 7:08 AM, "Shane Curcuru" wrote: >Bertrand Delacretaz wrote on 8/19/16 5:57 AM: >> Hi Mark, >> >> On Fri, Aug 19, 2016 at 11:23 AM, Mark Thomas wrote: >>> ...I'm thinking of a graduation criteria long the lines of: >>> "Is the release process clearly documented to the point that so

Re: Ease of release process and exit criteria

Bertrand Delacretaz wrote on 8/19/16 5:57 AM: > Hi Mark, > > On Fri, Aug 19, 2016 at 11:23 AM, Mark Thomas wrote: >> ...I'm thinking of a graduation criteria long the lines of: >> "Is the release process clearly documented to the point that someone new >> to the project could produce a release bu

Re: Ease of release process and exit criteria

For Wicket I've crafted a release script that not only creates the artifacts to vote on, but also generates the messages needed for voting and announcing, and scripts to either promote or rollback a release. https://github.com/apache/wicket/blob/master/release.sh It uses the aforementioned settin

Re: Ease of release process and exit criteria

In addition, the release steps here are also available on DS's website - they've obviously been updated since the original, but are pretty close to Mark's email: http://deltaspike.apache.org/steps_for_a_release.html John On Fri, Aug 19, 2016 at 6:18 AM Mark Struberg wrote: > Good links. > > I’d

Re: Ease of release process and exit criteria

I would personally love it if we came up with some best practices for new projects as they're coming in. There's been a few very questionable ones done in the past, not that they're bad or incorrect, but do become burdensome. However, I've seen projects create amazing releases in short periods of

Re: Ease of release process and exit criteria

Good links. I’d like to add some information for projects who use GIT with maven: First and important: configure the maven-release-plugin to operate ‚locally‘ https://github.com/apache/deltaspike/blob/master/pom.xml#L123 The important parts are false true This will configure maven to NOT push

Re: Ease of release process and exit criteria

Hi Mark, On Fri, Aug 19, 2016 at 11:23 AM, Mark Thomas wrote: > ...I'm thinking of a graduation criteria long the lines of: > "Is the release process clearly documented to the point that someone new > to the project could produce a release build?"... I like this - as another example we have http

Ease of release process and exit criteria

Hi, I've noticed a pattern in some the board reports of PMCs who are beginning to experience difficulties. In a notable number of cases a significant part of the problem is difficulty in producing a release. The sorts of phrases I am seeing are along the lines of releases "are too difficult", "tak