You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "Aaron Mihalik (JIRA)" <ji...@apache.org> on 2016/09/16 00:39:20 UTC

[jira] [Created] (RYA-186) Create dist.a.o/repos/dist/dev/incubator/rya and add KEYS

Aaron Mihalik created RYA-186:
---------------------------------

             Summary: Create dist.a.o/repos/dist/dev/incubator/rya  and add KEYS
                 Key: RYA-186
                 URL: https://issues.apache.org/jira/browse/RYA-186
             Project: Rya
          Issue Type: Bug
            Reporter: Aaron Mihalik
            Priority: Blocker


During the review of the 3.2.10-RC1 Release, Josh Noted:

* https://dist.apache.org/repos/dist/release/incubator/rya and
https://dist.apache.org/repos/dist/dev/incubator/rya don't exist. You
must have the former created with a KEYS file that contains the GPG
public keys for those creating Rya release notes. Typically, you should
use dist.a.o/repos/dist/dev/incubator/rya to stage your release
artifacts, although policy on whether using the staging repo alone is
sufficient is not clear to me. (were it not for the licensing issues
below, we could just fix this)


Adina also noted this:

* Release artifacts should be staged at
https://dist.apache.org/repos/dist/dev/incubator/rya/...  (Josh said so
already)
* KEYS file with the release manager's keys and maybe other committers'
too can typically be found at
https://dist.apache.org/repos/dist/dev/incubator/rya/KEYS





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)