commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [VOTE] Release Apache Commons Daemon 1.1.0 based on RC2
Date Thu, 09 Nov 2017 21:43:04 GMT
On Thu, Nov 9, 2017 at 2:35 PM, Mark Thomas <markt@apache.org> wrote:

> On 09/11/17 20:18, Gary Gregory wrote:
> > There is a lot of required information missing from this VOTE request.
>
> No there isn't. The VOTE contains more than the minimum necessary
> information for a VOTE that is consistent with ASF policy.
>
> Take a look at a typical httpd vote thread:
> http://markmail.org/thread/t5qjo3s6cnis6dag


This is not httpd, their PMC can decide on their own rules of engagement.


>
>
> > How about following the format in
> > http://commons.apache.org/releases/prepare.html ?
>
> Commons seems to have added an awful lot of additional requirements.
> Working through them:
>
> Listing the Maven artefacts and hashes is unnecessary given the staging
> repo URL and the auditing we have in place around repository actions.
>

This is all about tractability of what we vote on. If cutting and pasting
the list of files and hashes from the email Nexus sends you is too much
work, well, I'm not sure what to say.

Any SVN URL should be accompanied with a revision number.


> The site is not part of the release and as such does not need to be
> voted on. In addition, now that people.a.o does not allow shell access
> publishing a draft site is rather more involved. Simpler for folks just
> to build it locally and review it if they want to.
>

The simple solution I've been using is to publish a zipped site on p.a.o.
It all depends on how much work you want to give reviewers. Some reviewers
like to compare what they build from source with what an RM puts out.

Gary


>
> With uploading a working draft site no longer possible, providing links
> to RAT and Clirr reports is not as simple as it once was. Added to
> which, if folks want to base their vote on the RAT and Clirr reports
> then to be sure they see the correct results they should generate them
> locally. Given they'll have to build from source anyway, generating
> those reports (and the rest of the site) is only one more command.
>
> What the RM has tested and how belongs in the RM's vote e-mail, not in
> the original call for a VOTE.
>
> Mark
>
> >
> > Gary
> >
> > On Thu, Nov 9, 2017 at 1:15 PM, Mark Thomas <markt@apache.org> wrote:
> >
> >> The Apache Commons Deamon 1.1.0 release based on RC2 is now ready for
> >> voting.
> >>
> >> It can be obtained from:
> >> https://dist.apache.org/repos/dist/dev/commons/daemon/
> >>
> >> The Maven staging repo is:
> >> https://repository.apache.org/content/repositories/
> orgapachecommons-1291/
> >>
> >> The svn tag is:
> >> https://svn.apache.org/repos/asf/commons/proper/daemon/
> >> tags/COMMONS_DAEMON_1_1_0_RC2/
> >> (r1814731)
> >>
> >>
> >> The proposed release is:
> >>
> >> The proposed 1.1.0 release based on RC2 is:
> >> [ ] Broken   - do not release because...
> >> [ ] Approved - go ahead and release as 1.1.0
> >>
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message