Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
On 11/21/06, Patrick Linskey [EMAIL PROTECTED] wrote: What do you do when it comes time to vote? Clearly, you can't be voting on the RC build, as that's not the final build (the final build doesn't include RC in the name, does it?), and it's my understanding that only final bits are voted on. Have a look at the recent number of RC's we've had to do to get our releases in shape... http://people.apache.org/~chirino/ basically we create a maven repo for each RC but the artifacts inside them are all 'the final build' with no RC in their name - then if the vote goes well, the RC is just moved to the right place. That way we don't have to do another build after the vote - but folks can still compare each RC etc. -- James --- http://radio.weblogs.com/0112098/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Publish Yoko M1 release
Great! Thanks and we will definitely consider all your suggestions for the next release. Edell. -Original Message- From: Jukka Zitting [mailto:[EMAIL PROTECTED] Sent: 22 November 2006 23:49 To: general@incubator.apache.org Subject: Re: [VOTE] Publish Yoko M1 release Hi, On 11/21/06, Jukka Zitting [EMAIL PROTECTED] wrote: I wouldn't call either a blocker, notably since the release packages were created and the vote started well before November 1st, but I'll need to give the packages a more thorough review before voting. +1 for the release, looks good PS. Some more issue to consider in future releases: * Having SNAPSHOT in the names of the release packages and jar libraries suggests at least to me that we're talking about an SVN snapshot instead of a tagged release. * Release notes would be a very welcome addition. * The README should contain a brief description of the project and pointers at least to the LICENSE and NOTICE files instead or in addition to just the build instructions. BR, Jukka Zitting - 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: Woden podling artifacts on ibiblio!!
The artifacts have been removed from the central repository. Jason. On 22 Nov 06, at 6:54 AM 22 Nov 06, Jeremy Hughes wrote: Unknown to the woden-dev team (until today) our M6 release artifacts have escaped to ibiblio (see this thread on woden-dev): http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200611.mbox/% [EMAIL PROTECTED] via them being erroneously being put into here: http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/ apache/woden/ Also, the file names lack the mandatory 'incubating' I feel duty bound to inform the IPMC in case there is something that can be done. Thanks, Jeremy - 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: Woden podling artifacts on ibiblio!!
thanks a ton Jason. -- dims On 11/23/06, Jason van Zyl [EMAIL PROTECTED] wrote: The artifacts have been removed from the central repository. Jason. On 22 Nov 06, at 6:54 AM 22 Nov 06, Jeremy Hughes wrote: Unknown to the woden-dev team (until today) our M6 release artifacts have escaped to ibiblio (see this thread on woden-dev): http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200611.mbox/% [EMAIL PROTECTED] via them being erroneously being put into here: http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/ apache/woden/ Also, the file names lack the mandatory 'incubating' I feel duty bound to inform the IPMC in case there is something that can be done. Thanks, Jeremy - 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] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Another question about LGPL code
When entering incubation, the ServiceMix project left a small amount of code at Codehaus. This code uses some vendor libraries or LGPL libraries (the jboss integration). However no one has ever released this code. I was wondering if we could import this code in the incubator servicemix svn area, maybe not in the main trunk, to avoid having some resources at Codehaus. I don't think we need to release it at all, but we could point users to this specific svn tree if they wish to use it. Would it be possible to do so ? I really don't think keeping some stuff at Codehaus is the way to go ... -- Cheers, Guillaume Nodet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache CXF 2.0-M1 Release
On 11/22/06, Dan Diephouse [EMAIL PROTECTED] wrote: snip We ask that you please vote to approve this release binary: [ ] +1 Release the binary as Apache CXF 2.0-M1 [ ] -1 Veto the release (please provide specific comments) -1 *** IMPORTANT *** my reading of http://svn.apache.org/repos/asf/incubator/cxf/tags/2.0-incubator-M1/distribution/src/main/release/licenses/wsi.html is that it *EXPLICITLY PREVENTS DISTRIBUTION*. if this is the case we need to remove all material in subversion under that license *RIGHT NOW* we've usually been able to work around mistakes like the past but the right thing to do is to stop distributing now and then work out what to do later. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache CXF 2.0-M1 Release
On 11/22/06, Dan Diephouse [EMAIL PROTECTED] wrote: The Apache CXF team has cut a candidate release bit unfortunate about the licensing foobar - looked a good release :-/ here are the notes i made before i found the license issue just FYI for feedback -- possible minor issues -- RAT: http://svn.apache.org/repos/asf/incubator/cxf/tags/2.0-incubator-M1/common/schemas/src/main/resources/schemas/wsdl/xml.xsd is missing a license header. doesn't look generated and looks complex enough for copyright. -- notes and suggestions (not requirements) -- consider including a glossary for acronyms either directly in the release notes or by reference separating release notes into README in the base and RELEASE_NOTE in the documentation is fine by me note that the release contains a number of documents from standards bodies including some which are under redistributable but not open source licenses. be aware of the http://www.apache.org/legal/3party.html proposal. xml documents are a difficult area. consider subscribing to legal-discuss where this policy is being formulated. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache CXF 2.0-M1 Release
Arggh... *mutters very bad things about standards organizations*. Looking into this deeper, and the only file that I can find that is associated with the WS-I organization is this one: http://fisheye3.cenqua.com/browse/celtixfire/trunk/distribution/src/main/release/samples/mtom/wsdl/wsi-swa.xsd?r=450119 To me the amount of creativity in this file is dubious, but it does clearly state that Use of this WS-I Material i governed by the WS-I Test License and other licenses. We'll go through and recheck things to make sure they're valid. We caught some stuff the first time through, but not all of it it seems. Thanks Robert, - Dan On 11/23/06, robert burrell donkin [EMAIL PROTECTED] wrote: On 11/22/06, Dan Diephouse [EMAIL PROTECTED] wrote: snip We ask that you please vote to approve this release binary: [ ] +1 Release the binary as Apache CXF 2.0-M1 [ ] -1 Veto the release (please provide specific comments) -1 *** IMPORTANT *** my reading of http://svn.apache.org/repos/asf/incubator/cxf/tags/2.0-incubator-M1/distribution/src/main/release/licenses/wsi.html is that it *EXPLICITLY PREVENTS DISTRIBUTION*. if this is the case we need to remove all material in subversion under that license *RIGHT NOW* we've usually been able to work around mistakes like the past but the right thing to do is to stop distributing now and then work out what to do later. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Re: [VOTE] Apache CXF 2.0-M1 Release
I've taken immediate action to remove these files from SVN. I'm curious to know if any other Apache projects depend on this wsi-swa.xsd file as I don't think its possible to use the JAXB 2.0 soap with attachments support without referencing this file. I know the JAXWS-RI itself redistributes it, which may have thrown us off. Are there any WS-I experts around that can shed light on this? It is hard to conform to the basic profile if you can't use their schemas in projects/products - which kind of defeats the point. I will start a thread sometime soon on legal-discuss on how to best deal with this. - Dan On 11/23/06, Dan Diephouse [EMAIL PROTECTED] wrote: Arggh... *mutters very bad things about standards organizations*. Looking into this deeper, and the only file that I can find that is associated with the WS-I organization is this one: http://fisheye3.cenqua.com/browse/celtixfire/trunk/distribution/src/main/release/samples/mtom/wsdl/wsi-swa.xsd?r=450119 To me the amount of creativity in this file is dubious, but it does clearly state that Use of this WS-I Material i governed by the WS-I Test License and other licenses. We'll go through and recheck things to make sure they're valid. We caught some stuff the first time through, but not all of it it seems. Thanks Robert, - Dan On 11/23/06, robert burrell donkin [EMAIL PROTECTED] wrote: On 11/22/06, Dan Diephouse [EMAIL PROTECTED] wrote: snip We ask that you please vote to approve this release binary: [ ] +1 Release the binary as Apache CXF 2.0-M1 [ ] -1 Veto the release (please provide specific comments) -1 *** IMPORTANT *** my reading of http://svn.apache.org/repos/asf/incubator/cxf/tags/2.0-incubator-M1/distribution/src/main/release/licenses/wsi.html is that it *EXPLICITLY PREVENTS DISTRIBUTION*. if this is the case we need to remove all material in subversion under that license *RIGHT NOW* we've usually been able to work around mistakes like the past but the right thing to do is to stop distributing now and then work out what to do later. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Re: [VOTE] Apache CXF 2.0-M1 Release
Hi Again, I did it a bit of poking around and it seems that no one else is using the wsi-swa.xsd which is good. There are however two files in Axis1 C though that are under the WS-I test license: http://svn.apache.org/viewvc/webservices/axis/trunk/c/tests/auto_build/wsi/analyzerConfig.xml?view=log http://svn.apache.org/viewvc/webservices/axis/trunk/c/tests/auto_build/wsi/monitorConfig.xml?view=log I'm not sure if these files are being distributed or not. Maybe the Axis team can comment? - Dan On 11/23/06, Dan Diephouse [EMAIL PROTECTED] wrote: I've taken immediate action to remove these files from SVN. I'm curious to know if any other Apache projects depend on this wsi-swa.xsd file as I don't think its possible to use the JAXB 2.0 soap with attachments support without referencing this file. I know the JAXWS-RI itself redistributes it, which may have thrown us off. Are there any WS-I experts around that can shed light on this? It is hard to conform to the basic profile if you can't use their schemas in projects/products - which kind of defeats the point. I will start a thread sometime soon on legal-discuss on how to best deal with this. - Dan On 11/23/06, Dan Diephouse [EMAIL PROTECTED] wrote: Arggh... *mutters very bad things about standards organizations*. Looking into this deeper, and the only file that I can find that is associated with the WS-I organization is this one: http://fisheye3.cenqua.com/browse/celtixfire/trunk/distribution/src/main/release/samples/mtom/wsdl/wsi-swa.xsd?r=450119 To me the amount of creativity in this file is dubious, but it does clearly state that Use of this WS-I Material i governed by the WS-I Test License and other licenses. We'll go through and recheck things to make sure they're valid. We caught some stuff the first time through, but not all of it it seems. Thanks Robert, - Dan On 11/23/06, robert burrell donkin [EMAIL PROTECTED] wrote: On 11/22/06, Dan Diephouse [EMAIL PROTECTED] wrote: snip We ask that you please vote to approve this release binary: [ ] +1 Release the binary as Apache CXF 2.0-M1 [ ] -1 Veto the release (please provide specific comments) -1 *** IMPORTANT *** my reading of http://svn.apache.org/repos/asf/incubator/cxf/tags/2.0-incubator-M1/distribution/src/main/release/licenses/wsi.html is that it *EXPLICITLY PREVENTS DISTRIBUTION*. if this is the case we need to remove all material in subversion under that license *RIGHT NOW* we've usually been able to work around mistakes like the past but the right thing to do is to stop distributing now and then work out what to do later. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
