incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <ctubb...@apache.org>
Subject Re: [VOTE] Apache Fluo 1.1.0-incubating (rc1)
Date Wed, 07 Jun 2017 00:59:48 GMT
On Tue, Jun 6, 2017 at 6:47 PM sebb <sebbaz@gmail.com> wrote:

> On 6 June 2017 at 23:38, Christopher <ctubbsii@apache.org> wrote:
> > On Tue, Jun 6, 2017 at 6:29 PM sebb <sebbaz@gmail.com> wrote:
> >
> >> On 6 June 2017 at 23:25, Christopher <ctubbsii@apache.org> wrote:
> >> > On Tue, Jun 6, 2017 at 6:03 PM sebb <sebbaz@gmail.com> wrote:
> >> >
> >> >> On 6 June 2017 at 21:15, Keith Turner <keith@deenlo.com> wrote:
> >> >> > Dear IPMC,
> >> >> >
> >> >> > Please vote for the following release candidate of Apache Fluo
> >> >> > 1.1.0-incubating.
> >> >> >
> >> >> > PPMC vote thread:
> >> >> >
> >> >>
> >>
> https://lists.apache.org/thread.html/c815b7a22fab10281ab2d4e88418a47a5903ba85327058bb727c7ccd@%3Cdev.fluo.apache.org%3E
> >> >> >
> >> >>
> >>
> https://lists.apache.org/thread.html/99508ef4a2b782b82494e4250713c1d0917b75cf7149bec64455bea2@%3Cdev.fluo.apache.org%3E
> >> >> >
> >> >> > Staged dist artifacts:
> >> >> >
> >> >>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/fluo/fluo/1.1.0-incubating-rc1/
> >> >>
> >> >> The hashes need to be in individual files, like the signature (.asc)
> >> >> [You can probably copy the corresponding ones from the Maven repo.]
> >> >>
> >> >> AFAIK the MD5SUM and SHA1SUM files should not be present.
> >> >>
> >> >> I'm not sure the .gitignore files should be there.
> >> >>
> >> >>
> >> >
> >> > I believe the *SUM files have been discussed before. I do not believe
> it
> >> to
> >> > be an issue, as INFRA excludes these from mirroring in the same way as
> >> > other files, and they are convenient.
> >>
> >> But the individual has files are still required.
> >>
> >>
> > Required by what policy?
> >
>
> http://www.apache.org/dev/release-distribution.html#sigs-and-sums
>
>

Thanks.

That's interesting. The current wording seems like a technical requirement
for the mirror distribution process. It seems like the intent (though, hard
to know for sure) was to follow a pattern that would ensure hashes aren't
mirrored. However, it is currently inconsistent with the actual behavior of
the mirror distribution process and also seems to apply to all other
infra-supported channels like Nexus. It also seems to be regularly
violated, since there are a *LOT* of projects which use variants, such as
".sha1" or ".sha256" or ".sha512" or ".mds" in dist/release. Also, every
Maven artifact deployed to Nexus is also in violation. That's not an excuse
to violate it again, of course... but it's a strong indication that the
page isn't accurately documenting the actual policy that INFRA enforces for
distribution through ASF infra channels.

Perhaps VP Infra would be willing to consider a change to the wording so it
more closely aligns with the actual requirements of the mirroring process.
I don't recall who that is at the moment. David Nalley, according to
https://home.apache.org/phonebook.html?pmc=infrastructure ? Is that right?
Or is it Greg Stein
(/foundation/officers/personnel-duties/infra-admin.txt)? Or should I just
start a conversation on an infra list somewhere? Or file a JIRA? I don't
know the best method to contact VP Infra to request update/clarification on
this policy issue.



> >> > I'm not sure what .gitignore files you're referring to. There are
> some in
> >> > the directories above the RC directory, to support using SVN with
> git-svn
> >> > (git ignores empty directories; the .gitignore file preserves them).
> >> There
> >> > aren't any inside the 1.1.0-incubating-rc1 directory, though.
> >>
> >> I'm referring to the ones in the parent directories.
> >>
> >> Since the dist tree is SVN only (and will remain that way) there is no
> >> need for them.
> >>
> >>
> >
> > They are needed by git-svn in order to preserve the empty directory in
> the
> > clone. They can be ignored for the purposes of this vote, since they
> aren't
> > even in the same directory as the release candidate files, and will not
> be
> > included in the `svn mv` upon a successful vote.
>
> OK, so long as they are not added to the dist/release directory area.
>
> >
> >
> >> >
> >> >
> >> >> > Staged Maven repository:
> >> >> >
> >> https://repository.apache.org/content/repositories/orgapachefluo-1017/
> >> >> >
> >> >> > Signing KEYS:
> >> >> > https://www.apache.org/dist/incubator/fluo/KEYS
> >> >> > (fingerprint for this release:
> >> CF72CA07C8BC86A1C862765F9AACFB56352ACF76)
> >> >> >
> >> >> > Git repo:
> >> >> > https://gitbox.apache.org/repos/asf/incubator-fluo
> >> >> > (branch: 1.1.0-incubating-rc1,
> >> >> > commit: ad8ee492e2f435405f98d825781098c55186f4fb)
> >> >> >
> >> >> > This vote will end on Fri Jun  9 20:30:00 UTC 2017
> >> >> > (Fri Jun  9 16:30:00 EDT 2017 / Fri Jun  9 13:30:00 PDT 2017)
> >> >> >
> >> >> >
> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> >> > For additional commands, e-mail: general-help@incubator.apache.org
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> >> For additional commands, e-mail: general-help@incubator.apache.org
> >> >>
> >> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
>

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