Whoops, will do going forward. Thanks! A.
On Fri, May 31, 2013 at 8:58 AM, Mohammad Nour El-Din < [email protected]> wrote: > Hi > > If this is the jclouds development community [VOTE] so please don't CC > general@ in all your replies. For future release developers [VOTE] please > send a separate e-mail cause this causes some noise on general > > Thanks and good job for bringing a release in that short time, hope it > passes the [VOTE] ;) > > > > On Fri, May 31, 2013 at 5:24 PM, Andrew Bayer <[email protected] > >wrote: > > > One note - looking at the docs and other projects, it seems we should in > > fact be using the standard Apache NOTICE, not our previous one with the > > additional qualifiers, so I'll switch that. I still need to address the > > tarball names, the duplicate license in cli, the missing license and > notice > > in labs, and anything else that comes up. I'll cut another RC this > > afternoon PDT, once I've addressed those problems and waited to see what > > additional issues are uncovered. > > > > A. > > > > > > > > On May 31, 2013, at 8:03 AM, Andrew Bayer <[email protected]> > wrote: > > > > > Looks like jclouds-cli has a LICENSE.txt in its root dir in git as well > > as the one the remote resources plugin inserts. I'll clean that up. I'll > > dig into labs and see why it's not getting the license and notice it > should. > > > > > > A. > > > > > > > > > > > > On May 31, 2013, at 7:47 AM, "Chen, Pei" < > [email protected]> > > wrote: > > > > > >> Just an observation: > > >> jclouds-cli-pom-1.6.1-incubating-source-release.tar.gz root has 2 > > LICENSE files? > > >> LICENSE and LICENSE.txt > > >> jclouds-labs-1.6.1-incubating-source-release.tar.gz root is missing > > LICENSE/NOTICE ? > > >> > > >>> -----Original Message----- > > >>> From: Andrew Bayer [mailto:[email protected]] > > >>> Sent: Thursday, May 30, 2013 11:19 PM > > >>> To: [email protected] > > >>> Cc: [email protected]; [email protected] > > >>> Subject: Re: [VOTE] Release Apache jclouds 1.6.1-incubating > > >>> > > >>> NOTICE is being generated (I believe in all cases) from incubator- > > >>> jclouds.git/resources/NOTICE.txt - I think the resources/NOTICE.txt > in > > chef > > >>> may be from an earlier incarnation, but I'm not 100% sure. It does > > look like > > >>> we are overly broad in the list of included code in NOTICE, but I'm > > not sure > > >>> whether we should have separate NOTICEs for each sub project or if we > > can > > >>> just use one that's applicable across all of them. This is my first > > ASF project > > >>> with separate release artifacts for source projects. > > >>> > > >>> I'll fix the tarball names by hand for this RC tomorrow morning, and > > we'll > > >>> figure out the best way to get them automatically named correctly > going > > >>> forward, including any subsequent RCs if they prove necessary for > code > > >>> reasons, etc. > > >>> > > >>> We've been uncertain about how to handle test resources - there are a > > good > > >>> number of test resources which are just used for validating test > > output, and > > >>> we'd have to have the tests spit out the license headers as well as > > their real > > >>> output if we had license headers in the output comparison resources. > > As a > > >>> result, we've excluded src/test/resources from rat checks in the > > build. This > > >>> may have been too broad an exclusion, but we'd like to make sure we > > know > > >>> what can get away with not having a license header and what can't > > before > > >>> we change that. > > >>> > > >>> A. > > >>> > > >>> On May 30, 2013, at 7:41 PM, David Nalley <[email protected]> wrote: > > >>> > > >>>> On Thu, May 30, 2013 at 3:44 PM, Andrew Bayer <[email protected]> > > >>> wrote: > > >>>>> Hello, > > >>>>> > > >>>>> This is the first release candidate for Apache jclouds > > >>>>> 1.6.1-incubating, the first jclouds release at Apache. > > >>>>> > > >>>>> We are calling this vote on both the IPMC and the jclouds PPMC at > the > > >>>>> same time, as the code for this release has already been vetted by > > >>>>> the jclouds developers leading up to this RC. > > >>>>> > > >>>>> It fixes the following issues: > > >>>>> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=123244 > > >>>>> 12&styleName=Html&projectId=12314430 > > >>>>> > > >>>>> *** Please download, test and vote by Sunday, June 2nd, 1pm PDT. > > >>>>> > > >>>>> Note that we are voting upon the source (tag), binaries are > provided > > >>>>> for convenience. > > >>>>> > > >>>>> Source and binary files: > > >>>>> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-rc1 > > >>>>> > > >>>>> Maven staging repo: > > >>>>> > > https://repository.apache.org/content/repositories/orgapachejclouds-0 > > >>>>> 39 > > >>>>> > > >>>>> The tags to be voted upon: > > >>>>> - jclouds - > > >>>>> > > https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag > > >>>>> ;h=57718280be4bccea9e7885c5c3c38550f818d0dd > > >>>>> - jclouds-labs - > > >>>>> > https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git > > ; > > >>>>> a=tag;h=df11ed5cc10e86b6ee33be2c85f25717ca59b6f4 > > >>>>> - jclouds-chef - > > >>>>> > https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git > > ; > > >>>>> a=tag;h=989d9a484ac3f4fa919307173b7a8839817bb797 > > >>>>> - jclouds-karaf - > > >>>>> > > https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git > > >>>>> ;a=tag;h=964f2694b5198c7916869308c2c644a2f71927ff > > >>>>> - jclouds-cli - > > >>>>> > > https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a > > >>>>> =tag;h=8f0491d33ca07eab01d90e9a4571d6d046865638 > > >>>>> > > >>>>> Whirr's KEYS file containing PGP keys we use to sign the release: > > >>>>> http://www.apache.org/dist/incubator/jclouds/KEYS > > >>>>> > > >>>>> [ ] +1 > > >>>>> [ ] 0 > > >>>>> [ ] -1 (explain why) > > >>>>> > > >>>>> Please note whether you're voting as an IPMC member, a jclouds PPMC > > >>>>> member, or both. Thanks! > > >>>>> > > >>>>> A. > > >>>> > > >>>> Hi Andrew: > > >>>> > > >>>> I've started looking at the chef bits (haven't gotten past that, > yet) > > >>>> but NOTICE looks eerily familiar. Can you tell me how NOTICE was > > >>>> generated? Jersey, for instance, is listed as being included, but I > > >>>> can't find it bundled into source of chef source tarball anywhere. > > >>>> Have you seen: http://www.apache.org/dev/licensing-howto.html > > >>>> > > >>>> There's also an issue with naming - chef-project does not match > naming > > >>>> specified at: > > >>>> http://incubator.apache.org/guides/releasemanagement.html#naming > > >>>> > > >>>> What are the LICENSE.txt and NOTICE.txt files under resources/ > > intended > > >>> for? > > >>>> > > >>>> The json files in core/src/test/resources/ don't seem to have > license > > >>>> headers - or at least not all of them do - one or two of them do > > >>>> contain a license header. > > >>>> > > >>>> --David > > >>>> > > >>>> > --------------------------------------------------------------------- > > >>>> To unsubscribe, e-mail: [email protected] > > >>>> For additional commands, e-mail: [email protected] > > >>>> > > >>> > > >>> --------------------------------------------------------------------- > > >>> To unsubscribe, e-mail: [email protected] > > >>> For additional commands, e-mail: [email protected] > > >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > -- > Thanks > - Mohammad Nour > ---- > "Life is like riding a bicycle. To keep your balance you must keep moving" > - Albert Einstein >
