[VOTE] commons-fileupload 1.2 (rc2)

[Jochen Wiedmann <jo...@gmail.com>]

Hi,

after IO 1.3 is out, I've made a second release candidate available
for review on

    http://people.apache.org/~jochen/commons-fileupload/dist

The proposed site can be viewed at

    http://people.apache.org/~jochen/commons-fileupload/site

The site includes clirr and checkstyle reports, a rat report is at

    http://people.apache.org/~jochen/commons-fileupload/dist/rat.txt

(This report was created by using the rat-maven-plugin, btw.)

Please cast your vote:

[ ] +1
[ ] =0
[ ] -1

I'll keep the vote open until saturday, if noone else intervenes.

Jochen


-- 
How fast can a year go? As fast as your childs first year.

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

Re: [VOTE] commons-fileupload 1.2 (rc2)

[Henri Yandell <fl...@gmail.com>]

Also - the build is built using 1.6.0-rc with source/binary flags set
for 1.3. I'm happy to do that and let the user report if they find
they can't use it on 1.3+, but others seem to care strongly so just
reporting it.

Is 1.6.0-rc the released version or one of the betas? Not sure what
Sun's naming convention is there.

Hen

On 2/5/07, Henri Yandell <fl...@gmail.com> wrote:
> On 2/5/07, Jochen Wiedmann <jo...@gmail.com> wrote:
> > On 2/5/07, Henri Yandell <fl...@gmail.com> wrote:
> >
> > > * No zip file for the -src.
> >
> > Ok, added zip file generation to the source assembly.
> >
> > > * The tar.gz doesn't open into *-src/ directory.
> >
> > That wasn't the case for the previous fileupload releases. Why change it?
>
> No idea - other components do etc.
>
> Well, I say no idea - I think generally because it's a pattern for
> foo.tgz to unpack into foo and bar.zip to unpack into bar. And so that
> the binary and src archives can unpack next to each other.
>
> > > * Unable to find your key so I can verify the pgp.
> >
> > See, for example,
> >
> >     http://www.apache.org/dist/ws/jaxme/KEYS
> >     http://www.apache.org/dist/ws/xmlrpc/KEYS
> >
> > You are right, of course, that an entry must be added to the KEYS file.
> >
> >
> > > Jars were built by Plexus, so does that mean this is a Maven2 release?
> >
> > Yes.
> >
> >
> > > Do we have a plan for how we'll do that?
> >
> > What's the deal?
>
> Just a radar thing - Maven2 releases (using the release manager) have
> flagged for me as something that could make changes on our release
> process so my radar is beeping.
>
> I'll reply to the Maven 2 thread that's been started.
>
> Hen
>

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

Re: [VOTE] commons-fileupload 1.2 (rc2)

[Henri Yandell <fl...@gmail.com>]

On 2/5/07, Jochen Wiedmann <jo...@gmail.com> wrote:
> On 2/5/07, Henri Yandell <fl...@gmail.com> wrote:
>
> > * No zip file for the -src.
>
> Ok, added zip file generation to the source assembly.
>
> > * The tar.gz doesn't open into *-src/ directory.
>
> That wasn't the case for the previous fileupload releases. Why change it?

No idea - other components do etc.

Well, I say no idea - I think generally because it's a pattern for
foo.tgz to unpack into foo and bar.zip to unpack into bar. And so that
the binary and src archives can unpack next to each other.

> > * Unable to find your key so I can verify the pgp.
>
> See, for example,
>
>     http://www.apache.org/dist/ws/jaxme/KEYS
>     http://www.apache.org/dist/ws/xmlrpc/KEYS
>
> You are right, of course, that an entry must be added to the KEYS file.
>
>
> > Jars were built by Plexus, so does that mean this is a Maven2 release?
>
> Yes.
>
>
> > Do we have a plan for how we'll do that?
>
> What's the deal?

Just a radar thing - Maven2 releases (using the release manager) have
flagged for me as something that could make changes on our release
process so my radar is beeping.

I'll reply to the Maven 2 thread that's been started.

Hen

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

Re: [VOTE] commons-fileupload 1.2 (rc2)

[Jochen Wiedmann <jo...@gmail.com>]

On 2/5/07, Henri Yandell <fl...@gmail.com> wrote:

> * No zip file for the -src.

Ok, added zip file generation to the source assembly.

> * The tar.gz doesn't open into *-src/ directory.

That wasn't the case for the previous fileupload releases. Why change it?


> * Unable to find your key so I can verify the pgp.

See, for example,

    http://www.apache.org/dist/ws/jaxme/KEYS
    http://www.apache.org/dist/ws/xmlrpc/KEYS

You are right, of course, that an entry must be added to the KEYS file.


> Jars were built by Plexus, so does that mean this is a Maven2 release?

Yes.


> Do we have a plan for how we'll do that?

What's the deal?


> I'm thinking:
>
> * Change group id?

Couldn't we do that *after* the release, please? I would clearly
prefer *not* to introduce any incompatible changes in that stage.


> * How do we build a 2.0 release and vote on that rather than voting on
> the release manager's ability to do a release? Is there a way to
> deploy known files to an m2 repository rather than having to rebuild?

I never intended to publish the exact distributables that we voted on.
For example, I never intented to change version numbers within the
binary distributables from 1.2rc2 to 1.2. How do others do that?

Afar from that, I never intended to use the release manager. To be
honest, I never got it working. I was thinking along the lines of

    mvn -Drelease clean install site assembly:assembly deploy

Which is (apart from the "deploy") exactly what I did to build the
current files.

If you insist, I can omit the "deploy" and do the deployment manually.
(In other words, omit rebuilding the files.) That said, I spent a lot
of time in an automatic build exactly for *not* requiring any manual
interventions, because I trust my build system more than myself.


> * How much of the release code can be shared - I can see stuff in the
> pom.xml, can that stuff be in the parent pom?

Yes, but my clear intention was *not* to wait for a release of
commons-parent again (I already did so last year for several months),
rather than learning from this release and then move the stuff up
later. (Note, that I did all changes in a branch, to allow me for
careful integration into either trunk or commons-parent later.)


Jochen

-- 
How fast can a year go? As fast as your childs first year.

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

Re: [VOTE] commons-fileupload 1.2 (rc2)

[Henri Yandell <fl...@gmail.com>]

* No zip file for the -src.
* The tar.gz doesn't open into *-src/ directory.
* Unable to find your key so I can verify the pgp.

--

MD5s good.
Ant, Maven and Maven2 all work from the src tar.gz.

Jars were built by Plexus, so does that mean this is a Maven2 release?
Do we have a plan for how we'll do that?

I'm thinking:

* Change group id?
* How do we build a 2.0 release and vote on that rather than voting on
the release manager's ability to do a release? Is there a way to
deploy known files to an m2 repository rather than having to rebuild?
* How much of the release code can be shared - I can see stuff in the
pom.xml, can that stuff be in the parent pom?

Hen

On 2/1/07, Jochen Wiedmann <jo...@gmail.com> wrote:
> Hi,
>
> after IO 1.3 is out, I've made a second release candidate available
> for review on
>
>     http://people.apache.org/~jochen/commons-fileupload/dist
>
> The proposed site can be viewed at
>
>     http://people.apache.org/~jochen/commons-fileupload/site
>
> The site includes clirr and checkstyle reports, a rat report is at
>
>     http://people.apache.org/~jochen/commons-fileupload/dist/rat.txt
>
> (This report was created by using the rat-maven-plugin, btw.)
>
> Please cast your vote:
>
> [ ] +1
> [ ] =0
> [ ] -1
>
> I'll keep the vote open until saturday, if noone else intervenes.
>
> Jochen
>
>
> --
> How fast can a year go? As fast as your childs first year.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>

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