You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-dev@incubator.apache.org by Xavier Hanin <xa...@gmail.com> on 2007/03/14 07:54:34 UTC
Release todo list
Hi,
I think it would be a good thing to produce a first incubating version of
Ivy early April, and I would like to check what we need to do, and who does
what.
This version would only be a beta version, or even an alpha, so I don't
think we need to concentrate on technical things. The purpose would be to
show that we are able to release something in the incubator, and to show
that the project is alive and working on delivering stuff. It could also be
a basis for people who want to use an apache version with the new API, and
could serve as a basis for my talk at ApacheCon.
So I would like to know what do we need to do to make such a release. What
is the process of releasing software in the incubator? What are the
requirements we need to address? Who can perform the remaining tasks?
- Xavier
Re: Release todo list
Posted by Xavier Hanin <xa...@gmail.com>.
On 3/22/07, Xavier Hanin <xa...@gmail.com> wrote:
>
> On 3/22/07, Steve Loughran <st...@apache.org> wrote:
> >
> > Xavier Hanin wrote:
> >
> > >
> > > These three things should already be straightforward to get:
> > > $ svn co https://svn.apache.org/repos/asf/incubator/ivy/core/trunk ivy
> > > $ cd ivy
> > > $ ant release
> > > This generates the same kinf of files as those available here:
> > > http://incubator.apache.org/ivy/downloads/latest/
> > >
> > > I'll need to check if building is still ok with the source distrib.
> > And I
> > > don't know if the packaging used is ok.
> >
> > it does not like me
>
>
> Ok, I think I get it. The problem occurs on the trunk version, because its
> own settings has been refactored with the new name, but it still use ivy
> 1.4.1 for resolving dependencies. I'll fix that in a moment.
>
Fixed
- Xavier
Re: Release todo list
Posted by Xavier Hanin <xa...@gmail.com>.
On 3/22/07, Steve Loughran <st...@apache.org> wrote:
>
> Xavier Hanin wrote:
>
> >
> > These three things should already be straightforward to get:
> > $ svn co https://svn.apache.org/repos/asf/incubator/ivy/core/trunk ivy
> > $ cd ivy
> > $ ant release
> > This generates the same kinf of files as those available here:
> > http://incubator.apache.org/ivy/downloads/latest/
> >
> > I'll need to check if building is still ok with the source distrib. And
> I
> > don't know if the packaging used is ok.
>
> it does not like me
Ok, I think I get it. The problem occurs on the trunk version, because its
own settings has been refactored with the new name, but it still use ivy
1.4.1 for resolving dependencies. I'll fix that in a moment.
- Xavier
resolve:
> [ivy:retrieve] :: resolving dependencies :: [ apache | ivy |
> working@chamonix ]
> [ivy:retrieve] confs: [default, test]
> [ivy:retrieve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | default | 6 | 0 | 0 | 0 || 0 |
> 0 |
> | test | 1 | 0 | 0 | 0 || 0 |
> 0 |
>
> ---------------------------------------------------------------------
> [ivy:retrieve]
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve] :::: WARNINGS
> [ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve] :: UNRESOLVED DEPENDENCIES ::
> [ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve] :: [ apache | commons-vfs | 20060920 ]: no
> resolver found for [ apache | commons-vfs ]: check your configuration
> [ivy:retrieve] :: [ apache | oro | 2.0.8 ]: no resolver found
> for [ apache | oro ]: check your configuration
> [ivy:retrieve] :: [ jcraft | jsch | 0.1.25 ]: no resolver found
> for [ jcraft | jsch ]: check your configuration
> [ivy:retrieve] :: [ apache | ant | 1.6.5 ]: no resolver found
> for [ apache | ant ]: check your configuration
> [ivy:retrieve] :: [ junit | junit | 3.8.2 ]: no resolver found
> for [ junit | junit ]: check your configuration
> [ivy:retrieve] :: [ apache | commons-cli | 1.0 ]: no resolver
> found for [ apache | commons-cli ]: check your configuration
> [ivy:retrieve] :: [ apache | commons-httpclient | 3.0 ]: no
> resolver found for [ apache | commons-httpclient ]: check your
> configuration
> [ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve] :::: ERRORS
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | ant ]: check your
> configuration[ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | commons-httpclient ]:
> check your configuration
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | commons-cli ]: check
> your configuration
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | oro ]: check your
> configuration[ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | commons-vfs ]: check
> your configuration
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ jcraft | jsch ]: check your
> configuration
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ junit | junit ]: check your
> configuration
> [ivy:retrieve]
> [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>
> BUILD FAILED - at 22/03/07 14:56
> /home/slo/Java/Apache/ivy/build.xml:118: impossible to resolve
> dependencies: resolve failed - see output for details
>
>
>
Re: Release todo list
Posted by Steve Loughran <st...@apache.org>.
Xavier Hanin wrote:
> On 3/22/07, Steve Loughran <st...@apache.org> wrote:
>>
>> Xavier Hanin wrote:
>>
>> >
>> > These three things should already be straightforward to get:
>> > $ svn co https://svn.apache.org/repos/asf/incubator/ivy/core/trunk ivy
>> > $ cd ivy
>> > $ ant release
>> > This generates the same kinf of files as those available here:
>> > http://incubator.apache.org/ivy/downloads/latest/
>> >
>> > I'll need to check if building is still ok with the source distrib. And
>> I
>> > don't know if the packaging used is ok.
>>
>> it does not like me
>
>
> Could you give more detail on your environment, it seems to be working
> properly on my box:
> - windows vista
> - ant 1.6.5 with junit-3.8.2.jar in ant lib
> - jdk 1.4.2
> - ~/.ivy cleaned before build
> - ran "ant" in the ivy-1.5.0-incubating-dev-20070308022022 directory
> obtained after extraction of src distrib available in
> http://incubator.apache.org/ivy/downloads/latest/
>
> My only problem is that there is an online test failing, due to the
> renaming
> of the ivyconf file from Ivy website (I will fix that). But no problem of
> dependency resolution.
>
> - Xavier
Key things.
-ant1.7, (which isnt the cause, as Gump is Ant1.7+).
-java1.6
-ivy in ant lib dir
-ubuntu linux
-proxied web access (ANT_OPTS is set up for this)
------- Ant diagnostics report -------
Apache Ant version 1.7.0 compiled on December 15 2006
-------------------------------------------
Implementation Version
-------------------------------------------
core tasks : 1.7.0
optional tasks : not available
-------------------------------------------
ANT PROPERTIES
-------------------------------------------
ant.version: Apache Ant version 1.7.0 compiled on December 15 2006
ant.java.version: 1.6
ant.core.lib: /home/slo/Java/Apache/ant/lib/ant.jar
ant.home: /home/slo/Java/Apache/ant
-------------------------------------------
ANT_HOME/lib jar listing
-------------------------------------------
ant.home: /home/slo/Java/Apache/ant
commons-logging-api-1.0.4.jar (26202 bytes)
xml-apis-2.0.2.jar (109318 bytes)
checkstyle-2.3.jar (178503 bytes)
ant-antlr.jar (5773 bytes)
ant-jdepend.jar (8156 bytes)
avalon-framework-4.1.3.jar (63966 bytes)
ant-apache-oro.jar (39595 bytes)
jython-2.1.jar (719950 bytes)
bsf-2.3.0.jar (175348 bytes)
jsvn-0.9-dev.jar (192979 bytes)
ant-trax.jar (6901 bytes)
commons-collections.jar (568086 bytes)
ant-apache-regexp.jar (3741 bytes)
logkit-1.0.1.jar (72150 bytes)
ant-jmf.jar (6613 bytes)
ant-jsch.jar (30126 bytes)
ant-apache-bsf.jar (3984 bytes)
jsch-0.1.27.jar (122011 bytes)
ant-swing.jar (6717 bytes)
regexp-1.3.jar (25429 bytes)
commons-logging-1.0.4.jar (38015 bytes)
resolver.jar (60047 bytes)
bsf-2.4.0.jar (113369 bytes)
commons-net-1.4.0.jar (180799 bytes)
mail.jar (280984 bytes)
cpptasks.jar (199636 bytes)
maven-artifact-ant-2.0.4-dep.jar (887507 bytes)
ant-antunit-1.0.jar (28568 bytes)
Tidy.jar (137810 bytes)
xercesImpl.jar (1223877 bytes)
ant-apache-bcel.jar (8631 bytes)
jruby-0.8.3.jar (1088261 bytes)
oro-2.0.8.jar (65261 bytes)
ant-javamail.jar (7015 bytes)
ant-junit.jar (92796 bytes)
ant-commons-net.jar (47167 bytes)
ant-commons-logging.jar (3947 bytes)
jmxri.jar (223212 bytes)
which-1.0.jar (17398 bytes)
commons-digester.jar (110855 bytes)
ivy-1.4.1.jar (571869 bytes)
activation-1.0.2.jar (55147 bytes)
jdepend-2.7.jar (83365 bytes)
js-1.6R3.jar (708578 bytes)
ant-apache-log4j.jar (3078 bytes)
ant.jar (1289810 bytes)
xml-resolver-1.1.jar (60047 bytes)
log4j-1.2.13.jar (358180 bytes)
xml-apis.jar (194354 bytes)
jakarta-regexp-1.2.jar (29871 bytes)
jakarta-oro-2.0.4.jar (79160 bytes)
commons-modeler.jar (110906 bytes)
ant-nodeps.jar (429655 bytes)
xalan-2.7.0.jar (2730442 bytes)
ant-testutil.jar (14926 bytes)
junit-3.8.2.jar (120640 bytes)
ant-launcher.jar (11737 bytes)
xmlParserAPIs-2.6.1.jar (124724 bytes)
bsh-2.0b4.jar (281694 bytes)
commons-beanutils.jar (139998 bytes)
ant-apache-resolver.jar (4084 bytes)
bcel-5.1.jar (515920 bytes)
ant-contrib.jar (194050 bytes)
antlr-2.7.2.jar (358273 bytes)
-------------------------------------------
USER_HOME/.ant/lib jar listing
-------------------------------------------
user.home: /home/slo
antbook-log-1.0.jar (3216 bytes)
-------------------------------------------
Tasks availability
-------------------------------------------
image : Not Available (the implementation class is not present)
wlrun : Not Available (the implementation class is not present)
stlist : Not Available (the implementation class is not present)
netrexxc : Not Available (the implementation class is not present)
starteam : Not Available (the implementation class is not present)
stylebook : Not Available (the implementation class is not present)
stlabel : Not Available (the implementation class is not present)
stcheckin : Not Available (the implementation class is not present)
stcheckout : Not Available (the implementation class is not present)
ejbc : Not Available (the implementation class is not present)
wlstop : Not Available (the implementation class is not present)
ddcreator : Not Available (the implementation class is not present)
A task being missing/unavailable should only matter if you are trying to
use it
-------------------------------------------
org.apache.env.Which diagnostics
-------------------------------------------
#---- BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.6.0
file.encoding=UTF-8
java.ext.dirs=/usr/java/jdk1.6.0/jre/lib/ext:/usr/java/packages/lib/ext
java.class.path=/home/slo/Java/Apache/ant/lib/ant-launcher.jar:/home/slo/.ant/lib/antbook-log-1.0.jar:/home/slo/Java/Apache/ant/lib/commons-logging-api-1.0.4.jar:/home/slo/Java/Apache/ant/lib/xml-apis-2.0.2.jar:/home/slo/Java/Apache/ant/lib/checkstyle-2.3.jar:/home/slo/Java/Apache/ant/lib/ant-antlr.jar:/home/slo/Java/Apache/ant/lib/ant-jdepend.jar:/home/slo/Java/Apache/ant/lib/avalon-framework-4.1.3.jar:/home/slo/Java/Apache/ant/lib/ant-apache-oro.jar:/home/slo/Java/Apache/ant/lib/jython-2.1.jar:/home/slo/Java/Apache/ant/lib/bsf-2.3.0.jar:/home/slo/Java/Apache/ant/lib/jsvn-0.9-dev.jar:/home/slo/Java/Apache/ant/lib/ant-trax.jar:/home/slo/Java/Apache/ant/lib/commons-collections.jar:/home/slo/Java/Apache/ant/lib/ant-apache-regexp.jar:/home/slo/Java/Apache/ant/lib/logkit-1.0.1.jar:/home/slo/Java/Apache/ant/lib/ant-jmf.jar:/home/slo/Java/Apache/ant/lib/ant-jsch.jar:/home/slo/Java/Apache/ant/lib/ant-apache-bsf.jar:/home/slo/Java/Apache/ant/lib/jsch-0.1.27.jar:/home/slo/Java/Apache/
ant/lib/ant-swing.jar:/home/slo/Java/Apache/ant/lib/regexp-1.3.jar:/home/slo/Java/Apache/ant/lib/commons-logging-1.0.4.jar:/home/slo/Java/Apache/ant/lib/resolver.jar:/home/slo/Java/Apache/ant/lib/bsf-2.4.0.jar:/home/slo/Java/Apache/ant/lib/commons-net-1.4.0.jar:/home/slo/Java/Apache/ant/lib/mail.jar:/home/slo/Java/Apache/ant/lib/cpptasks.jar:/home/slo/Java/Apache/ant/lib/maven-artifact-ant-2.0.4-dep.jar:/home/slo/Java/Apache/ant/lib/ant-antunit-1.0.jar:/home/slo/Java/Apache/ant/lib/Tidy.jar:/home/slo/Java/Apache/ant/lib/xercesImpl.jar:/home/slo/Java/Apache/ant/lib/ant-apache-bcel.jar:/home/slo/Java/Apache/ant/lib/jruby-0.8.3.jar:/home/slo/Java/Apache/ant/lib/oro-2.0.8.jar:/home/slo/Java/Apache/ant/lib/ant-javamail.jar:/home/slo/Java/Apache/ant/lib/ant-junit.jar:/home/slo/Java/Apache/ant/lib/ant-commons-net.jar:/home/slo/Java/Apache/ant/lib/ant-commons-logging.jar:/home/slo/Java/Apache/ant/lib/jmxri.jar:/home/slo/Java/Apache/ant/lib/which-1.0.jar:/home/slo/Java/Apache/ant/lib/
commons-digester.jar:/home/slo/Java/Apache/ant/lib/ivy-1.4.1.jar:/home/slo/Java/Apache/ant/lib/activation-1.0.2.jar:/home/slo/Java/Apache/ant/lib/jdepend-2.7.jar:/home/slo/Java/Apache/ant/lib/js-1.6R3.jar:/home/slo/Java/Apache/ant/lib/ant-apache-log4j.jar:/home/slo/Java/Apache/ant/lib/ant.jar:/home/slo/Java/Apache/ant/lib/xml-resolver-1.1.jar:/home/slo/Java/Apache/ant/lib/log4j-1.2.13.jar:/home/slo/Java/Apache/ant/lib/xml-apis.jar:/home/slo/Java/Apache/ant/lib/jakarta-regexp-1.2.jar:/home/slo/Java/Apache/ant/lib/jakarta-oro-2.0.4.jar:/home/slo/Java/Apache/ant/lib/commons-modeler.jar:/home/slo/Java/Apache/ant/lib/ant-nodeps.jar:/home/slo/Java/Apache/ant/lib/xalan-2.7.0.jar:/home/slo/Java/Apache/ant/lib/ant-testutil.jar:/home/slo/Java/Apache/ant/lib/junit-3.8.2.jar:/home/slo/Java/Apache/ant/lib/ant-launcher.jar:/home/slo/Java/Apache/ant/lib/xmlParserAPIs-2.6.1.jar:/home/slo/Java/Apache/ant/lib/bsh-2.0b4.jar:/home/slo/Java/Apache/ant/lib/commons-beanutils.jar:/home/slo/Java/Apac
he/ant/lib/ant-apache-resolver.jar:/home/slo/Java/Apache/ant/lib/bcel-5.1.jar:/home/slo/Java/Apache/ant/lib/ant-contrib.jar:/home/slo/Java/Apache/ant/lib/antlr-2.7.2.jar:/usr/java/jdk1.6.0/lib/tools.jar
os.name=Linux
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=/usr/java/jdk1.6.0/jre/lib/resources.jar:/usr/java/jdk1.6.0/jre/lib/rt.jar:/usr/java/jdk1.6.0/jre/lib/sunrsasign.jar:/usr/java/jdk1.6.0/jre/lib/jsse.jar:/usr/java/jdk1.6.0/jre/lib/jce.jar:/usr/java/jdk1.6.0/jre/lib/charsets.jar:/usr/java/jdk1.6.0/jre/classes
java.runtime.name=Java(TM) SE Runtime Environment
#---- END: Which report
-------------------------------------------
XML Parser information
-------------------------------------------
XML Parser : org.apache.xerces.jaxp.SAXParserImpl
XML Parser Location: /home/slo/Java/Apache/ant/lib/xercesImpl.jar
Namespace-aware parser : org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser
Namespace-aware parser Location:
/home/slo/Java/Apache/ant/lib/xercesImpl.jar
-------------------------------------------
System properties
-------------------------------------------
java.runtime.name : Java(TM) SE Runtime Environment
sun.boot.library.path : /usr/java/jdk1.6.0/jre/lib/i386
java.vm.version : 1.6.0-b105
ant.library.dir : /home/slo/Java/Apache/ant/lib
java.vm.vendor : Sun Microsystems Inc.
java.vendor.url : http://java.sun.com/
path.separator : :
java.vm.name : Java HotSpot(TM) Server VM
file.encoding.pkg : sun.io
user.country : GB
sun.java.launcher : SUN_STANDARD
sun.os.patch.level : unknown
java.vm.specification.name : Java Virtual Machine Specification
user.dir : /home/slo/Java/Apache/ivy
java.runtime.version : 1.6.0-b105
java.awt.graphicsenv : sun.awt.X11GraphicsEnvironment
java.endorsed.dirs : /usr/java/jdk1.6.0/jre/lib/endorsed
os.arch : i386
java.io.tmpdir : /tmp
line.separator :
java.vm.specification.vendor : Sun Microsystems Inc.
os.name : Linux
ant.home : /home/slo/Java/Apache/ant
sun.jnu.encoding : UTF-8
java.library.path :
/usr/java/jdk1.6.0/jre/lib/i386/server:/usr/java/jdk1.6.0/jre/lib/i386:/usr/java/jdk1.6.0/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
http.proxyPort : 8088
java.specification.name : Java Platform API Specification
java.class.version : 50.0
sun.management.compiler : HotSpot Server Compiler
os.version : 2.6.15-28-686
user.home : /home/slo
user.timezone : Europe/London
java.awt.printerjob : sun.print.PSPrinterJob
file.encoding : UTF-8
java.specification.version : 1.6
user.name : slo
java.class.path :
/home/slo/Java/Apache/ant/lib/ant-launcher.jar:/home/slo/.ant/lib/antbook-log-1.0.jar:/home/slo/Java/Apache/ant/lib/commons-logging-api-1.0.4.jar:/home/slo/Java/Apache/ant/lib/xml-apis-2.0.2.jar:/home/slo/Java/Apache/ant/lib/checkstyle-2.3.jar:/home/slo/Java/Apache/ant/lib/ant-antlr.jar:/home/slo/Java/Apache/ant/lib/ant-jdepend.jar:/home/slo/Java/Apache/ant/lib/avalon-framework-4.1.3.jar:/home/slo/Java/Apache/ant/lib/ant-apache-oro.jar:/home/slo/Java/Apache/ant/lib/jython-2.1.jar:/home/slo/Java/Apache/ant/lib/bsf-2.3.0.jar:/home/slo/Java/Apache/ant/lib/jsvn-0.9-dev.jar:/home/slo/Java/Apache/ant/lib/ant-trax.jar:/home/slo/Java/Apache/ant/lib/commons-collections.jar:/home/slo/Java/Apache/ant/lib/ant-apache-regexp.jar:/home/slo/Java/Apache/ant/lib/logkit-1.0.1.jar:/home/slo/Java/Apache/ant/lib/ant-jmf.jar:/home/slo/Java/Apache/ant/lib/ant-jsch.jar:/home/slo/Java/Apache/ant/lib/ant-apache-bsf.jar:/home/slo/Java/Apache/ant/lib/jsch-0.1.27.jar:/home/slo/Java/Apache/ant/lib/ant-swin
g.jar:/home/slo/Java/Apache/ant/lib/regexp-1.3.jar:/home/slo/Java/Apache/ant/lib/commons-logging-1.0.4.jar:/home/slo/Java/Apache/ant/lib/resolver.jar:/home/slo/Java/Apache/ant/lib/bsf-2.4.0.jar:/home/slo/Java/Apache/ant/lib/commons-net-1.4.0.jar:/home/slo/Java/Apache/ant/lib/mail.jar:/home/slo/Java/Apache/ant/lib/cpptasks.jar:/home/slo/Java/Apache/ant/lib/maven-artifact-ant-2.0.4-dep.jar:/home/slo/Java/Apache/ant/lib/ant-antunit-1.0.jar:/home/slo/Java/Apache/ant/lib/Tidy.jar:/home/slo/Java/Apache/ant/lib/xercesImpl.jar:/home/slo/Java/Apache/ant/lib/ant-apache-bcel.jar:/home/slo/Java/Apache/ant/lib/jruby-0.8.3.jar:/home/slo/Java/Apache/ant/lib/oro-2.0.8.jar:/home/slo/Java/Apache/ant/lib/ant-javamail.jar:/home/slo/Java/Apache/ant/lib/ant-junit.jar:/home/slo/Java/Apache/ant/lib/ant-commons-net.jar:/home/slo/Java/Apache/ant/lib/ant-commons-logging.jar:/home/slo/Java/Apache/ant/lib/jmxri.jar:/home/slo/Java/Apache/ant/lib/which-1.0.jar:/home/slo/Java/Apache/ant/lib/commons-digester
.jar:/home/slo/Java/Apache/ant/lib/ivy-1.4.1.jar:/home/slo/Java/Apache/ant/lib/activation-1.0.2.jar:/home/slo/Java/Apache/ant/lib/jdepend-2.7.jar:/home/slo/Java/Apache/ant/lib/js-1.6R3.jar:/home/slo/Java/Apache/ant/lib/ant-apache-log4j.jar:/home/slo/Java/Apache/ant/lib/ant.jar:/home/slo/Java/Apache/ant/lib/xml-resolver-1.1.jar:/home/slo/Java/Apache/ant/lib/log4j-1.2.13.jar:/home/slo/Java/Apache/ant/lib/xml-apis.jar:/home/slo/Java/Apache/ant/lib/jakarta-regexp-1.2.jar:/home/slo/Java/Apache/ant/lib/jakarta-oro-2.0.4.jar:/home/slo/Java/Apache/ant/lib/commons-modeler.jar:/home/slo/Java/Apache/ant/lib/ant-nodeps.jar:/home/slo/Java/Apache/ant/lib/xalan-2.7.0.jar:/home/slo/Java/Apache/ant/lib/ant-testutil.jar:/home/slo/Java/Apache/ant/lib/junit-3.8.2.jar:/home/slo/Java/Apache/ant/lib/ant-launcher.jar:/home/slo/Java/Apache/ant/lib/xmlParserAPIs-2.6.1.jar:/home/slo/Java/Apache/ant/lib/bsh-2.0b4.jar:/home/slo/Java/Apache/ant/lib/commons-beanutils.jar:/home/slo/Java/Apache/ant/lib/ant-a
pache-resolver.jar:/home/slo/Java/Apache/ant/lib/bcel-5.1.jar:/home/slo/Java/Apache/ant/lib/ant-contrib.jar:/home/slo/Java/Apache/ant/lib/antlr-2.7.2.jar:/usr/java/jdk1.6.0/lib/tools.jar
java.vm.specification.version : 1.0
sun.arch.data.model : 32
java.home : /usr/java/jdk1.6.0/jre
java.specification.vendor : Sun Microsystems Inc.
user.language : en
java.vm.info : mixed mode
java.version : 1.6.0
java.ext.dirs : /usr/java/jdk1.6.0/jre/lib/ext:/usr/java/packages/lib/ext
sun.boot.class.path :
/usr/java/jdk1.6.0/jre/lib/resources.jar:/usr/java/jdk1.6.0/jre/lib/rt.jar:/usr/java/jdk1.6.0/jre/lib/sunrsasign.jar:/usr/java/jdk1.6.0/jre/lib/jsse.jar:/usr/java/jdk1.6.0/jre/lib/jce.jar:/usr/java/jdk1.6.0/jre/lib/charsets.jar:/usr/java/jdk1.6.0/jre/classes
http.proxyHost : web-proxy
java.vendor : Sun Microsystems Inc.
file.separator : /
java.vendor.url.bug : http://java.sun.com/cgi-bin/bugreport.cgi
sun.cpu.endian : little
sun.io.unicode.encoding : UnicodeLittle
sun.desktop : gnome
sun.cpu.isalist :
-------------------------------------------
Temp dir
-------------------------------------------
Temp dir is /tmp
Temp dir is writeable
Temp dir alignment with system clock is -478 ms
-------------------------------------------
Locale information
-------------------------------------------
Timezone Greenwich Mean Time offset=0
-------------------------------------------
Proxy information
-------------------------------------------
http.proxyHost = "web-proxy"
http.proxyPort = "8088"
Java1.5+ proxy settings:
HTTP @ web-proxy:8088 web-proxy:8088 [unresolved]
Re: Release todo list
Posted by Xavier Hanin <xa...@gmail.com>.
On 3/22/07, Steve Loughran <st...@apache.org> wrote:
>
> Xavier Hanin wrote:
>
> >
> > These three things should already be straightforward to get:
> > $ svn co https://svn.apache.org/repos/asf/incubator/ivy/core/trunk ivy
> > $ cd ivy
> > $ ant release
> > This generates the same kinf of files as those available here:
> > http://incubator.apache.org/ivy/downloads/latest/
> >
> > I'll need to check if building is still ok with the source distrib. And
> I
> > don't know if the packaging used is ok.
>
> it does not like me
Could you give more detail on your environment, it seems to be working
properly on my box:
- windows vista
- ant 1.6.5 with junit-3.8.2.jar in ant lib
- jdk 1.4.2
- ~/.ivy cleaned before build
- ran "ant" in the ivy-1.5.0-incubating-dev-20070308022022 directory
obtained after extraction of src distrib available in
http://incubator.apache.org/ivy/downloads/latest/
My only problem is that there is an online test failing, due to the renaming
of the ivyconf file from Ivy website (I will fix that). But no problem of
dependency resolution.
- Xavier
resolve:
> [ivy:retrieve] :: resolving dependencies :: [ apache | ivy |
> working@chamonix ]
> [ivy:retrieve] confs: [default, test]
> [ivy:retrieve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | default | 6 | 0 | 0 | 0 || 0 |
> 0 |
> | test | 1 | 0 | 0 | 0 || 0 |
> 0 |
>
> ---------------------------------------------------------------------
> [ivy:retrieve]
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve] :::: WARNINGS
> [ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve] :: UNRESOLVED DEPENDENCIES ::
> [ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve] :: [ apache | commons-vfs | 20060920 ]: no
> resolver found for [ apache | commons-vfs ]: check your configuration
> [ivy:retrieve] :: [ apache | oro | 2.0.8 ]: no resolver found
> for [ apache | oro ]: check your configuration
> [ivy:retrieve] :: [ jcraft | jsch | 0.1.25 ]: no resolver found
> for [ jcraft | jsch ]: check your configuration
> [ivy:retrieve] :: [ apache | ant | 1.6.5 ]: no resolver found
> for [ apache | ant ]: check your configuration
> [ivy:retrieve] :: [ junit | junit | 3.8.2 ]: no resolver found
> for [ junit | junit ]: check your configuration
> [ivy:retrieve] :: [ apache | commons-cli | 1.0 ]: no resolver
> found for [ apache | commons-cli ]: check your configuration
> [ivy:retrieve] :: [ apache | commons-httpclient | 3.0 ]: no
> resolver found for [ apache | commons-httpclient ]: check your
> configuration
> [ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve] :::: ERRORS
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | ant ]: check your
> configuration[ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | commons-httpclient ]:
> check your configuration
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | commons-cli ]: check
> your configuration
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | oro ]: check your
> configuration[ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ apache | commons-vfs ]: check
> your configuration
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ jcraft | jsch ]: check your
> configuration
> [ivy:retrieve] unknown resolver null
> [ivy:retrieve] no resolver found for [ junit | junit ]: check your
> configuration
> [ivy:retrieve]
> [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>
> BUILD FAILED - at 22/03/07 14:56
> /home/slo/Java/Apache/ivy/build.xml:118: impossible to resolve
> dependencies: resolve failed - see output for details
>
>
>
Re: Release todo list
Posted by Steve Loughran <st...@apache.org>.
Xavier Hanin wrote:
>
> These three things should already be straightforward to get:
> $ svn co https://svn.apache.org/repos/asf/incubator/ivy/core/trunk ivy
> $ cd ivy
> $ ant release
> This generates the same kinf of files as those available here:
> http://incubator.apache.org/ivy/downloads/latest/
>
> I'll need to check if building is still ok with the source distrib. And I
> don't know if the packaging used is ok.
it does not like me
resolve:
[ivy:retrieve] :: resolving dependencies :: [ apache | ivy |
working@chamonix ]
[ivy:retrieve] confs: [default, test]
[ivy:retrieve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| default | 6 | 0 | 0 | 0 || 0 |
0 |
| test | 1 | 0 | 0 | 0 || 0 |
0 |
---------------------------------------------------------------------
[ivy:retrieve]
[ivy:retrieve] :: problems summary ::
[ivy:retrieve] :::: WARNINGS
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :: UNRESOLVED DEPENDENCIES ::
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :: [ apache | commons-vfs | 20060920 ]: no
resolver found for [ apache | commons-vfs ]: check your configuration
[ivy:retrieve] :: [ apache | oro | 2.0.8 ]: no resolver found
for [ apache | oro ]: check your configuration
[ivy:retrieve] :: [ jcraft | jsch | 0.1.25 ]: no resolver found
for [ jcraft | jsch ]: check your configuration
[ivy:retrieve] :: [ apache | ant | 1.6.5 ]: no resolver found
for [ apache | ant ]: check your configuration
[ivy:retrieve] :: [ junit | junit | 3.8.2 ]: no resolver found
for [ junit | junit ]: check your configuration
[ivy:retrieve] :: [ apache | commons-cli | 1.0 ]: no resolver
found for [ apache | commons-cli ]: check your configuration
[ivy:retrieve] :: [ apache | commons-httpclient | 3.0 ]: no
resolver found for [ apache | commons-httpclient ]: check your configuration
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :::: ERRORS
[ivy:retrieve] unknown resolver null
[ivy:retrieve] no resolver found for [ apache | ant ]: check your
configuration[ivy:retrieve] unknown resolver null
[ivy:retrieve] no resolver found for [ apache | commons-httpclient ]:
check your configuration
[ivy:retrieve] unknown resolver null
[ivy:retrieve] no resolver found for [ apache | commons-cli ]: check
your configuration
[ivy:retrieve] unknown resolver null
[ivy:retrieve] no resolver found for [ apache | oro ]: check your
configuration[ivy:retrieve] unknown resolver null
[ivy:retrieve] no resolver found for [ apache | commons-vfs ]: check
your configuration
[ivy:retrieve] unknown resolver null
[ivy:retrieve] no resolver found for [ jcraft | jsch ]: check your
configuration
[ivy:retrieve] unknown resolver null
[ivy:retrieve] no resolver found for [ junit | junit ]: check your
configuration
[ivy:retrieve]
[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
BUILD FAILED - at 22/03/07 14:56
/home/slo/Java/Apache/ivy/build.xml:118: impossible to resolve
dependencies: resolve failed - see output for details
Re: Release todo list
Posted by Xavier Hanin <xa...@gmail.com>.
On 3/22/07, Steve Loughran <st...@apache.org> wrote:
>
> Xavier Hanin wrote:
> > On 3/20/07, Stefan Bodewig <bo...@apache.org> wrote:
> >>
> >> On Wed, 14 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
> >>
> >> > I think it would be a good thing to produce a first incubating
> >> > version of Ivy early April, and I would like to check what we need
> >> > to do, and who does what.
> >>
> >> We have a pretty detailed step by step guide at Ant[1] that show how
> >> we do it over there. In general the exact process of doing a release
> >> is different between ASF projects but there are a few things that are
> >> common:
> >>
> >> * the distribution must only contain stuff we are allowed to
> >> distribute
> >
> > I think this is ok. For external dependencies, I think they are all ok
> > since
> > either from Apache, or used by other Apache projects. We also have a
> > dependency on xooki for the documentation, which is released under ASL
> v2.
> > There is also one class largely inspired by a Maven class, but I think
> this
> > is not a problem. Xooki itself has some piece of codes inspired by
> > tiddlywiki (BSD) and dojo ( Academic Free
> > License<http://opensource.org/licenses/afl-2.1.php>
> > v2.1)
>
>
> Is xooki distributed? or just depended on to create the distros?
For the moment xooki is only an in browser solution, so you need xooki to
browse the doc. This is likely to change in the future since it causes some
problems (bad accessibility and bad compatibility with web crawlers for the
online version), but right now we'll need to distribute it together with the
doc. Is it a problem?
>
> > * all LICENSE and NOTICE files are in place (this also means inside
> >> the JAR file in the case of binary distributions), all project files
> >> contain the license headers
> >
> >
> > I think I see what to do for LICENSE and NOTICE, but I'm not sure for
> > license headers. All java source files have the proper license header.
> But
> > should all xml files, including files used for unit tests and examples,
> > include the header? What about properties files? HTML files from the
> > documentation?
> >
> > * the distribution files are signed with a valid PGP key.
> >>
> >> Sidenote: make sure to catch Steve and myself (don't know whether
> >> any other Ant people will be around) as well as any other Apache
> >> people you will meet in Amsterdam and make sure we sign the key you
> >> intend to use for the final release. There probably will be a
> >> keysigning event at ApacheCon.
> >
> >
> > Does it mean this step is necessary before I can release a first alpha
> or
> > beta version? Because I would like to try to release it before
> ApacheCon.
>
> As Jan said, we can do that together. if you look at the full apache
> release rules (where are they, BTW?), the PMC members are meant to
> verify that that the built artifacts are what they say they are, which
> may include rebuilding the files and comparing checksums on the
> individual .class files in the JAR. This is there to catch malicious
> build managers putting in back doors.
>
> So >1 person should be building the file anyway...any of the people who
> are in the apache trustweb can sign the release.
Ok, I didn't know that, I see that security is a major concern for Apache,
it's a good thing.
> * before the distribution files can be copied to the distribution area
> >> you need at least 3 +1s from PMC members and more +1s than -1s.
> >>
> >> * people will vote on the distribution files, so prepare what you want
> >> to release before calling for a vote.
> >
> >
> > Ok, so I'll first commit the required files (NOTICE, LICENSE,
> DISCLAIMER,
> > and a release guide) to see if things seems ok, then I'll prepare a
> release
> > and put it in my user space on the apache web site to ease evaluation
> and
> > start the vote, first on this list, then if it's ok on the
> > general@i.a.c. Is
> > it a correct way to proceed?
>
> I should subscribe to general@incubator, shouldn't I?
I think so, as a mentor and member of the incubator PMC. But I'm certainly
not the best person to give recomentation on that subject :-)
>
> >> So I would like to know what do we need to do to make such a
> >> > release. What is the process of releasing software in the incubator?
> >>
> >> It is not too different from the "normal" way of making a release
> >> AFAIU[2]. Your mentors are supposed to be Incubator PMC members, so
> our
> >> +1s should be enough to ensure the quorum.
> >>
> >> > Who can perform the remaining tasks?
> >>
> >> In theory anybody can be the release manager, being a committer
> >> certainly simplifies things 8-)
> >
> >
> > Ok, I'll take this task, unless somebody else want to take it.
>
> Well volunteered :)
>
> I may be able to add the ivy build to the bamboo build of smartfrog
> we're setting up here, though its probably better as a public CI server.
> Hmm. Maybe I could set it up at home, too.
This would be nice, a more real time feedback than gump would be nice, and
being able to use generated artifacts as with our prior cruisecontrol setup
at jayasoft.
What is needed at the end of the day is
> -the JAR file
> -the docs for offline use, maybe some examples.
> -a source distribution that people can use to build the JAR file. If
> it doesnt work, you don't get contributions back.
These three things should already be straightforward to get:
$ svn co https://svn.apache.org/repos/asf/incubator/ivy/core/trunk ivy
$ cd ivy
$ ant release
This generates the same kinf of files as those available here:
http://incubator.apache.org/ivy/downloads/latest/
I'll need to check if building is still ok with the source distrib. And I
don't know if the packaging used is ok.
-the right headers on all the source files. Checkstyle can audit the
> code for this.
As I said before, I don't exactly know what should be considered source
files. Java files already have the good header (I think), but what about xml
files and the like.
About checkstyles, maybe we could include the check as part of Ivy build. Is
there an easy to use checkstyle rule for that?
-a release announcement PGP-signed by someone other apache people trust.
I can write the release announcement even if my english is far from
perfect, but I'll need a volunteer for signing.
Other than that, the release guidelines are just that, guidelines.
>
> For ant, we set up a wiki page of what has to be done...here is the
> ant1.7 one:
> http://wiki.apache.org/ant/Ant17/Planning
>
> That's probably the first step...create a (draft) plan.
That sounds like a good idea, I'll create a draft page on the wiki.
For the rest, well, I like to view the alpha release as a way of testing
> the release process.
Exactly, that's my view too. And it will also help people see that we are
making progress in our incubation process.
- Xavier
You can do tricks like unzip/untar the redist
> artifacts, then do a build of that project (pointing it away from the
> normal ivy cache dirs), to check that your source redist is cleanly
> buildable, and run checkstyle against the source to look for licensing
> problems.
>
> -steve
>
Re: Release todo list
Posted by Steve Loughran <st...@apache.org>.
Xavier Hanin wrote:
> On 3/20/07, Stefan Bodewig <bo...@apache.org> wrote:
>>
>> On Wed, 14 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
>>
>> > I think it would be a good thing to produce a first incubating
>> > version of Ivy early April, and I would like to check what we need
>> > to do, and who does what.
>>
>> We have a pretty detailed step by step guide at Ant[1] that show how
>> we do it over there. In general the exact process of doing a release
>> is different between ASF projects but there are a few things that are
>> common:
>>
>> * the distribution must only contain stuff we are allowed to
>> distribute
>
> I think this is ok. For external dependencies, I think they are all ok
> since
> either from Apache, or used by other Apache projects. We also have a
> dependency on xooki for the documentation, which is released under ASL v2.
> There is also one class largely inspired by a Maven class, but I think this
> is not a problem. Xooki itself has some piece of codes inspired by
> tiddlywiki (BSD) and dojo ( Academic Free
> License<http://opensource.org/licenses/afl-2.1.php>
> v2.1)
Is xooki distributed? or just depended on to create the distros?
>
> * all LICENSE and NOTICE files are in place (this also means inside
>> the JAR file in the case of binary distributions), all project files
>> contain the license headers
>
>
> I think I see what to do for LICENSE and NOTICE, but I'm not sure for
> license headers. All java source files have the proper license header. But
> should all xml files, including files used for unit tests and examples,
> include the header? What about properties files? HTML files from the
> documentation?
>
> * the distribution files are signed with a valid PGP key.
>>
>> Sidenote: make sure to catch Steve and myself (don't know whether
>> any other Ant people will be around) as well as any other Apache
>> people you will meet in Amsterdam and make sure we sign the key you
>> intend to use for the final release. There probably will be a
>> keysigning event at ApacheCon.
>
>
> Does it mean this step is necessary before I can release a first alpha or
> beta version? Because I would like to try to release it before ApacheCon.
As Jan said, we can do that together. if you look at the full apache
release rules (where are they, BTW?), the PMC members are meant to
verify that that the built artifacts are what they say they are, which
may include rebuilding the files and comparing checksums on the
individual .class files in the JAR. This is there to catch malicious
build managers putting in back doors.
So >1 person should be building the file anyway...any of the people who
are in the apache trustweb can sign the release.
> * before the distribution files can be copied to the distribution area
>> you need at least 3 +1s from PMC members and more +1s than -1s.
>>
>> * people will vote on the distribution files, so prepare what you want
>> to release before calling for a vote.
>
>
> Ok, so I'll first commit the required files (NOTICE, LICENSE, DISCLAIMER,
> and a release guide) to see if things seems ok, then I'll prepare a release
> and put it in my user space on the apache web site to ease evaluation and
> start the vote, first on this list, then if it's ok on the
> general@i.a.c. Is
> it a correct way to proceed?
I should subscribe to general@incubator, shouldn't I?
>
>> So I would like to know what do we need to do to make such a
>> > release. What is the process of releasing software in the incubator?
>>
>> It is not too different from the "normal" way of making a release
>> AFAIU[2]. Your mentors are supposed to be Incubator PMC members, so our
>> +1s should be enough to ensure the quorum.
>>
>> > Who can perform the remaining tasks?
>>
>> In theory anybody can be the release manager, being a committer
>> certainly simplifies things 8-)
>
>
> Ok, I'll take this task, unless somebody else want to take it.
Well volunteered :)
I may be able to add the ivy build to the bamboo build of smartfrog
we're setting up here, though its probably better as a public CI server.
Hmm. Maybe I could set it up at home, too.
What is needed at the end of the day is
-the JAR file
-the docs for offline use, maybe some examples.
-a source distribution that people can use to build the JAR file. If
it doesnt work, you don't get contributions back.
-the right headers on all the source files. Checkstyle can audit the
code for this.
-a release announcement PGP-signed by someone other apache people trust.
Other than that, the release guidelines are just that, guidelines.
For ant, we set up a wiki page of what has to be done...here is the
ant1.7 one:
http://wiki.apache.org/ant/Ant17/Planning
That's probably the first step...create a (draft) plan.
For the rest, well, I like to view the alpha release as a way of testing
the release process. You can do tricks like unzip/untar the redist
artifacts, then do a build of that project (pointing it away from the
normal ivy cache dirs), to check that your source redist is cleanly
buildable, and run checkstyle against the source to look for licensing
problems.
-steve
Re: Release todo list
Posted by Xavier Hanin <xa...@gmail.com>.
On 3/27/07, Stefan Bodewig <bo...@apache.org> wrote:
>
> On Mon, 26 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
>
> > So one question, where can I find the header to use in an html file?
>
> It is exactly the same as in any other file, just hidden in XML
> comments. So it is byte for byte the same you put in an XML file. 8-)
Ok, thanks, I was wondering if it needed to appear on the page or not,
because I checked the UIMA 2.1.0-incubating release to see how an approved
incubator release looks like, and the html doc has no license header in
comments, but seems to show the license on all pages content. I know their
doc is generated, but I was wondering if it was a requirement to actually
show the license on the pages. But I prefer adding the license in comments
as you indicate.
- Xavier
<!--
> Licensed to the Apache Software Foundation (ASF) under one or more
> contributor license agreements. See the NOTICE file distributed with
> this work for additional information regarding copyright ownership.
> The ASF licenses this file to You under the Apache License, Version 2.0
> (the "License"); you may not use this file except in compliance with
> the License. You may obtain a copy of the License at
>
> http://www.apache.org/licenses/LICENSE-2.0
>
> Unless required by applicable law or agreed to in writing, software
> distributed under the License is distributed on an "AS IS" BASIS,
> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> See the License for the specific language governing permissions and
> limitations under the License.
> -->
>
> Stefan
>
Re: Release todo list
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 26 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
> So one question, where can I find the header to use in an html file?
It is exactly the same as in any other file, just hidden in XML
comments. So it is byte for byte the same you put in an XML file. 8-)
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
Stefan
Re: Release todo list
Posted by Xavier Hanin <xa...@gmail.com>.
On 3/24/07, Stefan Bodewig <bo...@apache.org> wrote:
>
> On Thu, 22 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
> > On 3/20/07, Stefan Bodewig <bo...@apache.org> wrote:
>
> > * all LICENSE and NOTICE files are in place (this also means inside
> >> the JAR file in the case of binary distributions), all project
> >> files contain the license headers
> >
>
> > HTML files from the documentation?
>
> If they are static content, they need the header. If they are
> generated then the header is optional.
I'm not sure if the doc should be considered generated or not, so I think I
will add the license header to the doc, it doesn't hurt.
So one question, where can I find the header to use in an html file?
- Xavier
> * the distribution files are signed with a valid PGP key.
> >>
> >> Sidenote: make sure to catch Steve and myself (don't know whether
> >> any other Ant people will be around) as well as any other Apache
> >> people you will meet in Amsterdam and make sure we sign the key
> >> you intend to use for the final release. There probably will be
> >> a keysigning event at ApacheCon.
> >
> > Does it mean this step is necessary before I can release a first
> > alpha or beta version? Because I would like to try to release it
> > before ApacheCon.
>
> Signing the distribution is mandatory. Using a key that is signed by
> other ASF people is optional, but certainly a good idea. Just ship
> the alpha release and we'll sign your key in time for the final
> release.
>
> Stefan
>
Re: Release todo list
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 22 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
> On 3/20/07, Stefan Bodewig <bo...@apache.org> wrote:
> * all non-project contents of the distribution must be properly
>> attributed
>
> This means we need to provide in the NOTICE the attribution of
> dependencies as I've explained earlier, right?
Yes. At least for all dependencies you want to bundle with Ivy.
> * all LICENSE and NOTICE files are in place (this also means inside
>> the JAR file in the case of binary distributions), all project
>> files contain the license headers
>
> I think I see what to do for LICENSE and NOTICE, but I'm not sure
> for license headers. All java source files have the proper license
> header.
Good.
> But should all xml files, including files used for unit tests and
> examples, include the header?
Yes.
> What about properties files?
Wouldn't hurt to add the header as well.
> HTML files from the documentation?
If they are static content, they need the header. If they are
generated then the header is optional.
> * the distribution files are signed with a valid PGP key.
>>
>> Sidenote: make sure to catch Steve and myself (don't know whether
>> any other Ant people will be around) as well as any other Apache
>> people you will meet in Amsterdam and make sure we sign the key
>> you intend to use for the final release. There probably will be
>> a keysigning event at ApacheCon.
>
> Does it mean this step is necessary before I can release a first
> alpha or beta version? Because I would like to try to release it
> before ApacheCon.
Signing the distribution is mandatory. Using a key that is signed by
other ASF people is optional, but certainly a good idea. Just ship
the alpha release and we'll sign your key in time for the final
release.
Stefan
Re: Release todo list
Posted by Xavier Hanin <xa...@gmail.com>.
On 3/20/07, Stefan Bodewig <bo...@apache.org> wrote:
>
> On Wed, 14 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
>
> > I think it would be a good thing to produce a first incubating
> > version of Ivy early April, and I would like to check what we need
> > to do, and who does what.
>
> We have a pretty detailed step by step guide at Ant[1] that show how
> we do it over there. In general the exact process of doing a release
> is different between ASF projects but there are a few things that are
> common:
>
> * the distribution must only contain stuff we are allowed to
> distribute
I think this is ok. For external dependencies, I think they are all ok since
either from Apache, or used by other Apache projects. We also have a
dependency on xooki for the documentation, which is released under ASL v2.
There is also one class largely inspired by a Maven class, but I think this
is not a problem. Xooki itself has some piece of codes inspired by
tiddlywiki (BSD) and dojo ( Academic Free
License<http://opensource.org/licenses/afl-2.1.php>
v2.1)
* all non-project contents of the distribution must be properly
> attributed
This means we need to provide in the NOTICE the attribution of dependencies
as I've explained earlier, right?
* all LICENSE and NOTICE files are in place (this also means inside
> the JAR file in the case of binary distributions), all project files
> contain the license headers
I think I see what to do for LICENSE and NOTICE, but I'm not sure for
license headers. All java source files have the proper license header. But
should all xml files, including files used for unit tests and examples,
include the header? What about properties files? HTML files from the
documentation?
* the distribution files are signed with a valid PGP key.
>
> Sidenote: make sure to catch Steve and myself (don't know whether
> any other Ant people will be around) as well as any other Apache
> people you will meet in Amsterdam and make sure we sign the key you
> intend to use for the final release. There probably will be a
> keysigning event at ApacheCon.
Does it mean this step is necessary before I can release a first alpha or
beta version? Because I would like to try to release it before ApacheCon.
* before the distribution files can be copied to the distribution area
> you need at least 3 +1s from PMC members and more +1s than -1s.
>
> * people will vote on the distribution files, so prepare what you want
> to release before calling for a vote.
Ok, so I'll first commit the required files (NOTICE, LICENSE, DISCLAIMER,
and a release guide) to see if things seems ok, then I'll prepare a release
and put it in my user space on the apache web site to ease evaluation and
start the vote, first on this list, then if it's ok on the general@i.a.c. Is
it a correct way to proceed?
> So I would like to know what do we need to do to make such a
> > release. What is the process of releasing software in the incubator?
>
> It is not too different from the "normal" way of making a release
> AFAIU[2]. Your mentors are supposed to be Incubator PMC members, so our
> +1s should be enough to ensure the quorum.
>
> > Who can perform the remaining tasks?
>
> In theory anybody can be the release manager, being a committer
> certainly simplifies things 8-)
Ok, I'll take this task, unless somebody else want to take it.
Thanks for your time, Stefan,
- Xavier
Stefan
>
> Footnotes:
> [1] http://svn.apache.org/repos/asf/ant/core/trunk/ReleaseInstructions
>
> [2] http://incubator.apache.org/guides/releasemanagement.html
>
>
Re: Release todo list
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 14 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
> I think it would be a good thing to produce a first incubating
> version of Ivy early April, and I would like to check what we need
> to do, and who does what.
We have a pretty detailed step by step guide at Ant[1] that show how
we do it over there. In general the exact process of doing a release
is different between ASF projects but there are a few things that are
common:
* the distribution must only contain stuff we are allowed to
distribute
* all non-project contents of the distribution must be properly
attributed
* all LICENSE and NOTICE files are in place (this also means inside
the JAR file in the case of binary distributions), all project files
contain the license headers
* the distribution files are signed with a valid PGP key.
Sidenote: make sure to catch Steve and myself (don't know whether
any other Ant people will be around) as well as any other Apache
people you will meet in Amsterdam and make sure we sign the key you
intend to use for the final release. There probably will be a
keysigning event at ApacheCon.
* before the distribution files can be copied to the distribution area
you need at least 3 +1s from PMC members and more +1s than -1s.
* people will vote on the distribution files, so prepare what you want
to release before calling for a vote.
> So I would like to know what do we need to do to make such a
> release. What is the process of releasing software in the incubator?
It is not too different from the "normal" way of making a release
AFAIU[2]. Your mentors are supposed to be Incubator PMC members, so our
+1s should be enough to ensure the quorum.
> Who can perform the remaining tasks?
In theory anybody can be the release manager, being a committer
certainly simplifies things 8-)
Stefan
Footnotes:
[1] http://svn.apache.org/repos/asf/ant/core/trunk/ReleaseInstructions
[2] http://incubator.apache.org/guides/releasemanagement.html