Hi Deron, Here's an example from a release I did recently for a TLP to give you some guidance. https://dist.apache.org/repos/dist/release/deltaspike/1.7.2/ (and i'm sure others may find some errors in what I did - no one's perfect)
In this release, for each file there are 3 accompanying files - the .asc, .sha1. and the .md5. Your release is missing sha1's, but i'm not sure that's too important. The overall release contents are made up of: - Source ZIP file - POM file for the root of the project - The convenience binary zip - The convenience binary .tar.gz I actually have a note to not copy the tests JAR in the future. I think the problem area is that its not clear looking at the file names what is what in your release. If your release only included a single source zip, two convenience binaries (tar.gz and zip) as well as the relevant asc and md5 files, they were all named properly, that would be perfect. John On Tue, Nov 8, 2016 at 3:00 PM Deron Eriksson <deroneriks...@gmail.com> wrote: > Hello, > > Thank you for your patience. For release candidate validation, would it be > acceptable and helpful to reduce the dist artifacts to the following with > their accompanying signature files? It would be nice if we could include > the binary distribution with dependencies. This would reduce the dist > artifacts from 9 to 4. > > Source distribution: > systemml-0.11.0-incubating-src.tar.gz > systemml-0.11.0-incubating-src.zip > > Binary distribution with dependencies: > systemml-0.11.0-incubating-standalone.tar.gz > systemml-0.11.0-incubating-standalone.zip > > > https://dist.apache.org/repos/dist/dev/incubator/systemml/0.11.0-incubating-rc5/ > > Thank you, > Deron > > > On Sun, Nov 6, 2016 at 9:06 PM, Luciano Resende <luckbr1...@gmail.com> > wrote: > > > On Sun, Nov 6, 2016 at 7:36 PM, Justin Mclean <jus...@classsoftware.com> > > wrote: > > > > > Hi, > > > > > > > I understand that the most important thing for Apache is the source > > > release > > > > artifact, but that does not prohibit a project from distributing > > > > convenience binaries as long as they meet all the legal requirements > > > > mandated by Apache. > > > > > > Which is fine but currently it is not clear (to an external person) > > > exactly what is what in that directory and the VOTE email doesn’t > clarify > > > it. > > > > > > > Yes, it's a bit confusing, so maybe it's a matter of adding a README to > > clarify what are the artifacts being released. > > > > > > > > > > > Also, the release structure hasn't changed much from > > > > our previous release > > > > > > Which I asked about the last RC and got no reply. I took a guess but > > still > > > not sure if it was right or not and if everything got reviewed. > > > > > > > > Sorry for not getting back to you on the list of artifacts, I have > > documented them on the following thread on the SystemML mailing list: > > https://www.mail-archive.com/dev@systemml.incubator.apache. > > org/msg01121.html > > > > Also, from previous RC the community removed one jar from the release > > (*-standalone.jar) and all other artifacts were reviewed by the SystemML > > podling members. We are also looking into reducing the number of > > distributed artifacts for our next release which should avoid further > > confusion on the matter. > > > > > > > Thanks, > > > Justin > > > > > > > > > > -- > > Luciano Resende > > http://twitter.com/lresende1975 > > http://lresende.blogspot.com/ > > >
