Re: [commons-release-plugin] Next

[Rob Tompkins]

> 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/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. That was my impression.
>> 
> 
> I have a first cut done. Can you review?

Looking.


> 
> Gary
> 
> 
>>> Gary
>>> 
 On Sat, May 12, 2018 at 2:51 PM, Rob Tompkins 
>> wrote:
 
 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:
>>> 
 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 have everything uploaded
 and
 emailed properly. Unfortunately, I'm not familiar enough with maven
>> to
>> know
 how to automate that sort of thing (in the past, I've usually
 offloaded
 that part to a CI pipeline script of some sort).
 
>>> 
>>> Right, in a dream world, there would be a simple one-liner for
>> creating
>> an
>>> RC and another for promoting an RC to release.
>> 
>> All steps in that direction. I figure tackle the hard bits first, then
>> sort the remainders out. :-)
>> 
> 
> I'd like to release collections, text, pool, lang soon, so the better
>> the
> plugin, the happier the RM ;-)
> 
> I'm not sure how much time I can devote to helping on the plugin but I
>> am
> around to discuss and test.
> 
> Gary
> 
> 
>>> 
>>> Gary
>>> 
>>> 
 
 
 --
 Matt Sicker 
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org
 
 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@commons.apache.org 
>> 

Re: [commons-release-plugin] Next

[Gary Gregory]

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 _build_ plugin, as
> > opposed to the _release_ plugin.
> >
>
> Right. That was my impression.
>

I have a first cut done. Can you review?

Gary


> > Gary
> >
> >> On Sat, May 12, 2018 at 2:51 PM, Rob Tompkins 
> wrote:
> >>
> >> 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:
> >
> >> 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 have everything uploaded
> >> and
> >> emailed properly. Unfortunately, I'm not familiar enough with maven
> to
>  know
> >> how to automate that sort of thing (in the past, I've usually
> >> offloaded
> >> that part to a CI pipeline script of some sort).
> >>
> >
> > Right, in a dream world, there would be a simple one-liner for
> creating
>  an
> > RC and another for promoting an RC to release.
> 
>  All steps in that direction. I figure tackle the hard bits first, then
>  sort the remainders out. :-)
> 
> >>>
> >>> I'd like to release collections, text, pool, lang soon, so the better
> the
> >>> plugin, the happier the RM ;-)
> >>>
> >>> I'm not sure how much time I can devote to helping on the plugin but I
> am
> >>> around to discuss and test.
> >>>
> >>> Gary
> >>>
> >>>
> >
> > Gary
> >
> >
> >>
> >>
> >> --
> >> Matt Sicker 
> >>
> 
> 
>  -
>  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>  For additional commands, e-mail: dev-h...@commons.apache.org
> 
> 
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [commons-release-plugin] Next

[Rob Tompkins]

> 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. That was my impression. 

> Gary
> 
>> On Sat, May 12, 2018 at 2:51 PM, Rob Tompkins  wrote:
>> 
>> 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:
> 
>> 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 have everything uploaded
>> and
>> emailed properly. Unfortunately, I'm not familiar enough with maven to
 know
>> how to automate that sort of thing (in the past, I've usually
>> offloaded
>> that part to a CI pipeline script of some sort).
>> 
> 
> Right, in a dream world, there would be a simple one-liner for creating
 an
> RC and another for promoting an RC to release.
 
 All steps in that direction. I figure tackle the hard bits first, then
 sort the remainders out. :-)
 
>>> 
>>> I'd like to release collections, text, pool, lang soon, so the better the
>>> plugin, the happier the RM ;-)
>>> 
>>> I'm not sure how much time I can devote to helping on the plugin but I am
>>> around to discuss and test.
>>> 
>>> Gary
>>> 
>>> 
> 
> Gary
> 
> 
>> 
>> 
>> --
>> Matt Sicker 
>> 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org
 
 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [commons-release-plugin] Next

[Gary Gregory]

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 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:
> >>>
>  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 have everything uploaded
> and
>  emailed properly. Unfortunately, I'm not familiar enough with maven to
> >> know
>  how to automate that sort of thing (in the past, I've usually
> offloaded
>  that part to a CI pipeline script of some sort).
> 
> >>>
> >>> Right, in a dream world, there would be a simple one-liner for creating
> >> an
> >>> RC and another for promoting an RC to release.
> >>
> >> All steps in that direction. I figure tackle the hard bits first, then
> >> sort the remainders out. :-)
> >>
> >
> > I'd like to release collections, text, pool, lang soon, so the better the
> > plugin, the happier the RM ;-)
> >
> > I'm not sure how much time I can devote to helping on the plugin but I am
> > around to discuss and test.
> >
> > Gary
> >
> >
> >>>
> >>> Gary
> >>>
> >>>
> 
> 
>  --
>  Matt Sicker 
> 
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [commons-release-plugin] Next

[Rob Tompkins]

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:
>>> 
 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 have everything uploaded and
 emailed properly. Unfortunately, I'm not familiar enough with maven to
>> know
 how to automate that sort of thing (in the past, I've usually offloaded
 that part to a CI pipeline script of some sort).
 
>>> 
>>> Right, in a dream world, there would be a simple one-liner for creating
>> an
>>> RC and another for promoting an RC to release.
>> 
>> All steps in that direction. I figure tackle the hard bits first, then
>> sort the remainders out. :-)
>> 
> 
> I'd like to release collections, text, pool, lang soon, so the better the
> plugin, the happier the RM ;-)
> 
> I'm not sure how much time I can devote to helping on the plugin but I am
> around to discuss and test.
> 
> Gary
> 
> 
>>> 
>>> Gary
>>> 
>>> 
 
 
 --
 Matt Sicker 
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [commons-release-plugin] Next

[Matt Benson]

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:
> > >
> > > 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 have everything uploaded
> and
> > >> emailed properly. Unfortunately, I'm not familiar enough with maven to
> > know
> > >> how to automate that sort of thing (in the past, I've usually
> offloaded
> > >> that part to a CI pipeline script of some sort).
> > >>
> > >
> > > Right, in a dream world, there would be a simple one-liner for creating
> > an
> > > RC and another for promoting an RC to release.
> >
> > All steps in that direction. I figure tackle the hard bits first, then
> > sort the remainders out. :-)
> >
>
> I'd like to release collections, text, pool, lang soon, so the better the
> plugin, the happier the RM ;-)
>
> I'm not sure how much time I can devote to helping on the plugin but I am
> around to discuss and test.
>
> Gary
>
>
> > >
> > > Gary
> > >
> > >
> > >>
> > >>
> > >> --
> > >> Matt Sicker 
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>

Re: [commons-release-plugin] Next

[Gary Gregory]

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 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 not familiar enough with maven to
> know
> >> how to automate that sort of thing (in the past, I've usually offloaded
> >> that part to a CI pipeline script of some sort).
> >>
> >
> > Right, in a dream world, there would be a simple one-liner for creating
> an
> > RC and another for promoting an RC to release.
>
> All steps in that direction. I figure tackle the hard bits first, then
> sort the remainders out. :-)
>

I'd like to release collections, text, pool, lang soon, so the better the
plugin, the happier the RM ;-)

I'm not sure how much time I can devote to helping on the plugin but I am
around to discuss and test.

Gary


> >
> > Gary
> >
> >
> >>
> >>
> >> --
> >> Matt Sicker 
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [commons-release-plugin] Next

[Rob Tompkins]

> 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 release:perform", fill
>> out the release candidate version, and then have everything uploaded and
>> emailed properly. Unfortunately, I'm not familiar enough with maven to know
>> how to automate that sort of thing (in the past, I've usually offloaded
>> that part to a CI pipeline script of some sort).
>> 
> 
> Right, in a dream world, there would be a simple one-liner for creating an
> RC and another for promoting an RC to release.

All steps in that direction. I figure tackle the hard bits first, then sort the 
remainders out. :-)

> 
> Gary
> 
> 
>> 
>> 
>> --
>> Matt Sicker 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [commons-release-plugin] Next

[Gary Gregory]

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 have everything uploaded and
> emailed properly. Unfortunately, I'm not familiar enough with maven to know
> how to automate that sort of thing (in the past, I've usually offloaded
> that part to a CI pipeline script of some sort).
>

Right, in a dream world, there would be a simple one-liner for creating an
RC and another for promoting an RC to release.

Gary


>
>
> --
> Matt Sicker 
>

Re: [commons-release-plugin] Next

[Matt Sicker]

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 not familiar enough with maven to know
how to automate that sort of thing (in the past, I've usually offloaded
that part to a CI pipeline script of some sort).


-- 
Matt Sicker 

Re: [commons-release-plugin] Next

[Gary Gregory]

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 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.
> >>>
> >>
> >> How about just saying the vote will last at least 72 hours? Emails have
> >> timestamps in them. ;)
> >>
> >
> > Genius idea! :-)
> >
> > Another item would be to have ONE Maven call instead of SIX for:
>
> Agree on that point. I suppose we could re-work the build plugin to do all
> of those at once, or to build another target that does all of them together
> leaving the separate ones as well.
>

I think creating a _new_ target is the way to go. I am sure some RMs will
want the finer grained control.

Curious: Have you looked at that code?

Gary


>
> -Rob
>
> >
> > Update the download xml file
> >> The download page on the website is created from the file
> >> src/site/xdoc/download_{component}.xml. The XML file is created using
> mvn
> >> commons:download-page [-Dcommons.release.version=m.n]. Check that the
> >> changes (if any) are correct and commit the updated file.
> >> Update the other autogenerated files
> >> Various files are autogenerated using the commons build plugin.
> >>
> >>   - CONTRIBUTING.md - mvn commons:contributing-md
> >>
> >>
> >>   - README.md - mvn commons:readme-md
> >>
> >>
> >>   - src/site/xdoc/issue-tracking.xml - mvn commons:jira-page
> >>
> >>
> >>   - src/site/xdoc/mail-lists.xml - mvn commons:mail-page
> >>
> >> Check that the changes (if any) are correct and commit the updated
> >> file(s).
> >
> >
> >
> > Gary
> >
> >
> >>
> >>
> >> --
> >> Matt Sicker 
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [commons-release-plugin] Next

[Rob Tompkins]

> 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 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.
>>> 
>> 
>> How about just saying the vote will last at least 72 hours? Emails have
>> timestamps in them. ;)
>> 
> 
> Genius idea! :-)
> 
> Another item would be to have ONE Maven call instead of SIX for:

Agree on that point. I suppose we could re-work the build plugin to do all of 
those at once, or to build another target that does all of them together 
leaving the separate ones as well. 

-Rob

> 
> Update the download xml file
>> The download page on the website is created from the file
>> src/site/xdoc/download_{component}.xml. The XML file is created using mvn
>> commons:download-page [-Dcommons.release.version=m.n]. Check that the
>> changes (if any) are correct and commit the updated file.
>> Update the other autogenerated files
>> Various files are autogenerated using the commons build plugin.
>> 
>>   - CONTRIBUTING.md - mvn commons:contributing-md
>> 
>> 
>>   - README.md - mvn commons:readme-md
>> 
>> 
>>   - src/site/xdoc/issue-tracking.xml - mvn commons:jira-page
>> 
>> 
>>   - src/site/xdoc/mail-lists.xml - mvn commons:mail-page
>> 
>> Check that the changes (if any) are correct and commit the updated
>> file(s).
> 
> 
> 
> Gary
> 
> 
>> 
>> 
>> --
>> Matt Sicker 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [commons-release-plugin] Next

[Gary Gregory]

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 about git since we just VOTEd to move
> everything
> > from svn to git.
> >
>
> How about just saying the vote will last at least 72 hours? Emails have
> timestamps in them. ;)
>

Genius idea! :-)

Another item would be to have ONE Maven call instead of SIX for:

Update the download xml file
> The download page on the website is created from the file
> src/site/xdoc/download_{component}.xml. The XML file is created using mvn
> commons:download-page [-Dcommons.release.version=m.n]. Check that the
> changes (if any) are correct and commit the updated file.
> Update the other autogenerated files
> Various files are autogenerated using the commons build plugin.
>
>- CONTRIBUTING.md - mvn commons:contributing-md
>
>
>- README.md - mvn commons:readme-md
>
>
>- src/site/xdoc/issue-tracking.xml - mvn commons:jira-page
>
>
>- src/site/xdoc/mail-lists.xml - mvn commons:mail-page
>
> Check that the changes (if any) are correct and commit the updated
> file(s).



Gary


>
>
> --
> Matt Sicker 
>

Re: [commons-release-plugin] Next

[Matt Sicker]

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

How about just saying the vote will last at least 72 hours? Emails have
timestamps in them. ;)


-- 
Matt Sicker 

Re: [commons-release-plugin] Next

[Gary Gregory]

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.
> >>>
> >>
> >> 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 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.
> >
>
> It doesn’t seem too hard to generate the VOTE email. I can put that in the
> backlog too.
>

Thanks Rob!

Gary


>
> -Rob
>
> > Gary
> >
> >
> >>
> >> Gary
> >>
> >>
> >>>
>  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
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >>> For additional commands, e-mail: dev-h...@commons.apache.org
> >>>
> >>>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [commons-release-plugin] Next

[Rob Tompkins]

> 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
>> consuming. Any help there would be great.
>> 
> 
> 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.
> 

It doesn’t seem too hard to generate the VOTE email. I can put that in the 
backlog too. 

-Rob

> Gary
> 
> 
>> 
>> Gary
>> 
>> 
>>> 
 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
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
>>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [commons-release-plugin] Next

[Gary Gregory]

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

Gary


>
> Gary
>
>
>>
>> > 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
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>

Re: [commons-release-plugin] Next

[Gary Gregory]

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'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
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [commons-release-plugin] Next

[Rob Tompkins]

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


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org