I think that looks fine to me.
On Jan 7, 2011, at 7:09 AM, Pid wrote: > Hi, > > I aim to enhance the current build.xml to produce an archive for our own > testing. (For clarity: I am not suggesting we do a release yet!) > > Does anyone have anything to contribute or strong feelings about what a > release artefact should look like, in terms of directory layout & > contents? E.g. > > Artefacts: > > apache-kitty-0.1-dev-incubating.tar.gz > apache-kitty-0.1-dev-incubating.zip > > Containing: > > kitty.bat > kitty.sh > apache-kitty-0.1-dev-incubating.jar > LICENSE (etc) > ... > lib > groovy-all-1.7.6.jar > ... > src > apache-kitty-src-0.1-dev-incubating.jar > ... > docs > ... > > > If I've understood things correctly, the version string should be: > '0.1-dev-incubating' > > When we have a release: '0.1-incubating'. (The 'incubating' is removed > after graduation.) > > I'm not sure if 'incubating' has to be included in the jars we produce, > or just the distributable archive. A mentor may know? > > > p > > > > > > > <0x62590808.asc>
