Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Received-SPF: pass (athena.apache.org: domain of craig.russell@oracle.com
 designates 141.146.126.69 as permitted sender)
Subject: [VOTE][RESULT] Use svnpubsub for publishing DB project release
 artifacts
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-17--347233482
From: Craig L Russell <craig.russell@oracle.com>
In-Reply-To: <533F1337.1050805@nc.rr.com>
Date: Sat, 5 Apr 2014 10:34:37 -0700
Cc: "jdo-dev@db.apache.org project" <jdo-dev@db.apache.org>,
        Derby Discussion <derby-user@db.apache.org>
Message-Id: <CC4A8CAB-3A59-49AF-BA01-F1F712905410@oracle.com>
References: <A61CD865-8059-4529-9EF4-E8525D602B86@oracle.com>
 <5336DBE5.9080303@apache.org> <533F1337.1050805@nc.rr.com>
To: private@db.apache.org

--Apple-Mail-17--347233482
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

After 10 days, eight in favor, and no votes against, this vote passes.
+1 votes were received from Craig, Greg, Michael, Thomas, Rick, Myrna, =
Camilla, and Dag.
Next steps:
The current Derby and Torque releases need to be copied to new svn =
directories under https://dist.apache.org/repos/dist/release/db/
This can be done by anyone in the DB PMC. Infra will then establish the =
sync to the official Apache release directory.=20
Thanks, everyone.
Craig
On 24.03.14 18:11, Craig L Russell wrote:
Hi PMC,

Recently the JDO project set up to use svnpubsub to publish our =
releases. We have opened this JIRA to track the request: =
https://issues.apache.org/jira/browse/INFRA-7320 But because JDO is a =
sub-project of db, infra would like to have "all or nothing" for =
svnpubsub.=20

This technique is easier and less error-prone than the alternative =
(manually copying release artifacts to dist/db via scp). The technique =
is described here: http://www.apache.org/dev/release#upload-ci=20

The impact on Derby is that as part of the migration, a Derby release =
manager (actually anyone with commit privs to derby) will have to copy =
the release artifacts to the source svnpubsub repository: =
https://dist.apache.org/repos/dist/release/db/derby

Once this is done, infra will synchronize the release/db directory with =
Apache's official release directory which is automatically mirrored =
worldwide. The downloads page that chooses a mirror will continue to =
work exactly as before. There are no other changes to release artifact =
naming.

To stop mirroring a Derby release, the appropriate directory under =
https://dist.apache.org/repos/dist/release/db/derby simply needs to be =
svn rm'd. The change will automatically propagate to mirrors.

Please vote to adopt this new release process.

Here's my +1

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


--Apple-Mail-17--347233482--