Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of andy.seaborne.apache@gmail.com
 designates 74.125.82.175 as permitted sender)
Received-SPF: pass (google.com: domain of andy.seaborne.apache@gmail.com
 designates 10.216.135.214 as permitted sender) client-ip=10.216.135.214;
Sender: Andy Seaborne <andy.seaborne.apache@gmail.com>
Message-ID: <4F4A52BD.6020808@apache.org>
Date: Sun, 26 Feb 2012 15:41:49 +0000
From: Andy Seaborne <andy@apache.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: general@incubator.apache.org
Subject: Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
References: <4F46605E.9000305@apache.org>
 <CAOGo0VaNQSRQ+-M4d+dY67-6xoR2Ryx2Zh96eVFt+RyuNNEpRQ@mail.gmail.com>
 <4F46A540.6060300@apache.org>
 <CAOGo0VaYxLcKQjDu+W5EjVcPax_oX5mKuO9QQ_0B5Ox7sw4TTg@mail.gmail.com>
 <4F477E7B.5040505@apache.org>
 <CAOGo0VYsDDbkb=jxVTO84jXsuiFqque=T+G-o93UG1C7vmtZcA@mail.gmail.com>
 <4F48089B.7080904@apache.org>
 <CAOGo0VaXEfFR3oSAjcmFFdj3zX_07GBS8McX4eSW4pJHbpAztA@mail.gmail.com>
In-Reply-To: 
 <CAOGo0VaXEfFR3oSAjcmFFdj3zX_07GBS8McX4eSW4pJHbpAztA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

sebb,

What I'm trying to get to at the moment is something that enables a 
release of TDB and we can apply to next module.

jena is a number of modules, we have released 3 (5 actually - 2 are the 
parent POM and the distribution maker for the core) already; TDB is the 
sixth, and there are 3 more in the pipeline.

People have been asking for more packaging forms - WAR file for the 
server functionality, OSGi for Jena as a whole, which seems to be a 
non-trivial exercise.

One of the ones to come is not a simple jar build - it's a server that 
can used as a jar, as a combined dependencies jar or run from the 
command line.  I'm trying to understand the constraints required so that 
will be smooth(er).

We are discussing rebuilding our build strategy but doing so, and to get 
it working reliably and stably will take time.  We chose to release with 
what we have, and not let reworking the build system become critical 
path for graduation.

 >> The apache-jena-tdb... is then merely being a renamed file for browsing
 >> apache-jena-tdb-0.9.0-incubating-distribution.zip
 >>
 >> (c.f. Ant which has renamed items in it dist/ant)

I referred to Ant specifically because the incubator documentation for 
podling releases picks ant and httpd out as examples to look at.

ant has top level items for easy discovery which are renamed duplicates 
of things in binaries/

 >> `-- source-release
 >>     `-- jena-tdb-0.9.0-incubating
 >
 > What's the point of the subdirectory?

because there are other modules with their own source-release artifact. 
  The TDB release items will be merged into the existing directory.

We had been following a layout like CXF where source-release and 
binaries are in the same directory.  Given that is where a the 
maven-driven process puts them, someone taking the source releease 
doing "mvn package" is going to look in target/ and expect created items 
to be there.

That was the RC-2 proposal for dist for TDB.  If, as seems necessary, we 
have to adopt a different layout, we'll reorganise the existing release 
items into the same structure.

>> Would a structure:
>>
>> dist
>> |-- binaries
>> |   `-- jena-tdb-0.9.0-incubating
>> |       |-- jena-tdb-0.9.0-incubating-distribution.tar.gz
>> |       |-- jena-tdb-0.9.0-incubating-distribution.zip
>> |       |-- jena-tdb-0.9.0-incubating-javadoc.jar
>> |       |-- jena-tdb-0.9.0-incubating-sources.jar
>> |       |-- jena-tdb-0.9.0-incubating.jar
>
> The jars are not generally needed for dist/
>
>> |-- download
>> |   |-- apache-jena-tdb-0.9.0-incubating-distribution.tar.gz
>> |   |-- apache-jena-tdb-0.9.0-incubating-distribution.zip
>
> Are these the same as the distribution archives above?
>
>> `-- source-release
>>     `-- jena-tdb-0.9.0-incubating
>
> What's the point of the subdirectory?
>
>>         |-- jena-tdb-0.9.0-incubating-source-release.zip
>
> Name does not agree with binary archives
>
>> + the .asc, .md5 .sha1 files
>>
>> be acceptable?
>>
>> Or with "download/" removed its files at the top level?
>
> I still find it very confusing.
> e.g. where is the source file for jena-tdb-0.9.0-incubating-distribution.tar.gz?

jena-tdb-0.9.0-incubating-source-release.zip

Given the way maven classifiers work, it is a reasonable expectation of 
the user to find the various classifier artifacts in target/ after
"mvn package"

> Why is there a download directory and a binaries directory?

Like ant, I pulled out the items which are "download-unpack-go".  The 
dist areas serves several audiences - for (new) users, not necessarily 
experienced maven users, we have the Jena website (we use Apache CMS to 
produce the website, not maven by the way) simply point to download/ 
(mirrored).  Ditto URLs handled out on the web as being the place to go 
to download Jena.

I don't mind if it's download/ or (like ant) at the top level.

	Andy

>> Mocked up at:
>>
>> http://people.apache.org/~andy/dist-tdb-proto/
>>
>
> See my mockups at:
>
> http://people.apache.org/~sebb/dist-tdb-proto/
>
> one - parallel binaries/ and source/
> two - single directory named after the release.
>
> The latter is likely to be easier to manage when moving to svnpubsub.
>
> $ ls -1R
>
> ./one:
> KEYS
> binaries
> source
>
> ./one/binaries:
> apache-jena-tdb-0.9.0-incubating-distribution.tar.gz
> apache-jena-tdb-0.9.0-incubating-distribution.zip
>
> ./one/source:
> apache-jena-tdb-0.9.0-incubating-source-release.zip
>
> ./two:
> KEYS
> apache-jena-tdb-0.9.0-incubating
>
> ./two/apache-jena-tdb-0.9.0-incubating:
> apache-jena-tdb-0.9.0-incubating-distribution.tar.gz
> apache-jena-tdb-0.9.0-incubating-distribution.zip
> apache-jena-tdb-0.9.0-incubating-source-release.zip
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org