Well IMHO i don't think this release demonstrates that the poddling has an understanding of making or reviewing ASF releases and thats the point of requiring releases during incubation.
The comment from Guillaume in this thread was just about naming the SVN folder containing the tags "releases" instead of "tags" which no one is saying is a major issue. ...ant On Mon, Nov 21, 2011 at 1:47 PM, Karl Pauls <karlpa...@gmail.com> wrote: > Well, I agree and disagree at the same time :-). > > On the one hand (as pointed out by Guillaume Nodet), we should have > generated the source distribution for each bundle. We switched to a > newer parent pom and did miss that we should have configured that. > This makes it not very practical to build the release and we for sure > will configure it next time. > > On the other hand, we don't want to provide a single source > distribution for all bundles as we still want to release our bundles > independently from each other. > > In summary, the next release will contain easier to build source > distributions for each bundle but not a single source distribution for > all of them. That is a good catch overall but I don't think it makes > this release invalid (as the required things are there - just > unfortunately not very practical to build). As we are planning to > roll a 1.0.0 release anyways when graduated, I'd say lets ask for > graduation and then provide a 1.0.0 release which has the source > distribution configured per bundle. How about that? > > regards, > > Karl > > > On Mon, Nov 21, 2011 at 2:56 AM, ant elder <antel...@apache.org> wrote: >> That seems an unusual approach to building the src. It also means that >> to build the complete 0.8.0 release which contains 60 something >> modules would require manually typing in over 400 commands which is >> not very practical, i doubt anyone who voted +1 for the release >> actually did that. I think an ASF release like this should have also >> had a single source distribution that contained all the source for all >> those modules along with a build script to build them, and IMHO your >> mentors should have helped you do that. Would you consider doing >> another release like this before you graduate? >> >> ...ant >> >> On Thu, Nov 17, 2011 at 2:07 PM, Karl Pauls <karlpa...@gmail.com> wrote: >>> $ mkdir org.apache.ace.client.automation-0.8.0-incubator >>> $ cd org.apache.ace.client.automation-0.8.0-incubator/ >>> $ wget >>> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar >>> $ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar >>> $ wget >>> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom >>> $ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml >>> $ mvn clean install >>> >>> regards, >>> >>> Karl >>> >>> On Thu, Nov 17, 2011 at 2:54 PM, ant elder <ant.el...@gmail.com> wrote: >>>> To try that I just went to the ACE downloads page which has a bunch of >>>> jars and source jars to download, i downloaded the source of the first >>>> one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and >>>> looking inside there is the source to some Java classes but no build >>>> scripts or pom.xml file, so how would I go about building this? >>>> >>>> ...ant >>>> >>>> On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls <karlpa...@gmail.com> wrote: >>>>> Again, we had this discussion before namely, when the actual release >>>>> vote happened. I'm still confused why we have to go through this >>>>> again. You should be able to build all of the components by using the >>>>> -source.jar's that are provided. They contain what is necessary i.e., >>>>> the full source. >>>>> >>>>> regards, >>>>> >>>>> Karl >>>>> >>>>> On Thu, Nov 17, 2011 at 2:30 PM, sebb <seb...@gmail.com> wrote: >>>>>> On 17 November 2011 12:29, Karl Pauls <karlpa...@gmail.com> wrote: >>>>>>> I'm not sure what this has to do with the graduation vote. The release >>>>>>> as such has been accepted by the incubator pmc and there only need to >>>>>>> be one release. The source for each artifact is there, it is just per >>>>>>> artifact in the -source.jar. >>>>>> >>>>>> AFAICT the full source (as in SVN trunk) is not actually present in >>>>>> the distribution directory. >>>>>> >>>>>> For example, where are the top-level files in SVN (BUILDING, README) ? >>>>>> And the etc/ directory? >>>>>> >>>>>> If I wanted to build any or all of the components, there does not >>>>>> appear to be a way to do this from the files in the distribution. >>>>>> >>>>>>> There might be different set-up then a lot of other projects have it >>>>>>> but we release our stuff on a per artifact basis how it is done by for >>>>>>> example Apache Felix as well and never has been an issue (and didn't >>>>>>> become unmanageably either - also ymmv). >>>>>> >>>>>> The ASF primarily releases source; releases must include full source. >>>>>> >>>>>>> I agree about the KEYS file. We should have uploaded it to the dist >>>>>>> dir as well but at least we have it at some place so it should be easy >>>>>>> to fix. >>>>>>> >>>>>>> regards, >>>>>>> >>>>>>> Karl >>>>>>> >>>>>>> On Thu, Nov 17, 2011 at 1:07 PM, sebb <seb...@gmail.com> wrote: >>>>>>>> On 17 November 2011 10:42, Marcel Offermans >>>>>>>> <marcel.offerm...@luminis.nl> wrote: >>>>>>>>> In my opinion, ACE is ready to begin the process of graduating from >>>>>>>>> the Apache Incubator to a Top Level Project. >>>>>>>>> >>>>>>>>> Since joining the incubator in in May 2009 we've added 4 new >>>>>>>>> committers (12 in total now) from diverse organizations and did a >>>>>>>>> release in May this year to demonstrate we follow the Apache >>>>>>>>> guidelines. We've shown an ability to self-govern using accepted >>>>>>>>> Apache practices and ACE continues to attract new contributors and >>>>>>>>> users. >>>>>>>>> >>>>>>>>> The first step is to vote as a community, demonstrating that ACE is >>>>>>>>> ready and willing to graduate. Once this vote is succesful we create >>>>>>>>> a board resolution proposal or Charter and start a vote on the >>>>>>>>> general incubator list. The full process is described at >>>>>>>>> http://incubator.apache.org/guides/graduation.html#toplevel >>>>>>>>> >>>>>>>>> The vote is open for at least 72 hours. >>>>>>>> >>>>>>>> The last (and only) release was 0.8, as far as I can tell. >>>>>>>> >>>>>>>> There is no KEYS file in http://www.apache.org/dist/incubator/ace/, >>>>>>>> and there does not appear to be a full source archive of the project >>>>>>>> anywhere. >>>>>>>> The download page does not have a link to any source archives as far >>>>>>>> as I can tell. >>>>>>>> It does link to KEYS in SVN, but almost all other ASF projects have a >>>>>>>> copy of KEYS in the appropriate /dist directory. >>>>>>>> >>>>>>>> Normally releases are divided into binaries/ and source/ directories, >>>>>>>> with a KEYS file in the top-level, i.e. >>>>>>>> >>>>>>>> /dist/incubator/ace >>>>>>>> - KEYS >>>>>>>> - binaries/ace ....zip >>>>>>>> - sources/ace....zip >>>>>>>> >>>>>>>> Most of the files in the /dist/incubator/ace directory appear to be >>>>>>>> Maven artifacts; normally these are not stored in /dist but only in >>>>>>>> the Maven repo. >>>>>>>> Indeed most of the files are also in Maven Central. The only non-Maven >>>>>>>> files appear to be >>>>>>>> >>>>>>>> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip >>>>>>>> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip >>>>>>>> >>>>>>>> neither of which contains the source. >>>>>>>> >>>>>>>> I would expect the above zips to be in >>>>>>>> >>>>>>>> /dist/incubator/ace/binaries >>>>>>>> >>>>>>>> with corresponding source files in >>>>>>>> >>>>>>>> /dist/incubator/ace/source >>>>>>>> >>>>>>>> The SVN layout [1] is also a bit unusual. >>>>>>>> There is no tags/ directory for release tags, although there is a >>>>>>>> releases/ directory containing individual entries for each release for >>>>>>>> each component. >>>>>>>> This is likely to become unmanageable very quickly, if every release >>>>>>>> adds another 63 directory entries under releases/ >>>>>>>> >>>>>>>> [1] https://svn.apache.org/repos/asf/incubator/ace/ >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Karl Pauls >>>>>>> karlpa...@gmail.com >>>>>>> http://twitter.com/karlpauls >>>>>>> http://www.linkedin.com/in/karlpauls >>>>>>> https://profiles.google.com/karlpauls >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>>>> >>>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Karl Pauls >>>>> karlpa...@gmail.com >>>>> http://twitter.com/karlpauls >>>>> http://www.linkedin.com/in/karlpauls >>>>> https://profiles.google.com/karlpauls >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>> >>>> >>> >>> >>> >>> -- >>> Karl Pauls >>> karlpa...@gmail.com >>> http://twitter.com/karlpauls >>> http://www.linkedin.com/in/karlpauls >>> https://profiles.google.com/karlpauls >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > > > > -- > Karl Pauls > karlpa...@gmail.com > http://twitter.com/karlpauls > http://www.linkedin.com/in/karlpauls > https://profiles.google.com/karlpauls > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
