Re: [commons-release-plugin] Next

> On May 13, 2018, at 4:18 PM, Gary Gregory wrote: > > On Sun, May 13, 2018, 12:00 Rob Tompkins > wrote: > >> >> >>> On May 13, 2018, at 10:26 AM, Gary Gregory >> wrote: >>> >>> To be clear, I think we need a new goal for >>> http://commons.apache.org/proper/com

Re: [commons-release-plugin] Next

On Sun, May 13, 2018, 12:00 Rob Tompkins wrote: > > > > On May 13, 2018, at 10:26 AM, Gary Gregory > wrote: > > > > To be clear, I think we need a new goal for > > http://commons.apache.org/proper/commons-build-plugin/index.html, one > that > > invokes all. That would mean a new version of the _

Re: [commons-release-plugin] Next

> On May 13, 2018, at 10:26 AM, Gary Gregory wrote: > > To be clear, I think we need a new goal for > http://commons.apache.org/proper/commons-build-plugin/index.html, one that > invokes all. That would mean a new version of the _build_ plugin, as > opposed to the _release_ plugin. > Right. T

Re: [commons-release-plugin] Next

To be clear, I think we need a new goal for http://commons.apache.org/proper/commons-build-plugin/index.html, one that invokes all. That would mean a new version of the _build_ plugin, as opposed to the _release_ plugin. Gary On Sat, May 12, 2018 at 2:51 PM, Rob Tompkins wrote: > I can hop in a

Re: [commons-release-plugin] Next

I can hop in and help out with some of those. And probably can put some time into the plugin this week. > On May 12, 2018, at 11:40 AM, Gary Gregory wrote: > >> On Fri, May 11, 2018 at 7:53 PM, Rob Tompkins wrote: >> >> >> >>> On May 10, 2018, at 12:11 PM, Gary Gregory >> wrote: >>>

Re: [commons-release-plugin] Next

I'm going to want to release [weaver] soon as well, so I might like to participate with plugin development. Matt On Sat, May 12, 2018, 10:40 AM Gary Gregory wrote: > On Fri, May 11, 2018 at 7:53 PM, Rob Tompkins wrote: > > > > > > > > On May 10, 2018, at 12:11 PM, Gary Gregory > > wrote: > >

Re: [commons-release-plugin] Next

On Fri, May 11, 2018 at 7:53 PM, Rob Tompkins wrote: > > > > On May 10, 2018, at 12:11 PM, Gary Gregory > wrote: > > > > On Thu, May 10, 2018 at 9:53 AM, Matt Sicker wrote: > > > >> On 10 May 2018 at 09:34, Gary Gregory wrote: > >> > >>> Another item would be to have ONE Maven call instead of

Re: [commons-release-plugin] Next

> On May 10, 2018, at 12:11 PM, Gary Gregory wrote: > > On Thu, May 10, 2018 at 9:53 AM, Matt Sicker wrote: > >> On 10 May 2018 at 09:34, Gary Gregory wrote: >> >>> Another item would be to have ONE Maven call instead of SIX for: >>> >> >> It would be great to just do "mvn release:prepare

Re: [commons-release-plugin] Next

On Thu, May 10, 2018 at 9:53 AM, Matt Sicker wrote: > On 10 May 2018 at 09:34, Gary Gregory wrote: > > > Another item would be to have ONE Maven call instead of SIX for: > > > > It would be great to just do "mvn release:prepare release:perform", fill > out the release candidate version, and then

Re: [commons-release-plugin] Next

On 10 May 2018 at 09:34, Gary Gregory wrote: > Another item would be to have ONE Maven call instead of SIX for: > It would be great to just do "mvn release:prepare release:perform", fill out the release candidate version, and then have everything uploaded and emailed properly. Unfortunately, I'm

Re: [commons-release-plugin] Next

On Thu, May 10, 2018 at 8:42 AM, Rob Tompkins wrote: > > > > On May 10, 2018, at 10:34 AM, Gary Gregory > wrote: > > > >> On Wed, May 9, 2018 at 12:06 PM, Matt Sicker wrote: > >> > >>> On 9 May 2018 at 12:11, Gary Gregory wrote: > >>> > >>> Also, generating the VOTE email is a minor pain and e

Re: [commons-release-plugin] Next

> On May 10, 2018, at 10:34 AM, Gary Gregory wrote: > >> On Wed, May 9, 2018 at 12:06 PM, Matt Sicker wrote: >> >>> On 9 May 2018 at 12:11, Gary Gregory wrote: >>> >>> Also, generating the VOTE email is a minor pain and error prone. I >> usually >>> mess up the "vote ends at this date and t

Re: [commons-release-plugin] Next

On Wed, May 9, 2018 at 12:06 PM, Matt Sicker wrote: > On 9 May 2018 at 12:11, Gary Gregory wrote: > > > Also, generating the VOTE email is a minor pain and error prone. I > usually > > mess up the "vote ends at this date and time" part. If we do this part, > we > > should probably only worry abo

Re: [commons-release-plugin] Next

On 9 May 2018 at 12:11, Gary Gregory wrote: > Also, generating the VOTE email is a minor pain and error prone. I usually > mess up the "vote ends at this date and time" part. If we do this part, we > should probably only worry about git since we just VOTEd to move everything > from svn to git. >

Re: [commons-release-plugin] Next

On Wed, May 9, 2018 at 11:28 AM, Rob Tompkins wrote: > > > > On May 9, 2018, at 1:11 PM, Gary Gregory wrote: > > > >> On Wed, May 9, 2018 at 9:38 AM, Gary Gregory > wrote: > >> > >>> On Wed, May 9, 2018 at 9:29 AM, Rob Tompkins > wrote: > >>> > >>> That seems like a good idea. > >>> > >> > >>

Re: [commons-release-plugin] Next

> On May 9, 2018, at 1:11 PM, Gary Gregory wrote: > >> On Wed, May 9, 2018 at 9:38 AM, Gary Gregory wrote: >> >>> On Wed, May 9, 2018 at 9:29 AM, Rob Tompkins wrote: >>> >>> That seems like a good idea. >>> >> >> For me, it's what happens _after_ a VOTE passes that is the most time >> con

Re: [commons-release-plugin] Next

On Wed, May 9, 2018 at 9:38 AM, Gary Gregory wrote: > On Wed, May 9, 2018 at 9:29 AM, Rob Tompkins wrote: > >> That seems like a good idea. >> > > For me, it's what happens _after_ a VOTE passes that is the most time > consuming. Any help there would be great. > Also, generating the VOTE email

Re: [commons-release-plugin] Next

On Wed, May 9, 2018 at 9:29 AM, Rob Tompkins wrote: > That seems like a good idea. > For me, it's what happens _after_ a VOTE passes that is the most time consuming. Any help there would be great. Gary > > > On May 9, 2018, at 11:27 AM, Gary Gregory > wrote: > > > > Rob and all: > > > > What

Re: [commons-release-plugin] Next

That seems like a good idea. > On May 9, 2018, at 11:27 AM, Gary Gregory wrote: > > Rob and all: > > What's next for the release plugin? How about handling moving the files > from dist to release as noted in > http://commons.apache.org/releases/release.html (Steps 1 and 2)? > > Gary ---

[commons-release-plugin] Next

Rob and all: What's next for the release plugin? How about handling moving the files from dist to release as noted in http://commons.apache.org/releases/release.html (Steps 1 and 2)? Gary