[RESULT] Re: [VOTE] Apache Felix 0.8.0 Incubator Release
This vote has been open for more than 72 hours, so we would like to call the vote on Felix-0.8.0-incubator so that we can move forward: * +1 votes from Robert Burrell Donkin, Upayavira, Enrique Rodriguez, Alex Karasulu * No 0 votes. * No -1 votes. With three +1 from IPMC members the vote is successful. We will make an official announcement and make the release available publicly. Thanks to the people who reviewed and/or voted. regards, Karl -- Karl Pauls [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: [VOTE] Apache Felix 0.8.0 Incubator Release
The asc and KEYS files are available on the page now. Please start reviewing our release again. The URL stays the same: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html +1 -- minor (fix in HEAD) -- a number of package.html's are IMHO creative enough to be copyrightable. i think that they should have copyright headers. Well, the point is that this package.html's are from the OSGi alliance (licensed under ASL). We redistribute them but try not to modify them. We've been discussing adding a copyright but decided against it on the grounds of them being provided like this. - notes and comments (not requirements) - the public key does not seems to be available from the major keysigning networks (see http://www.apache.org/dev/release-signing.html if you haven't uploaded it yet) I'm going to upload the key. Thanks. good practice to produce both tar.gz and zip compressed artifacts. yes, i know that most major platforms can easily open either format but users associated tar.gz with *nix and zip with m$. producing both formats is good psychology. Right, we will look into it. release notes are an important form of guerilla advertising. the same content can be used in several different places: on the download page, on announcements, on grassroots media (eg freshmeat) and as plain text in the release. consider adding some next time. - robert We will. Due to this being our first release it wouldn't contain much this time around anyhow, but I agree, release notes are important. Thanks for pointing it out and for reviewing. regards, Karl -- Karl Pauls [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache Felix 0.8.0 Incubator Release
Karl Pauls wrote: The asc and KEYS files are available on the page now. Please start reviewing our release again. The URL stays the same: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html regards, Karl On 12/12/06, Karl Pauls [EMAIL PROTECTED] wrote: Not quite there yet. The incubator DISCLAIMER file is still missing from the jars. That would prevent them going into maven repositories. Is that just a recommendation or a requirement? Our NOTICE files contain the incubator disclaimer text. it's a requirement that the text is present but AIUI in the NOTICE is ok (though perhaps a separate DISCLAIMER is clear) We have a separate DISCLAIMER on top-level. The binaries (i.e., jar files) contain a NOTICE that includes the DISCLAIMER. I agree that a separate DISCLAIMER is more clear but I think for this release we'll go with the current set-up. please let me know whether you plan to cut another candidate or whether i should review the one above Yes, please review the one above. signing the releases is a requirement. having a well connected code signing key is definitely good but not mandatory - robert We will make the asc and KEYS files available on the page mentioned above asap (i.e., a couple of hours). Okay. I have looked around the release, and to the best of my (at this point) limited knowledge, everything looks in order. I have verified that the MD5 and PGP signature are correct. Therefore I am prepared to vote +1. Regards, Upayavira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: [VOTE] Apache Felix 0.8.0 Incubator Release
On 12/12/06, Karl Pauls [EMAIL PROTECTED] wrote: The asc and KEYS files are available on the page now. Please start reviewing our release again. The URL stays the same: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html Robert's notes and comments are duly noted by the Felix community. Thanks for reviewing. I'm +1 (non-binding). Enrique - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: [VOTE] Apache Felix 0.8.0 Incubator Release
Not quite there yet. The incubator DISCLAIMER file is still missing from the jars. That would prevent them going into maven repositories. Is that just a recommendation or a requirement? Our NOTICE files contain the incubator disclaimer text. it's a requirement that the text is present but AIUI in the NOTICE is ok (though perhaps a separate DISCLAIMER is clear) We have a separate DISCLAIMER on top-level. The binaries (i.e., jar files) contain a NOTICE that includes the DISCLAIMER. I agree that a separate DISCLAIMER is more clear but I think for this release we'll go with the current set-up. please let me know whether you plan to cut another candidate or whether i should review the one above Yes, please review the one above. signing the releases is a requirement. having a well connected code signing key is definitely good but not mandatory - robert We will make the asc and KEYS files available on the page mentioned above asap (i.e., a couple of hours). regards, Karl -- Karl Pauls [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: [VOTE] Apache Felix 0.8.0 Incubator Release
The asc and KEYS files are available on the page now. Please start reviewing our release again. The URL stays the same: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html regards, Karl On 12/12/06, Karl Pauls [EMAIL PROTECTED] wrote: Not quite there yet. The incubator DISCLAIMER file is still missing from the jars. That would prevent them going into maven repositories. Is that just a recommendation or a requirement? Our NOTICE files contain the incubator disclaimer text. it's a requirement that the text is present but AIUI in the NOTICE is ok (though perhaps a separate DISCLAIMER is clear) We have a separate DISCLAIMER on top-level. The binaries (i.e., jar files) contain a NOTICE that includes the DISCLAIMER. I agree that a separate DISCLAIMER is more clear but I think for this release we'll go with the current set-up. please let me know whether you plan to cut another candidate or whether i should review the one above Yes, please review the one above. signing the releases is a requirement. having a well connected code signing key is definitely good but not mandatory - robert We will make the asc and KEYS files available on the page mentioned above asap (i.e., a couple of hours). regards, Karl -- Karl Pauls [EMAIL PROTECTED] -- Karl Pauls [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: [VOTE] Apache Felix 0.8.0 Incubator Release
On 12/12/06, Karl Pauls [EMAIL PROTECTED] wrote: The asc and KEYS files are available on the page now. Please start reviewing our release again. The URL stays the same: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html +1 -- minor (fix in HEAD) -- a number of package.html's are IMHO creative enough to be copyrightable. i think that they should have copyright headers. - notes and comments (not requirements) - the public key does not seems to be available from the major keysigning networks (see http://www.apache.org/dev/release-signing.html if you haven't uploaded it yet) good practice to produce both tar.gz and zip compressed artifacts. yes, i know that most major platforms can easily open either format but users associated tar.gz with *nix and zip with m$. producing both formats is good psychology. MANIFEST.MF lacks some of the attributes recommended by Sun (Extension-Name,Specification-Title, Specification-Vendor, Specification-Version, Implementation-Vendor-Id, Implementation-Title, Implementation-Vendor, Implementation-Version) release notes are an important form of guerilla advertising. the same content can be used in several different places: on the download page, on announcements, on grassroots media (eg freshmeat) and as plain text in the release. consider adding some next time. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache Felix 0.8.0 Incubator Release
On Monday 11 December 2006 11:16, Craig L Russell wrote: My understanding is that a legal issue is sufficient to veto a release. So if an issue is raised, e.g. missing NOTICE or wrong copyright in the LICENSE, that should be a veto. But I agree that the fact that there is a legal issue raised is sufficient for the proposer to withdraw the proposal and try again. On the other hand, objecting to the contents of a release (missing feature, badly implemented feature) can result in a -1 without a veto. Sounds very reasonable to me. However, if there is a disagreement of what constitutes a legal flaw, then there is something much more serious going on in the community. I.e. if person A doesn't manage to stop pmc B from a release, then A should probably consult the legal-discuss@ and/or [EMAIL PROTECTED] After all, it *could* be that B doesn't understand the legal requirements, but worse if it is done on purpose to hurt the ASF... Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache Felix 0.8.0 Incubator Release
On Dec 10, 2006, at 7:57 PM, Jason van Zyl wrote: On 10 Dec 06, at 6:40 PM 10 Dec 06, Roy T. Fielding wrote: On Dec 10, 2006, at 5:47 AM, Karl Pauls wrote: We ask that you please vote to approve this release: [ ] +1 Approve the Felix 0.8.0-incubator release. [ ] -1 Veto the release (please provide specific comments) BTW, this Veto thing is wrong. I've been meaning to mention it since several podlings have used this template. It is not possible to veto a release -- all releases are majority votes. +1 just means yes and -1 means no. Really? I thought that would be considered a technical thing? If you know a release is getting pushed out when it shouldn't because it's premature that on technical grounds you could say that it doesn't meet the requirements of a beta say? Or that it has know flaws and shouldn't be released? I honestly thought it was a technical type decision. As long as 3 people within the PMC attest to its validity, the release can go out. AFAIK, only a legal veto can block a release. In most cases, of course, the community listens and responds to any -1 votes and tries to address them, if need be. Ignoring -1's is bad form. But with releases, -1 aren't vetoes. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache Felix 0.8.0 Incubator Release
As a follow up, we resolved every issue raised by Daniel except the signing portion. A new snapshot of the release is available at: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html I was able to fix one minor bug in our maven bundle plugin that was causing LICENSE/NOTICE files to not get copied. Hopefully the majority vote can continue... - richard Daniel Kulp wrote: I'm not going to vote (would be non-binding anyway), but some issues I see: 1) The felix.jar itself does not have the DISCLAIMER in it. I think that's fine as long as you don't plan on putting it in any maven repository. That said, being a maven user, I'd like to see it fixed so it COULD be deployed there. 2) The LICENSE and NOTICE files in the felix jar are right in the root of the jar. I think we've been recommending they go into the META-INF dir. 3) None of the three jars in bundle directory have the license,notice, or disclaimer files. 4) I don't see and asc files on the web page. The release needs to be signed and KEYS made available. Dan On Sunday 10 December 2006 08:47, Karl Pauls wrote: The Felix PPMC has voted on an incubator release and we would like to call an Incubator PMC vote to get final approval. We hope that this release represents the final step for Felix' graduation, but wish to pursue this official incubator release since we do not know how long graduation will take and feel it is important to make a public release available. We hope to request graduation once this incubator release is approved. The candidate incubator release can be found here: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html We ask that you please vote to approve this release: [ ] +1 Approve the Felix 0.8.0-incubator release. [ ] -1 Veto the release (please provide specific comments) Thanks in advance for your effort in examining the release. - The Felix Team - 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]
Re: [VOTE] Apache Felix 0.8.0 Incubator Release
On Monday 11 December 2006 10:57, Richard S. Hall wrote: As a follow up, we resolved every issue raised by Daniel except the signing portion. A new snapshot of the release is available at: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html I was able to fix one minor bug in our maven bundle plugin that was causing LICENSE/NOTICE files to not get copied. Not quite there yet. The incubator DISCLAIMER file is still missing from the jars. That would prevent them going into maven repositories. For the signing part, you really need gnupg installed.Create a key if you don't already have one. (I think it's gpg --gen-key, but it's been a while since I looked into that part) Then you just need to run gpg -a -s filename.tar.gz to produce the asc files. You would also need to do: gpg --list-keys username KEYS gpg -a --export username KEYS and get that KEYS file added into the root of your SVN repository. Ideally, you would also upload it to one of the public keyservers as well. Longer term, you should also attend an apache keysigning party or similar to get your keys signed by enough apache people so that apache people can trust that those keys really are yours. Dan Hopefully the majority vote can continue... - richard Daniel Kulp wrote: I'm not going to vote (would be non-binding anyway), but some issues I see: 1) The felix.jar itself does not have the DISCLAIMER in it. I think that's fine as long as you don't plan on putting it in any maven repository. That said, being a maven user, I'd like to see it fixed so it COULD be deployed there. 2) The LICENSE and NOTICE files in the felix jar are right in the root of the jar. I think we've been recommending they go into the META-INF dir. 3) None of the three jars in bundle directory have the license,notice, or disclaimer files. 4) I don't see and asc files on the web page. The release needs to be signed and KEYS made available. Dan On Sunday 10 December 2006 08:47, Karl Pauls wrote: The Felix PPMC has voted on an incubator release and we would like to call an Incubator PMC vote to get final approval. We hope that this release represents the final step for Felix' graduation, but wish to pursue this official incubator release since we do not know how long graduation will take and feel it is important to make a public release available. We hope to request graduation once this incubator release is approved. The candidate incubator release can be found here: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html We ask that you please vote to approve this release: [ ] +1 Approve the Felix 0.8.0-incubator release. [ ] -1 Veto the release (please provide specific comments) Thanks in advance for your effort in examining the release. - The Felix Team - 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] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache Felix 0.8.0 Incubator Release
Daniel Kulp wrote: On Monday 11 December 2006 10:57, Richard S. Hall wrote: As a follow up, we resolved every issue raised by Daniel except the signing portion. A new snapshot of the release is available at: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html I was able to fix one minor bug in our maven bundle plugin that was causing LICENSE/NOTICE files to not get copied. Not quite there yet. The incubator DISCLAIMER file is still missing from the jars. That would prevent them going into maven repositories. Is that just a recommendation or a requirement? Our NOTICE files contain the incubator disclaimer text. For the signing part, you really need gnupg installed.Create a key if you don't already have one. (I think it's gpg --gen-key, but it's been a while since I looked into that part) Then you just need to run gpg -a -s filename.tar.gz to produce the asc files. You would also need to do: gpg --list-keys username KEYS gpg -a --export username KEYS and get that KEYS file added into the root of your SVN repository. Ideally, you would also upload it to one of the public keyservers as well. Longer term, you should also attend an apache keysigning party or similar to get your keys signed by enough apache people so that apache people can trust that those keys really are yours. Thanks for this info. We will work on it. - richard Dan Hopefully the majority vote can continue... - richard Daniel Kulp wrote: I'm not going to vote (would be non-binding anyway), but some issues I see: 1) The felix.jar itself does not have the DISCLAIMER in it. I think that's fine as long as you don't plan on putting it in any maven repository. That said, being a maven user, I'd like to see it fixed so it COULD be deployed there. 2) The LICENSE and NOTICE files in the felix jar are right in the root of the jar. I think we've been recommending they go into the META-INF dir. 3) None of the three jars in bundle directory have the license,notice, or disclaimer files. 4) I don't see and asc files on the web page. The release needs to be signed and KEYS made available. Dan On Sunday 10 December 2006 08:47, Karl Pauls wrote: The Felix PPMC has voted on an incubator release and we would like to call an Incubator PMC vote to get final approval. We hope that this release represents the final step for Felix' graduation, but wish to pursue this official incubator release since we do not know how long graduation will take and feel it is important to make a public release available. We hope to request graduation once this incubator release is approved. The candidate incubator release can be found here: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html We ask that you please vote to approve this release: [ ] +1 Approve the Felix 0.8.0-incubator release. [ ] -1 Veto the release (please provide specific comments) Thanks in advance for your effort in examining the release. - The Felix Team - 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]
Re: [VOTE] Apache Felix 0.8.0 Incubator Release
Jim Jagielski wrote: As long as 3 people within the PMC attest to its validity, the release can go out. AFAIK, only a legal veto can block a release. In most cases, of course, the community listens and responds to any -1 votes and tries to address them, if need be. Ignoring -1's is bad form. But with releases, -1 aren't vetoes. But if vetoed *code* is in a release candidate, it cannot proceed. You can't veto this release isn't ready or it's not feature complete, but you can point out commit r484848 was vetoed, please reroll your candidate with this commit reverted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache Felix 0.8.0 Incubator Release
On 12/11/06, Richard S. Hall [EMAIL PROTECTED] wrote: Daniel Kulp wrote: On Monday 11 December 2006 10:57, Richard S. Hall wrote: As a follow up, we resolved every issue raised by Daniel except the signing portion. A new snapshot of the release is available at: http://people.apache.org/~rickhall/felix-0.8.0-incubator.html I was able to fix one minor bug in our maven bundle plugin that was causing LICENSE/NOTICE files to not get copied. Not quite there yet. The incubator DISCLAIMER file is still missing from the jars. That would prevent them going into maven repositories. Is that just a recommendation or a requirement? Our NOTICE files contain the incubator disclaimer text. it's a requirement that the text is present but AIUI in the NOTICE is ok (though perhaps a separate DISCLAIMER is clear) please let me know whether you plan to cut another candidate or whether i should review the one above For the signing part, you really need gnupg installed.Create a key if you don't already have one. (I think it's gpg --gen-key, but it's been a while since I looked into that part) Then you just need to run gpg -a -s filename.tar.gz to produce the asc files. You would also need to do: gpg --list-keys username KEYS gpg -a --export username KEYS and get that KEYS file added into the root of your SVN repository. Ideally, you would also upload it to one of the public keyservers as well. Longer term, you should also attend an apache keysigning party or similar to get your keys signed by enough apache people so that apache people can trust that those keys really are yours. Thanks for this info. We will work on it. see http://www.apache.org/dev/release-signing.html signing the releases is a requirement. having a well connected code signing key is definitely good but not mandatory - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
