Hello Andy, 2015-05-11 23:43 GMT+02:00 Andy Seaborne <[email protected]>:
> On 11/05/15 19:12, John D. Ament wrote: > >> Since they're incubating, Commons RDF would upload to incubator/dist >> instead, but generally yes all the same would apply. >> >> On Mon, May 11, 2015 at 2:08 PM Benedikt Ritter <[email protected]> >> wrote: >> >> 2015-05-08 14:45 GMT+02:00 Stian Soiland-Reyes <[email protected]>: >>> >>> On 7 May 2015 at 21:29, Andy Seaborne <[email protected]> wrote: >>>> >>>>> Suggestion: >>>>> Only produce the zip version so there is exactly one "source release" >>>>> >>>> file >>>> >>>>> and so only one to check. >>>>> >>>> >>>> I think it's good to have both for longevity, and for the benefit of >>>> OS distributions and automated builds, zip is after all a confusingly >>>> defined format, and it is just a diff -ur to check their content is >>>> the same. >>>> >>>> It's not like we will have a very large download page :) >>>> >>>> (btw - could someone draft that? How is that done in Commons way? I >>>> remember something to watch out for is chmod +x on the cgi-bin..) >>>> >>>> >>> Sorry, I had to take care of that Commons CLI release the Groovy project >>> requested. I'm trying to follow up this discussion now... >>> >>> Commons projects usually produce: >>> - tar.gz and zip archives of the sources and binaries (uploaded to >>> >> > What's the difference with the "source-release" that the Apache parent > org.apache.apache enabled with, enabled with -Papache-release? > TBH I don't know why commons has it's own release profile. I've never worked for an other project so I didn't know about -Papache-release from apache-parent until now. > > <!-- Create a source-release artifact that contains the fully buildable > project directory source structure. This is the artifact which is > the official subject of any release vote. > --> > > and the "src" files made in commons-parent? > > Do commons components not use -Papache-release? > No we use -Prelease as described in [1]. Benedikt [1] http://commons.apache.org/releases/prepare.html > > Andy > > https://dist.apache.org/repos/dist/release/commons/) >>> - maven artifacts for maven central (before closing into the staging >>> repo, >>> we remove the tar.gz and zips from the staging repo so that only jars and >>> poms are pushed to maven central) >>> >>> I think Commons RDF should do the same. What was the reason for dropping >>> the tar.gz src build? Has there been a problem with Commons parent? >>> >> > 3 source bundles to check. > > > >>> br, >>> Benedikt >>> >>> >>> >>>> >>>> What I wondered is why the proposed source distributions in >>>> dist.apache.org are not simply byte-wise equal to the -src in >>>> >>>> >>>> >>> https://repository.apache.org/content/repositories/orgapachecommons-1095/org/apache/commons/commons-rdf-parent/0.1.0-incubating/ >>> >>>> ? >>>> >>>> (and why does that folder contain bout -src and -source-release.zip?) >>>> >>>> (Don't worry, the files inside it are byte-equal to the ones in the >>>> proposed release archives - except that -source.zip also contains the >>>> harmless examples/ folder) >>>> >>>> >>>> >>>> -- >>>> Stian Soiland-Reyes >>>> Apache Taverna (incubating), Apache Commons RDF (incubating) >>>> http://orcid.org/0000-0001-9842-9718 >>>> >>>> >>> >>> >>> -- >>> http://people.apache.org/~britter/ >>> http://www.systemoutprintln.de/ >>> http://twitter.com/BenediktRitter >>> http://github.com/britter >>> >>> >> > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
