Release Plugin (was Re: [All] Moving to git)

[Stefan Bodewig <bo...@apache.org>]

On 2014-12-31, Jochen Wiedmann wrote:

> On Mon, Dec 29, 2014 at 3:16 PM, Stefan Bodewig <bo...@apache.org> wrote:

>> Just as a "letter of intent" - I'd prefer to cut Compress 1.10 while
>> we're still in svn (as I know how to do it, I'm in the "avoid the
>> release plugin" camp) and call for a vote for moving to git after that.

> 1.) And why don't you intend to use this plugin? I know, it is a
> non-trivial task to use it, but my impression is that it's worth to
> struggle yourself through.

I have tons of experience with the release plugin at work, with git and
with svn.  And it's the reason I avoid it as it has cost me a lot of
time in the past.

Some of my problems are probably really just "my" problems.  I've got a
pretty flaky and slow network upstream and it has happened more than
once that "deploy" of one file failed and I had to roll back the whole
release process, drop the staging repo and so on.  By now I create an
upload bundle manually (not really manually, but not using Maven) and
upload a single file.  And the whole process of tagging and creating
archives is separated from that.

So my main beef is the release plugin is doing a lot of things and if a
single one of them fails I have to perform quite a bit of manual cleanup
and then must start over again.  My "manual approach" is a lot more
forgiving.

> 2.) Has anyone already attempted to use the release plugin with git?

In my experience the release plugin works as well or bad with git as it
does with svn.

Stefan

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

Re: Release Plugin (was Re: [All] Moving to git)

[Torsten Curdt <tc...@vafer.org>]

On Wed, Dec 31, 2014 at 11:34 AM, Stefan Bodewig <bo...@apache.org> wrote:

> On 2014-12-31, Jochen Wiedmann wrote:
>
> > On Mon, Dec 29, 2014 at 3:16 PM, Stefan Bodewig <bo...@apache.org>
> wrote:
>
> >> Just as a "letter of intent" - I'd prefer to cut Compress 1.10 while
> >> we're still in svn (as I know how to do it, I'm in the "avoid the
> >> release plugin" camp) and call for a vote for moving to git after that.
>
> > 1.) And why don't you intend to use this plugin? I know, it is a
> > non-trivial task to use it, but my impression is that it's worth to
> > struggle yourself through.
>
> I have tons of experience with the release plugin at work, with git and
> with svn.  And it's the reason I avoid it as it has cost me a lot of
> time in the past.


> Some of my problems are probably really just "my" problems.


I doubt that.


I've got a
> pretty flaky and slow network upstream and it has happened more than
> once that "deploy" of one file failed and I had to roll back the whole
> release process, drop the staging repo and so on.  By now I create an
> upload bundle manually (not really manually, but not using Maven) and
> upload a single file.  And the whole process of tagging and creating
> archives is separated from that.
>

Same here.


So my main beef is the release plugin is doing a lot of things and if a
> single one of them fails I have to perform quite a bit of manual cleanup
> and then must start over again.  My "manual approach" is a lot more
> forgiving.
>

Couldn't agree more. That said - it's been a while since I last tried it.

cheers,
Torsten

Re: Release Plugin (was Re: [All] Moving to git)

[Christopher <ct...@apache.org>]

On Wed, Dec 31, 2014 at 5:34 AM, Stefan Bodewig <bo...@apache.org> wrote:

> On 2014-12-31, Jochen Wiedmann wrote:
>
> > On Mon, Dec 29, 2014 at 3:16 PM, Stefan Bodewig <bo...@apache.org>
> wrote:
>
> >> Just as a "letter of intent" - I'd prefer to cut Compress 1.10 while
> >> we're still in svn (as I know how to do it, I'm in the "avoid the
> >> release plugin" camp) and call for a vote for moving to git after that.
>
> > 1.) And why don't you intend to use this plugin? I know, it is a
> > non-trivial task to use it, but my impression is that it's worth to
> > struggle yourself through.
>
> I have tons of experience with the release plugin at work, with git and
> with svn.  And it's the reason I avoid it as it has cost me a lot of
> time in the past.
>
> Some of my problems are probably really just "my" problems.  I've got a
> pretty flaky and slow network upstream and it has happened more than
> once that "deploy" of one file failed and I had to roll back the whole
> release process, drop the staging repo and so on.  By now I create an
> upload bundle manually (not really manually, but not using Maven) and
> upload a single file.  And the whole process of tagging and creating
> archives is separated from that.
>
> So my main beef is the release plugin is doing a lot of things and if a
> single one of them fails I have to perform quite a bit of manual cleanup
> and then must start over again.  My "manual approach" is a lot more
> forgiving.
>
> > 2.) Has anyone already attempted to use the release plugin with git?
>
> In my experience the release plugin works as well or bad with git as it
> does with svn.
>
> Stefan
>
>
In my experience, it works much, much better. We use it with Accumulo on
git:
https://repo1.maven.org/maven2/org/apache/accumulo/accumulo/1.6.1/accumulo-1.6.1.pom

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii