On 8 December 2011 16:54, Karl Pauls <karlpa...@gmail.com> wrote:
> On Thu, Dec 8, 2011 at 5:17 PM, sebb <seb...@gmail.com> wrote:
>> On 8 December 2011 15:28, Karl Pauls <karlpa...@gmail.com> wrote:
>>> On Thu, Dec 8, 2011 at 4:21 PM, sebb <seb...@gmail.com> wrote:
>>>> On 8 December 2011 14:30, Karl Pauls <karlpa...@gmail.com> wrote:
>>>>> On Thu, Dec 8, 2011 at 1:08 PM, sebb <seb...@gmail.com> wrote:
>>>>>> On 8 December 2011 10:39, sebb <seb...@gmail.com> wrote:
>>>>>>> On 8 December 2011 10:14, Karl Pauls <karlpa...@gmail.com> wrote:
>>>>>>>> The vote on "Release ace version 0.8.1-incubator subprojects" has been
>>>>>>>> running for 72h and we didn't see any more votes from IPMC members
>>>>>>>> other than the 4 votes we already have from the vote on the ace dev
>>>>>>>> list. Given that this release was created specifically because some
>>>>>>>> issues with our last release where causing some debate on our "should
>>>>>>>> we ask for graduation" vote I really would have hoped that we get some
>>>>>>>> feedback on this one -- hence,
>>>>>>>
>>>>>>> I'm not saying this is a big factor in the lack of response, but
>>>>>>> normally votes include all the relevant information in the e-mail.
>>>>>>> In this case one has to go digging through another e-mail (using an
>>>>>>> offsite link as well) to find the details.
>>>>>>> The easier it is made for users, the more likely they are to respond.
>>>>>>>
>>>>>>> I'm copying the details below in case that helps anyone else:
>>>>>>>
>>>>>>> ===============================
>>>>>>> After our community graduation vote lead to a lengthy discussion about
>>>>>>> the 0.8.0-incubator release we did, we decided to roll a new ACE
>>>>>>> release, based on the original release.
>>>>>>>
>>>>>>> In the release we fix the issue that our previous source artifacts did
>>>>>>> not contain a pom.xml so building them was hard. You can now download
>>>>>>> a single, or all sources, and build them with a single command. Also,
>>>>>>> we added an extra artifact that contains the full source code, which
>>>>>>> is there for convenience in case someone wants to download all the
>>>>>>> sources and start developing from there. We did that in a way that is
>>>>>>> somewhat similar to Sling, but instead of using svn:externals we used
>>>>>>> Maven to generate this artifact (for more see the README.txt inside
>>>>>>> org.apache.ace.release.full 0.8.1-incubator) -- hence,
>>>>>>>
>>>>>>> I would like to call a vote on the following ace 0.8.1-incubator
>>>>>>> subproject releases:
>>>>>>>
>>>>>>> ace-pom 0.8.1-incubator org.apache.ace.client.automation
>>>>>>> 0.8.1-incubator org.apache.ace.client.repository.api 0.8.1-incubator
>>>>>>> org.apache.ace.client.repository.helper.base 0.8.1-incubator
>>>>>>> org.apache.ace.client.repository.helper.bundle 0.8.1-incubator
>>>>>>> org.apache.ace.client.repository.helper.configuration 0.8.1-incubator
>>>>>>> org.apache.ace.client.repository.helper.user 0.8.1-incubator
>>>>>>> org.apache.ace.client.repository.impl 0.8.1-incubator
>>>>>>> org.apache.ace.client.repository.useradmin 0.8.1-incubator
>>>>>>> org.apache.ace.configurator 0.8.1-incubator
>>>>>>> org.apache.ace.configurator.serveruseradmin 0.8.1-incubator
>>>>>>> org.apache.ace.configurator.useradmin.task 0.8.1-incubator
>>>>>>> org.apache.ace.consolelogger 0.8.1-incubator
>>>>>>> org.apache.ace.deployment.api 0.8.1-incubator
>>>>>>> org.apache.ace.deployment.deploymentadmin 0.8.1-incubator
>>>>>>> org.apache.ace.deployment.provider.api 0.8.1-incubator
>>>>>>> org.apache.ace.deployment.provider.base 0.8.1-incubator
>>>>>>> org.apache.ace.deployment.provider.filebased 0.8.1-incubator
>>>>>>> org.apache.ace.deployment.provider.repositorybased 0.8.1-incubator
>>>>>>> org.apache.ace.deployment.servlet 0.8.1-incubator
>>>>>>> org.apache.ace.deployment.streamgenerator 0.8.1-incubator
>>>>>>> org.apache.ace.deployment.task 0.8.1-incubator
>>>>>>> org.apache.ace.discovery.api 0.8.1-incubator
>>>>>>> org.apache.ace.discovery.property 0.8.1-incubator
>>>>>>> org.apache.ace.discovery.upnp 0.8.1-incubator
>>>>>>> org.apache.ace.gateway.log 0.8.1-incubator
>>>>>>> org.apache.ace.gateway.log.store 0.8.1-incubator
>>>>>>> org.apache.ace.httplistener 0.8.1-incubator
>>>>>>> org.apache.ace.identification.api 0.8.1-incubator
>>>>>>> org.apache.ace.identification.ifconfig 0.8.1-incubator
>>>>>>> org.apache.ace.identification.property 0.8.1-incubator
>>>>>>> org.apache.ace.launcher 0.8.1-incubator org.apache.ace.location.upnp
>>>>>>> 0.8.1-incubator org.apache.ace.log 0.8.1-incubator
>>>>>>> org.apache.ace.log.listener 0.8.1-incubator org.apache.ace.log.servlet
>>>>>>> 0.8.1-incubator org.apache.ace.log.task 0.8.1-incubator
>>>>>>> org.apache.ace.managementagent 0.8.1-incubator
>>>>>>> org.apache.ace.nodelauncher.amazon 0.8.1-incubator
>>>>>>> org.apache.ace.nodelauncher.api 0.8.1-incubator
>>>>>>> org.apache.ace.nodelauncher.ui 0.8.1-incubator
>>>>>>> org.apache.ace.obr.metadata 0.8.1-incubator org.apache.ace.obr.servlet
>>>>>>> 0.8.1-incubator org.apache.ace.obr.storage 0.8.1-incubator
>>>>>>> org.apache.ace.range.api 0.8.1-incubator org.apache.ace.release.full
>>>>>>> 0.8.1-incubator org.apache.ace.repository.api 0.8.1-incubator
>>>>>>> org.apache.ace.repository.ext 0.8.1-incubator
>>>>>>> org.apache.ace.repository.impl 0.8.1-incubator
>>>>>>> org.apache.ace.repository.servlet 0.8.1-incubator
>>>>>>> org.apache.ace.repository.task 0.8.1-incubator
>>>>>>> org.apache.ace.resourceprocessor.useradmin 0.8.1-incubator
>>>>>>> org.apache.ace.scheduler 0.8.1-incubator org.apache.ace.scheduler.api
>>>>>>> 0.8.1-incubator org.apache.ace.server.action 0.8.1-incubator
>>>>>>> org.apache.ace.server.action.popupmessage 0.8.1-incubator
>>>>>>> org.apache.ace.server.log.store 0.8.1-incubator
>>>>>>> org.apache.ace.tageditor 0.8.1-incubator
>>>>>>> org.apache.ace.target.defaults 0.8.1-incubator
>>>>>>> org.apache.ace.target.devgateway 0.8.1-incubator
>>>>>>> org.apache.ace.target.devserver 0.8.1-incubator org.apache.ace.util
>>>>>>> 0.8.1-incubator org.apache.ace.webconsole.plugin 0.8.1-incubator
>>>>>>> org.apache.ace.webui.vaadin 0.8.1-incubator
>>>>>>>
>>>>>>> Staging repositories:
>>>>>>> https://repository.apache.org/content/repositories/orgapacheace-259/
>>>>>>>
>>>>>>> Tags: https://svn.apache.org/repos/asf/incubator/ace/releases/
>>>>>>
>>>>>> Hard work checking/downloading those, as the directory still contains
>>>>>> the 0.8.0 tags.
>>>>>>
>>>>>>> Verify: You can download the keys used to sign the release from:
>>>>>>> https://svn.apache.org/repos/asf/incubator/ace/trunk/KEYS
>>>>>>>
>>>>>>> Download: You can use this UNIX script to download the release and
>>>>>>> verify the signatures:
>>>>>>> https://svn.apache.org/repos/asf/incubator/ace/trunk/check_staged_release.sh
>>>>>>>
>>>>>>> Usage: sh check_staged_release.sh 259 /tmp/ace-staging
>>>>>>>
>>>>>>> Build: Find the source-release.{zip|tar.gz} in the /tmp/ace-staging
>>>>>>> and follow the README.txt. If you want to build all in one go, start
>>>>>>> with: 
>>>>>>> /tmp/ace-staging/259/org/apache/ace/org.apache.ace.release.full/0.8.1-incubator/org.apache.ace.release.full-0.8.1-incubator.zip
>>>>>>>
>>>>>>> Get all source and build with one download:
>>>>>>> https://repository.apache.org/content/repositories/orgapacheace-259/org/apache/ace/org.apache.ace.release.full/0.8.1-incubator/org.apache.ace.release.full-0.8.1-incubator.zip
>>>>>>
>>>>>> This does not actually contain everything in the releases/ folder
>>>>>> tree; it does not contain the contents of
>>>>>>
>>>>>> https://svn.apache.org/repos/asf/incubator/ace/releases/org.apache.ace.release.full-0.8.1-incubator/
>>>>>
>>>>> No, it does not contain that one as it is the result of that one. If
>>>>> you look at the:
>>>>>
>>>>> https://repository.apache.org/content/repositories/orgapacheace-259/org/apache/ace/org.apache.ace.release.full/0.8.1-incubator/org.apache.ace.release.full-0.8.1-incubator-source-release.zip
>>>>>
>>>>> source release of it then you can see that we released its source as well.
>>>>>
>>>>>> It does contain lots of files that don't appear to be in SVN, for
>>>>>> example velocity.log and DISCLAIMER/NOTICE/LICENSE
>>>>>
>>>>> They are either in the tags or they are generated by maven during a
>>>>> release/build. They don't have to be in svn as we don't release svn.
>>>>
>>>> SVN provides traceability; a random collection of source files in a
>>>> zip would be very difficult to trace back to the originals.
>>>> AIUI that's one reason why source releases should only contain files
>>>> that are in SVN or directly derived therefrom.
>>>
>>> I agree, and that is the case.
>>>
>>>> AFAICT the velocity.log files are just noise, and could be excluded
>>>> (not a blocker).
>>>
>>> Yes, they are.
>>>
>>>>> However, they are generated if you build/release what is inside svn.
>>>>>
>>>>>> There is also a top-level pom.xml which does not appear to be in the SVN 
>>>>>> tags
>>>>>
>>>>> Same thing, it is generated upon release based on what is in svn. In
>>>>> this case, it is based on:
>>>>>
>>>>> https://svn.apache.org/repos/asf/incubator/ace/releases/org.apache.ace.release.full-0.8.1-incubator/src/main/resources/release-reactor.xml
>>>>>
>>>>> I think your confusion is that it is a combined source artifact along
>>>>> the line of what sling is doing. We had some discussions on the
>>>>> approach:
>>>>>
>>>>> http://apache.markmail.org/thread/4hloen52iewblpqs
>>>>>
>>>>> It is there for convenience in case someone wants to download all the
>>>>> sources in one go and start developing from there. We did that in a
>>>>> way that is somewhat similar to Sling, but instead of using
>>>>> svn:externals we used Maven to generate this artifact (for more see
>>>>> the README.txt inside org.apache.ace.release.full 0.8.1-incubator).
>>>>
>>>> [BTW, that is rather hard to read, owing to very long lines - max
>>>> nearly 525 chars.]
>>>>
>>>> So is it possible to start with the combined zip file and produce all
>>>> the artifacts that are stored in the Nexus repo?
>>>
>>> Yes. The only exception is the combining project as well, which is
>>> part of the release (see previous mail) but not included in the
>>> combined zip file it produces.
>>>
>>>> Or are there additional files that would need to be obtained from SVN?
>>>
>>> No. It is self-contained.
>>>
>>>> Just tried "mvn install" on the zip, and it failed with:
>>>>
>>>> [INFO] Building Apache ACE :: Log :: Listener
>>>> [INFO]    task-segment: [install]
>>>> ...
>>>> The system is out of resources.
>>>> Consult the following stack trace for details.
>>>> java.lang.OutOfMemoryError: PermGen space
>>>> ...
>>>> [INFO] Final Memory: 65M/314M
>>>>
>>>> What Maven settings are needed to build from source?
>>>
>>> Depends on your environment etc. For me, it builds out of the box but
>>> just in case:
>>>
>>> export MAVEN_OPTS=-Xmx1024m
>>
>> That fixed it for me; perhaps should be added to README.txt.
>
> Yeah, that makes sense.
>
>> The NOTICE file seems to have gathered some unnecessary verbiage.
>>
>> For example:
>>
>>>>>
>> This product includes software developed at
>> The Apache Software Foundation (http://www.apache.org/).
>> Licensed under the Apache License 2.0.
>> <<<
>>
>> should be just
>>
>>>>>
>> This product includes software developed at
>> The Apache Software Foundation (http://www.apache.org/).
>> <<<
>>
>> Similarly for all the other products - the license details belong in
>> the LICENSE file, for example see the httpd versions:
>>
>> http://svn.apache.org/repos/asf/httpd/httpd/trunk/NOTICE
>> http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE
>>
>> Httpd don't include 3rd party code using AL 2.0, but this can easily
>> be documented by adding a list of products that use the AL 2.0 after
>> the license text.
>>
>> It's a lot easier for end users if all the 3rd party products are
>> listed in the LICENSE file.
>
> Yeah, that makes sense.
>
>> I could not find the CDDL license.
>
> Ups, yes, I see - the LICENSE contains the notice section of the code
> under CDDL instead of the CDDL license itself (in the LICENSE see:
> Jersey and JSR-250 License). Don't think this is a blocker as it is at
> least saying it is licensed under CDDL this way but we need to fix
> this to contain the actual CDDL license text for the next release.

Sorry, but I think the problems with the NOTICE and LICENSE file go
deeper than that.

For example, for xstream, the license is at:

http://xstream.codehaus.org/license.html

This starts:

>>>
Copyright (c) 2003-2006, Joe Walnes
Copyright (c) 2006-2009, XStream Committers
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice ...
<<<

However, the copy in the LICENSE file omits the first paragraph entirely.
Which makes a nonsense of of the third (now second) paragraph as it
references a non-existent copyright notice.

The LICENSE file must contain the full license; the NOTICE file should
contain whatever notice is required by the license.

I think the same applies to at least one other entry in the license
file (knoplerfish)

In the case of dual licensed files (Jersey and JSR-250 License) the
NOTICE file should clearly state which one is being used, e.g.

>>:>
This product includes xxx from Oracle
The software is included under the CDDL License.
<<<


> regards,
>
> Karl
>
>>> export JAVA_HOME=<path-to-java6-sdk-home>
>>>
>>> regards,
>>>
>>> Karl
>>>
>>>>> regards,
>>>>>
>>>>> Karl
>>>>>
>>>>>>> Please vote to approve this release:
>>>>>>>
>>>>>>> [ ] +1 Approve the release
>>>>>>> [ ] -1 Veto the release (please provide specific comments)
>>>>>>
>>>>>>> ===============================
>>>>>>>
>>>>>>>> I'm going to give it another 24h but if I don't see any other votes
>>>>>>>> nor any request for more time (as I appreciate that it is a big
>>>>>>>> release) I'm going to call this vote successful based on the 4 IPMC
>>>>>>>> member votes we did already get. In that case, however, I don't want
>>>>>>>> to see it debated again during graduation i.e., speak now or forever
>>>>>>>> hold your peace.
>>>>>>>>
>>>>>>>> regards,
>>>>>>>>
>>>>>>>> Karl
>>>>>>>>
>>>>>>>> On Sun, Dec 4, 2011 at 10:56 PM, Karl Pauls <karlpa...@gmail.com> 
>>>>>>>> wrote:
>>>>>>>>> This is the second release of the ace incubator project called ace
>>>>>>>>> version 0.8.1-incubator subprojects releases.
>>>>>>>>>
>>>>>>>>> For details of the release see the original vote thread:
>>>>>>>>> http://markmail.org/thread/bxk47uzt7dzbajir
>>>>>>>>>
>>>>>>>>> We have already received 4 binding IPMC votes during the PPMC voting
>>>>>>>>> below. I'd like to continue the vote on general@ now to get the IPMC
>>>>>>>>> approval -- hence,
>>>>>>>>>
>>>>>>>>> Please vote to approve this release.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Dec 4, 2011 at 10:36 PM, Karl Pauls <karlpa...@gmail.com> 
>>>>>>>>> wrote:
>>>>>>>>>> Time to call the vote on the ace version 0.8.1-incubator subprojects 
>>>>>>>>>> releases.
>>>>>>>>>>
>>>>>>>>>> * +1 votes from Marcel Offermans***, Jean-Baptiste Onofré***, Toni
>>>>>>>>>> Menzel*, Bram de Kruijff, Angelo van der Sijpt*, Carsten Ziegeler***,
>>>>>>>>>> and Karl Pauls***.
>>>>>>>>>>
>>>>>>>>>> * No other votes
>>>>>>>>>>
>>>>>>>>>> The vote is successful. I will approach the Incubator PMC for 
>>>>>>>>>> approval.
>>>>>>>>>>
>>>>>>>>>> * == PPMC
>>>>>>>>>> ** == IPMC
>>>>>>>>>> *** == PPMC + IPMC
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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
>>>
>>
>> ---------------------------------------------------------------------
>> 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

Reply via email to