On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote: > > I'm a bit confused by the LICENSE and NOTICE files that are in the root of > the package. > > They seem to be LICENSE/NOTICE files that would be good for a binary > distribution of Cloudstack built from this package, but don't really apply to > this package. Or maybe they were from before the dep jars were changed to be > grabbed via maven and were part of the src. Right? > > The license file lists license for jars in lib and aws and such that don't > exist. Likewise for the NOTICE file. > > Don't get me wrong. I think these LICENSE/NOTICE files are great to have for > people that are building binary distributions of Cloudstack and having that > information available to them certainly takes much of the burden off of them, > but I do question if they are appropriate for the Apache source based > releases. > > > Dan
Dan, Yes, the jars referenced in the legal docs are pulled in by the packaging process. The expectation was that the material would be brought into any packaging (including the non-asf, but community provided, deb/rpm's). When looking for examples from other ASF projects, IIRC I saw both approaches (I'll have to dig a bit to find the examples that I was looking at). At one point, I had a "*_BINARY" version of both files and the standard files for the source itself, but I then decided to simplify into a single set that would work for both situations. So I guess the question is this: is this an acceptable approach or not? -chip > On Oct 22, 2012, at 12:16 PM, Chip Childers (ASF) <chipchild...@apache.org> > wrote: > >> Hi All, >> >> I would like to call a vote for Apache CloudStack (Incubating) Release >> 4.0.0-incubating (third round). >> >> We encourage the whole community to download and test these release >> artifacts, so that any critical issues can be resolved before the >> release is made. The more time that each individual spends reviewing >> the artifacts, the higher confidence we can have in both the release >> itself and our ability to pass an IPMC vote later on. Everyone is free >> to vote on this release, so please give it a shot. >> >> Instructions for Validating and Testing the artifacts can be found here: >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure >> >> If you have any trouble setting up a test environment using the >> procedure above, please ask on the cloudstack-dev@i.a.o list. Someone >> will be sure to help, and we'll improve our test procedure >> documentation at the same time! >> >> Now, on to the specifics of what we are voting on... >> >> >> The following artifacts are up for the vote: >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/ >> >> PGP release keys (signed using A99A5D58): >> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS >> >> Branch: 4.0 >> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480 >> >> >> List of changes: >> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0 >> >> The artifacts being voted on during this round also include the >> following additional fixes (most were identified as part of testing >> during the last round of voting): >> >> * Many documentation fixes (particularly the release notes and >> installation guide) >> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI >> * CLOUDSTACK-349: Russian l10n not properly displaying >> * Correction to the devcloud rdeploy build target, to make testing easier >> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail >> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance" >> * DISCLAIMER added to the Marvin tool dir >> >> >> The vote will be open for 72 hours. >> >> >> For sanity in tallying the vote, can PPMC and IPMC members please be >> sure to indicate "(binding)" with their vote? >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> Thanks! > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > >
