Re: Heads up
Thanks for the advice. Is there any indication we cannot take a week or two to make the new release process repeatable and automated? I noticed that Mr. Fielding had backed off somewhat from removing current releases from distribution, which should give us a little more time. We could just add your filter to the current release script, but there may be better ways to do things if we have the chance. Karl On Fri, Mar 30, 2012 at 12:28 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Thu, Mar 29, 2012 at 2:28 PM, Karl Wright daddy...@gmail.com wrote: FWIW, I'm working on CONNECTORS-437 in a branch. Given the extent of the changes required, and the limits on my time, I'd expect this work to require at least another week to reach a point of rough equivalency to where we are now. If we want to push out the release now, the following steps should produce a close enough approximation of what people on general@ are asking for: $ tar zxf apache-manifoldcf-0.5-incubating-src.tar.gz $ find apache-manifoldcf-0.5-incubating -type f -name '*.jar' lib.txt $ find apache-manifoldcf-0.5-incubating -type f \! -name '*.jar' src.txt $ tar zcf apache-manifoldcf-0.5.1-incubating-lib.tar.gz -T lib.txt $ tar zcf apache-manifoldcf-0.5.1-incubating-src.tar.gz -T src.txt BR, Jukka Zitting
Re: Heads up
Hi, On Fri, Mar 30, 2012 at 6:53 PM, Karl Wright daddy...@gmail.com wrote: Is there any indication we cannot take a week or two to make the new release process repeatable and automated? No problem with that. BR, Jukka Zitting
Re: Heads up
Hi, On Wed, Mar 28, 2012 at 2:37 PM, Karl Wright daddy...@gmail.com wrote: Our build and release process was modeled, unfortunately, on other Apache Java projects, and these too have come under fire from the Board because the same practice has been followed, in some cases for more than a decade. I'm not sure what ManifoldCF did to become the focal point of this discussion, but there it is - and my personal opinion is that there is no chance of us releasing 0.5 without making significant changes. I'm very sorry about this situation. In the Incubator we've been hoping to avoid cases like this where someone on the IPMC comes up with a veto based on some new or previously unclear interpretation of Apache policies. Having such issues block releases that were previously considered OK is very unfortunate and I can only apologize for this situation. I'm hoping to drive the discussion on general@ to some reasonable consensus on what the actual problem is here and how affected projects should deal with it. Meanwhile, unless there's a rush to get the 0.5 release out, I wouldn't recommend taking too hasty actions in terms of CONNECTORS-437. BR, Jukka Zitting
Re: Heads up
Thanks for the update. FWIW, I'm working on CONNECTORS-437 in a branch. Given the extent of the changes required, and the limits on my time, I'd expect this work to require at least another week to reach a point of rough equivalency to where we are now. After that we probably will want to do more reorganization and update the documentation. So we're looking at weeks, but probably not months. If it turns out that the consensus is that all of our current releases go away, I'd want to have a prompt response ready. If not, we can take our time and get it right. Karl On Thu, Mar 29, 2012 at 8:11 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Wed, Mar 28, 2012 at 2:37 PM, Karl Wright daddy...@gmail.com wrote: Our build and release process was modeled, unfortunately, on other Apache Java projects, and these too have come under fire from the Board because the same practice has been followed, in some cases for more than a decade. I'm not sure what ManifoldCF did to become the focal point of this discussion, but there it is - and my personal opinion is that there is no chance of us releasing 0.5 without making significant changes. I'm very sorry about this situation. In the Incubator we've been hoping to avoid cases like this where someone on the IPMC comes up with a veto based on some new or previously unclear interpretation of Apache policies. Having such issues block releases that were previously considered OK is very unfortunate and I can only apologize for this situation. I'm hoping to drive the discussion on general@ to some reasonable consensus on what the actual problem is here and how affected projects should deal with it. Meanwhile, unless there's a rush to get the 0.5 release out, I wouldn't recommend taking too hasty actions in terms of CONNECTORS-437. BR, Jukka Zitting
Re: Heads up
Hi Karl, I'm trying to catch up all the points raised in the general@ thread in order to better understand them and what we actually need (not) to do. Will come back on this as soon as I can with more comments. Tommaso 2012/3/28 Karl Wright daddy...@gmail.com Dear Developers, In case you haven't been following our fortunes in the gene...@incubator.apache.org list, it has become clear that ManifoldCF has resurrected an old battle having to do with rules pertaining to the legality of including binaries in a source release. It is therefore my opinion that the 0.5-incubating release will not occur until we substantially rework our build process, especially where it pertains to dependencies. A short way of stating the problem is that binary dependencies can no longer be included in the source zip/tar.gz that gets voted on. A request has also been made for us to remove all previous releases that violate this principle, which is all of them. I am waiting to see how the discussion pans out before acting on this request. Our build and release process was modeled, unfortunately, on other Apache Java projects, and these too have come under fire from the Board because the same practice has been followed, in some cases for more than a decade. I'm not sure what ManifoldCF did to become the focal point of this discussion, but there it is - and my personal opinion is that there is no chance of us releasing 0.5 without making significant changes. I've captured what I think needs to be done in CONNECTORS-437, and have been working through an ordered process of first setting up an svn-based repository for those binaries which have been patched or otherwise contain fixes not present in official released code, with a long-term goal in mind of eventually having all dependencies come from the Maven repository. This is in svn under https://svn.apache.org/repos/asf/incubator/lcf/bin-dist;. I will also be extending the ant download-dependencies target to pull in ALL binaries, not just those which come with incompatible licenses. The ticket is probably incomplete; I'll be adding more stuff as I find it. Thanks, Karl
