Hi Gav, We have a few questions for you regarding svnpubsub. Could you please take a look?
THanks, Craig Begin forwarded message: > From: Craig L Russell <craig.russ...@oracle.com> > Date: February 28, 2014 11:50:39 AM PST > To: "ga...@16degrees.com.au McDonald" <ga...@16degrees.com.au> > Cc: Apache DB PMC <priv...@db.apache.org> > Subject: Re: [DISCUSS] Use svnpubsub for release > Reply-To: priv...@db.apache.org > > Hi Gav, > > On Feb 28, 2014, at 10:26 AM, Rick Hillegas wrote: > >> On 2/28/14 9:30 AM, Craig L Russell wrote: >>> Hi, >>> >>> Please take a look at http://www.apache.org/dev/release#upload-ci and >>> https://issues.apache.org/jira/browse/INFRA-7320 >>> >>> The modern way to put release artifacts into the mirrors is to use >>> svnpubsub which is set up by infra. This technique obsoletes the >>> error-prone scp process where the release manager directly copies artifacts >>> to the apache dist directory. >>> >>> The jdo project is currently trying to release jdo-3.1-rc1 and we would >>> like to use svnpubsub. But infra says that the directory structure makes it >>> awkward (impossible?) to set up just jdo for svnpubsub. >>> >>> Infra has asked that all db projects use svnpubsub as well. I guess that >>> this primarily affects Derby. >>> >>> WDYT? >>> >>> Craig >>> >>> >>> Craig L Russell >>> Architect, Oracle >>> http://db.apache.org/jdo >>> 408 276-5638 mailto:craig.russ...@oracle.com >>> P.S. A good JDO? O, Gasp! >>> >>> >> Hi Craig, >> >> At first blush this looks like a simpler way to publish releases. I'm >> unclear about some points, however: >> >> 1) Since this is a technique for configuring mirroring, I assume that this >> means that only the current, mirrored releases will be checked into the new >> location. Right? > > This is a good question. Releases already published should remain there. >> >> 2) Does this mean that Derby will need to move its two current, mirrored >> releases (10.10.1.1 and 10.8.3.0), or will Infra move these releases for us? > > Gavin, I guess this question needs a reply from you. What will happen to the > releases (not just Derby and JDO) that are currently in the apache/dist/db > directory. Ideally there would be no need for the projects to do anything. >> >> 3) Will we need to make changes to our download pages to reflect this move? >> Or will Infra make any necessary changes? > > If I understand correctly, download pages are directed to mirror sites. The > change in process should not affect already-distributed artifacts. >> >> 4) I assume this doesn't affect archiving. The location of archived releases >> won't change if we change the mirroring location? > > That's my understanding. >> >> 5) How do we turn off mirroring for old releases? Do we just svn delete the >> release directory? > > That's my understanding. >> >> 6) I notice that JDO is using this mechanism to publish a release candidate. >> I assume that's a subproject-specific preference and we don't need to change >> that part of our process (but are free to follow suit if that makes sense to >> us). Right? > > It's just a name. It's an official Apache release duly voted by the PMC. It > just has a name that doesn't sound complete. But it's as real as any Apache > release. > > Thanks, > > Craig > >> >> Thanks, >> -Rick > > Craig L Russell > Architect, Oracle > http://db.apache.org/jdo > 408 276-5638 mailto:craig.russ...@oracle.com > P.S. A good JDO? O, Gasp! > Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
