You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Andy Seaborne <an...@apache.org> on 2012/02/23 16:50:54 UTC
[VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
The Jena PPMC has voted to release
Apache Jena TDB 0.9.0-incubating
and we would now be grateful if members of IPMC would review and vote
for this release.
== Major changes since RC-2
+ Distribution has it's own content for NOTICE/LICENSE files which
rolls up information for the redistributed binaries.
+ jar file META-INF/NOTICE says "Apache Jena - module TDB" at the top.
+ source-release.zip does not contain a trunk/ copy.
+ New dist/ layout
The existing released files will need to moved to this layout.
The KEYS file is copied into the proposed dist/ area for clarity.
== Project vote
Result:
http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201202.mbox/%3C4F4614CB.9010802%40apache.org%3E
including 1 IPMC vote (Benson Margulies)
Call for VOTE:
http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201202.mbox/%3C4F40CE69.2080402%40apache.org%3E
The following was noted in the jena-dev RC-4 vote:
* The license information for Plugged-In software is in the distribution
LICENSE file twice.
== Staging repository
https://repository.apache.org/content/repositories/orgapachejena-001/
Direct link to TDB area in staging:
http://s.apache.org/vcp
== Proposed dist/ area:
The following will be added to the existing distribution area:
http://people.apache.org/~andy/dist-jena-tdb-0.9.0-incubating-RC-4/
will be added to:
http://www.apache.org/dist/incubator/jena/
Note: we will reorganise the current dist/ area to fit into this style
of layout.
== Keys
https://svn.apache.org/repos/asf/incubator/jena/dist/KEYS
== SVN tag
The module is currently tagged with the version and "-RC-4". If voted
on successfully, the tag will be changed ("svn mv") to the same but
minus the "RC" labelling.
https://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/tags/jena-tdb-0.9.0-incubating-RC-4/
Please vote on this release:
[ ] +1 Approve the release of Apache Jena, module TDB 0.9.0-incubating
[ ] -1 Don't release, because ...
This vote will be open until:
Sunday 26/February 23:59 UTC
(72 hours from the same hour tonight).
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] [ended] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Andy Seaborne <an...@apache.org>.
Currently, this vote has 2 +1 and some comments. This release vote
isn't going to get the necessary 3 +1's so is being closed. We'll be
back with another RC.
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Leo Simons <ma...@leosimons.com>.
On Thu, Feb 23, 2012 at 4:50 PM, Andy Seaborne <an...@apache.org> wrote:
> The Jena PPMC has voted to release
>
> Apache Jena TDB 0.9.0-incubating
>
> and we would now be grateful if members of IPMC would review and vote for
> this release.
+1 from me.
(justification:
1) I do not consider unintuitive file name and directory layout
conventions blockers for release; I think this thread shows
"unintuitive" is subjective anyway. I pointed the deviations out
before on jena-dev, and then folks obviously thought about this and
decided to do things differently from a lot of other projects. Even if
the chosen convention is wacky that does not make it wrong.
2) Whilst LEGAL-124 remains unresolved there's plenty of precedent for
not having license headers in test data and similar auxiliary files,
all around apache, and so I consider it fine to continue current
standard practice until different rules arrive.
3) all looks good to me ;-)
)
cheers,
Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Ralph Goers <ra...@dslextreme.com>.
Rats - please ignore my vote. I accidentally +1'd the wrong thread.
Ralph
On Feb 24, 2012, at 3:47 PM, Ralph Goers wrote:
> +1 (binding)
>
> Ralph
>
> On Feb 24, 2012, at 2:00 PM, Andy Seaborne wrote:
>
>> On 24/02/12 14:04, sebb wrote:
>>>> The directory structures align:
>>>>
>>>> /download/jena-tdb-0.9.0-incubating
>>>> /source-release/jena-tdb-0.9.0-incubating
>>>
>>> I see the following files (amongst others) in the RC area
>>> http://people.apache.org/~andy/dist-jena-tdb-0.9.0-incubating-RC-4/
>>>
>>> KEYS
>>> download/apache-jena-tdb-0.9.0-incubating.zip
>>> download//jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating.jar
>>> source-release/jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating-source-release.zip
>>>
>>> Note that the source release is in
>>> source-release/jena-tdb-0.9.0-incubating/
>>> whereas the corresponding binary release is in
>>> download/
>>> i.e. different depths - and they have different names.
>>>
>>> [I'm discounting the jar, since that is Maven-specific and is not
>>> needed on the dist/ mirror site.]
>>
>> I see the confusion now - the main product of the codebase is the core jena-tdb-0.9.0-incubating.jar with
>> apache-jena-tdb-0.9.0-incubating-distibution.zip being a subsidiary creation.
>>
>> If there were a file:
>>
>> download/jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating-distribution.zip
>>
>> then it would be aligned with the source-release hierarchy.
>>
>> 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)
>>
>> 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
>> |-- download
>> | |-- apache-jena-tdb-0.9.0-incubating-distribution.tar.gz
>> | |-- apache-jena-tdb-0.9.0-incubating-distribution.zip
>> `-- source-release
>> `-- jena-tdb-0.9.0-incubating
>> |-- jena-tdb-0.9.0-incubating-source-release.zip
>>
>> + the .asc, .md5 .sha1 files
>>
>> be acceptable?
>>
>> Or with "download/" removed its files at the top level?
>>
>> Mocked up at:
>>
>> http://people.apache.org/~andy/dist-tdb-proto/
>>
>> Andy
>>
>> ---------------------------------------------------------------------
>> 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Ralph Goers <ra...@dslextreme.com>.
+1 (binding)
Ralph
On Feb 24, 2012, at 2:00 PM, Andy Seaborne wrote:
> On 24/02/12 14:04, sebb wrote:
>>> The directory structures align:
>>>
>>> /download/jena-tdb-0.9.0-incubating
>>> /source-release/jena-tdb-0.9.0-incubating
>>
>> I see the following files (amongst others) in the RC area
>> http://people.apache.org/~andy/dist-jena-tdb-0.9.0-incubating-RC-4/
>>
>> KEYS
>> download/apache-jena-tdb-0.9.0-incubating.zip
>> download//jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating.jar
>> source-release/jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating-source-release.zip
>>
>> Note that the source release is in
>> source-release/jena-tdb-0.9.0-incubating/
>> whereas the corresponding binary release is in
>> download/
>> i.e. different depths - and they have different names.
>>
>> [I'm discounting the jar, since that is Maven-specific and is not
>> needed on the dist/ mirror site.]
>
> I see the confusion now - the main product of the codebase is the core jena-tdb-0.9.0-incubating.jar with
> apache-jena-tdb-0.9.0-incubating-distibution.zip being a subsidiary creation.
>
> If there were a file:
>
> download/jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating-distribution.zip
>
> then it would be aligned with the source-release hierarchy.
>
> 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)
>
> 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
> |-- download
> | |-- apache-jena-tdb-0.9.0-incubating-distribution.tar.gz
> | |-- apache-jena-tdb-0.9.0-incubating-distribution.zip
> `-- source-release
> `-- jena-tdb-0.9.0-incubating
> |-- jena-tdb-0.9.0-incubating-source-release.zip
>
> + the .asc, .md5 .sha1 files
>
> be acceptable?
>
> Or with "download/" removed its files at the top level?
>
> Mocked up at:
>
> http://people.apache.org/~andy/dist-tdb-proto/
>
> Andy
>
> ---------------------------------------------------------------------
> 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Andy Seaborne <an...@apache.org>.
>>>> `-- 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.
>
> So why don't you do the same for the download directory?
The download/ directory would be for all modules.
But as I said, top level work for me as well. One place where you can
get all the jena-related "unpack-and-go" files.
Is that not possible?
>> We had been following a layout like CXF where source-release and binaries
>> are in the same directory.
>>> I still find it very confusing.
>>> e.g. where is the source file for
>>> jena-tdb-0.9.0-incubating-distribution.tar.gz?
>
> Sorry, that was a mistake - I meant where is the source for the dowload file
>
> apache-jena-tdb-0.9.0-incubating-distribution.tar.gz
As per "ant" example - there is a correctly named and positioned file
and also a copy (and rename) elsewhere.
The specific rename is because, long term, post rework the build, we
think "apache-jena-..." will be the packaged up forms and "jena-..." the
core jars but that isn't really the issue here. A systematically named
file is available.
> What I care about is that it is:
> - more difficult to find the source than some of the binaries, because
> of the extra directory level.
Maybe I don't understand how should we manage multiple modules with
currently have independent version numbers.
The proposal is have:
/sources/jena-arq-2.9.0-incubating/
/sources/jena-core-2.7.0-incubating/
/sources/jena-iri-0.9.0-incubating/
/sources/jena-tdb-0.9.0-incubating/
/binaries/jena-arq-2.9.0-incubating/
/binaries/jena-core-2.7.0-incubating/
/binaries/jena-iri-0.9.0-incubating/
/binaries/jena-tdb-0.9.0-incubating/
Is this better?
/jena-arq-2.9.0-incubating/sources/
/jena-arq-2.9.0-incubating/binaries/
/jena-core-2.7.0-incubating/sources/
/jena-core-2.7.0-incubating/binaries/
/jena-iri-0.9.0-incubating/sources/
/jena-iri-0.9.0-incubating/binaries/
/jena-tdb-0.9.0-incubating/sources/
/jena-tdb-0.9.0-incubating/binaries/
Can we put "easy to find" files in "/"?
> - not at all clear how to find the source for some of the binaries, as
> it is at a different level and with a different name.
/sources/jena-tdb-0.9.0-incubating/jena-tdb-VER(-classifier)?
/binaries/jena-tdb-0.9.0-incubating/jena-tdb-VER-source-release
are at the same level.
We did have a form like "sling" uses, split per module.
> - binaries are available as tar.gz and zip, but source only as zip
Sorry - I thought I'd answered this earlier. We use org.apache:apache
which comes down to this (in assemblies/source-release.xml) which just
makes a zip.
<assembly>
<id>source-release</id>
<formats>
<format>zip</format>
</formats>
<componentDescriptors>
<componentDescriptor>assemblies/source-shared.xml</componentDescriptor>
</componentDescriptors>
</assembly>
so we just followed that. It's a tradeoff - reuse unchnaged vs forking it.
For the .jar.gz: we used to ship a zip, which any Java systems must have
access to as jar files are zip archives. Adding .tar.gz was courtesy
for people wanting files in those forms because it very little work to
help them.
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by sebb <se...@gmail.com>.
On 26 February 2012 15:41, Andy Seaborne <an...@apache.org> wrote:
> 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.
So why don't you do the same for the download 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?
Sorry, that was a mistake - I meant where is the source for the dowload file
apache-jena-tdb-0.9.0-incubating-distribution.tar.gz
>
>
> jena-tdb-0.9.0-incubating-source-release.zip
Not only is the name different, but also the archive type is different.
That is very confusing.
> 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"
Yes, but what has Maven to do with the self-contained release archives?
>
>> 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.
There should be no need to have Maven jars in the dist/ structure.
I think this is just confusing to end-users.
> I don't mind if it's download/ or (like ant) at the top level.
What I care about is that it is:
- more difficult to find the source than some of the binaries, because
of the extra directory level.
- not at all clear how to find the source for some of the binaries, as
it is at a different level and with a different name.
- binaries are available as tar.gz and zip, but source only as zip
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Andy Seaborne <an...@apache.org>.
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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by sebb <se...@gmail.com>.
On 24 February 2012 22:00, Andy Seaborne <an...@apache.org> wrote:
> On 24/02/12 14:04, sebb wrote:
>>>
>>> The directory structures align:
>>>
>>> /download/jena-tdb-0.9.0-incubating
>>> /source-release/jena-tdb-0.9.0-incubating
>>
>>
>> I see the following files (amongst others) in the RC area
>> http://people.apache.org/~andy/dist-jena-tdb-0.9.0-incubating-RC-4/
>>
>> KEYS
>> download/apache-jena-tdb-0.9.0-incubating.zip
>> download//jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating.jar
>>
>> source-release/jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating-source-release.zip
>>
>> Note that the source release is in
>> source-release/jena-tdb-0.9.0-incubating/
>> whereas the corresponding binary release is in
>> download/
>> i.e. different depths - and they have different names.
>>
>> [I'm discounting the jar, since that is Maven-specific and is not
>> needed on the dist/ mirror site.]
>
>
> I see the confusion now - the main product of the codebase is the core
> jena-tdb-0.9.0-incubating.jar with
> apache-jena-tdb-0.9.0-incubating-distibution.zip being a subsidiary
> creation.
>
> If there were a file:
>
> download/jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating-distribution.zip
>
> then it would be aligned with the source-release hierarchy.
>
> 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)
>
> 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?
Why is there a download directory and a binaries directory?
> 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Andy Seaborne <an...@apache.org>.
On 24/02/12 14:04, sebb wrote:
>> The directory structures align:
>>
>> /download/jena-tdb-0.9.0-incubating
>> /source-release/jena-tdb-0.9.0-incubating
>
> I see the following files (amongst others) in the RC area
> http://people.apache.org/~andy/dist-jena-tdb-0.9.0-incubating-RC-4/
>
> KEYS
> download/apache-jena-tdb-0.9.0-incubating.zip
> download//jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating.jar
> source-release/jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating-source-release.zip
>
> Note that the source release is in
> source-release/jena-tdb-0.9.0-incubating/
> whereas the corresponding binary release is in
> download/
> i.e. different depths - and they have different names.
>
> [I'm discounting the jar, since that is Maven-specific and is not
> needed on the dist/ mirror site.]
I see the confusion now - the main product of the codebase is the core
jena-tdb-0.9.0-incubating.jar with
apache-jena-tdb-0.9.0-incubating-distibution.zip being a subsidiary
creation.
If there were a file:
download/jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating-distribution.zip
then it would be aligned with the source-release hierarchy.
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)
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
|-- download
| |-- apache-jena-tdb-0.9.0-incubating-distribution.tar.gz
| |-- apache-jena-tdb-0.9.0-incubating-distribution.zip
`-- source-release
`-- jena-tdb-0.9.0-incubating
|-- jena-tdb-0.9.0-incubating-source-release.zip
+ the .asc, .md5 .sha1 files
be acceptable?
Or with "download/" removed its files at the top level?
Mocked up at:
http://people.apache.org/~andy/dist-tdb-proto/
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by sebb <se...@gmail.com>.
On 24 February 2012 12:11, Andy Seaborne <an...@apache.org> wrote:
>
>>> We distribute through maven but also many of our users are not
>>> experienced
>>> developers but students, including ones new to java.
>>>
>>> To make it as easy as possible for this category of user, we ship a
>>> distribution which is the collection of jars needed for use without a
>>> maven/ivy infrastructure.
>>
>>
>> That's fine, so long as the N&L files agree with the contents.
>
>
> They should do.
>
>
>>> This is created in the maven target/ area - and it is then renamed into
>>> the
>>> dist/ area as apache-jena* by the distribution build script. Maven
>>> forces
>>> the name to be jena-tdb-.... on staging whatever assembly root name is
>>> given.
>>
>>
>> Again that's OK, but the layout of the dist area - and the naming
>> convention - is very confusing.
>>
>> There is no direct correspondance between the binary and source archives.
>> It should be immediately obvious how to find the source and
>> corresponding binary, but that's not the case at present.
>
>
> The directory structures align:
>
> /download/jena-tdb-0.9.0-incubating
> /source-release/jena-tdb-0.9.0-incubating
I see the following files (amongst others) in the RC area
http://people.apache.org/~andy/dist-jena-tdb-0.9.0-incubating-RC-4/
KEYS
download/apache-jena-tdb-0.9.0-incubating.zip
download//jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating.jar
source-release/jena-tdb-0.9.0-incubating/jena-tdb-0.9.0-incubating-source-release.zip
Note that the source release is in
source-release/jena-tdb-0.9.0-incubating/
whereas the corresponding binary release is in
download/
i.e. different depths - and they have different names.
[I'm discounting the jar, since that is Maven-specific and is not
needed on the dist/ mirror site.]
> but since this isn't "/binaries" and "/sources" we'll build about RC - we'll
> be back in a week to 10 day I hope.
Does not have to be binaries and source (sic), so long as the source
and binary archives are directly related.
They have different names at present, which makes it difficult to tie
them together.
Also, the convention is to have the source and binary archives:
- in the same directory, or
- in parallel directories (binaries/source)
In the case of OS-specific binaries, these could be in folders such as
binaries/plan9
binaries/windows
etc.
In such cases, the binary archives would be one level lower than the
source archive, but that is easy to follow.
>
>> The scripts can all have AL headers; there are some XML files as well
>> that could have them.
>
>
> I will put either short or full AL headers on the scripts.
>
> find . -name \*xml | xargs grep -L "Licensed to the Apache Software
> Foundation" | xargs wc -l
>
> 39 ./testing/Deployment/pom.xml
> 8 ./src/main/java/com/hp/hpl/jena/tdb/tdb-properties.xml
> 8 ./src/main/resources/org/apache/jena/tdb/tdb-properties.xml
> 55 total
>
> and tdb-properies.xml has 2 Java properties.
>
> Andy
>
>
>> There is one Java file that has no AL header.
>>
>>> 12 are NOTICE/LICENSE/DEPENDENCIES etc.
>>
>>
>> These are OK
>>
>>> and then there setting and eclipse files that you have commented on
>>> before.
>>>
>>> (aside: we tried autogenerating Eclipse files following previous comments
>>> but encountered problems with eclipse:eclipse which we are investigating)
>>
>>
>> No need to autogenerate; just don't store them with the default names or
>> paths.
>>
>> Perhaps store them under a resources/eclipse directory.
>>
>>>
>>> Andy
>
>
> ---------------------------------------------------------------------
> 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Andy Seaborne <an...@apache.org>.
>> We distribute through maven but also many of our users are not experienced
>> developers but students, including ones new to java.
>>
>> To make it as easy as possible for this category of user, we ship a
>> distribution which is the collection of jars needed for use without a
>> maven/ivy infrastructure.
>
> That's fine, so long as the N&L files agree with the contents.
They should do.
>> This is created in the maven target/ area - and it is then renamed into the
>> dist/ area as apache-jena* by the distribution build script. Maven forces
>> the name to be jena-tdb-.... on staging whatever assembly root name is
>> given.
>
> Again that's OK, but the layout of the dist area - and the naming
> convention - is very confusing.
>
> There is no direct correspondance between the binary and source archives.
> It should be immediately obvious how to find the source and
> corresponding binary, but that's not the case at present.
The directory structures align:
/download/jena-tdb-0.9.0-incubating
/source-release/jena-tdb-0.9.0-incubating
but since this isn't "/binaries" and "/sources" we'll build about RC -
we'll be back in a week to 10 day I hope.
> The scripts can all have AL headers; there are some XML files as well
> that could have them.
I will put either short or full AL headers on the scripts.
find . -name \*xml | xargs grep -L "Licensed to the Apache Software
Foundation" | xargs wc -l
39 ./testing/Deployment/pom.xml
8 ./src/main/java/com/hp/hpl/jena/tdb/tdb-properties.xml
8 ./src/main/resources/org/apache/jena/tdb/tdb-properties.xml
55 total
and tdb-properies.xml has 2 Java properties.
Andy
> There is one Java file that has no AL header.
>
>> 12 are NOTICE/LICENSE/DEPENDENCIES etc.
>
> These are OK
>
>> and then there setting and eclipse files that you have commented on before.
>>
>> (aside: we tried autogenerating Eclipse files following previous comments
>> but encountered problems with eclipse:eclipse which we are investigating)
>
> No need to autogenerate; just don't store them with the default names or paths.
>
> Perhaps store them under a resources/eclipse directory.
>
>>
>> Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by sebb <se...@gmail.com>.
On 23 February 2012 20:44, Andy Seaborne <an...@apache.org> wrote:
> On 23/02/12 18:32, sebb wrote:
>
> Hi sebb,
>
> Thanks for the review,
>
>
>>> == Staging repository
>>>
>>> https://repository.apache.org/content/repositories/orgapachejena-001/
>>
>> This contains zip and tar.gz binary and source archives, which should
>> be deleted as they are not useful to Maven.
>
>
> There are two addition classifiers used: source-release and distribution.
>
> To take the file jena-tdb-0.9.0-incubating-source-release.zip specifically,
> this gets there because
>
> mvn release:perform -Papache-release
>
> puts it there. This seems to be the practice elsewhere as well:
>
> e.g.
> https://repository.apache.org/content/repositories/releases/org/apache/sling/org.apache.sling.engine/2.2.4/
>
>
> For "distribution":
>
> We distribute through maven but also many of our users are not experienced
> developers but students, including ones new to java.
>
> To make it as easy as possible for this category of user, we ship a
> distribution which is the collection of jars needed for use without a
> maven/ivy infrastructure.
That's fine, so long as the N&L files agree with the contents.
> This is created in the maven target/ area - and it is then renamed into the
> dist/ area as apache-jena* by the distribution build script. Maven forces
> the name to be jena-tdb-.... on staging whatever assembly root name is
> given.
Again that's OK, but the layout of the dist area - and the naming
convention - is very confusing.
There is no direct correspondance between the binary and source archives.
It should be immediately obvious how to find the source and
corresponding binary, but that's not the case at present.
>
>>> == SVN tag
>>> >
>>> > The module is currently tagged with the version and "-RC-4". If voted
>>> > on
>>> > successfully, the tag will be changed ("svn mv") to the same but minus
>>> > the
>>> > "RC" labelling.
>>> >
>>> >
>>> > https://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/tags/jena-tdb-0.9.0-incubating-RC-4/
>>
>> There are a lot of source files without AL headers.
>> These need to be fixed.
>>
>
> Could you say which ones you mean?
>
> Following the recent discussion on this (LEGAL-124), I thought the
> conclusion was it wasn't necessary on short files with little or no
> creativity or value.
>
> The files in testing/ are short test files - we do put the ASF header on the
> manifests.
>
> e.g:
> https://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/tags/jena-tdb-0.9.0-incubating-RC-4/testing/Pattern/pattern-1.rq
>
> ----
> PREFIX : <http://example/OTHER>
>
> SELECT *
> {
> :NoSuchNode ?p ?z .
> ?x ?p ?z
> }
> ----
> I found
> A total of 118 files that do not contain th line
> "Licensed to the Apache Software Foundation (ASF) under"
>
> 67 under testing/
> 25 are scripts
The scripts can all have AL headers; there are some XML files as well
that could have them.
There is one Java file that has no AL header.
> 12 are NOTICE/LICENSE/DEPENDENCIES etc.
These are OK
> and then there setting and eclipse files that you have commented on before.
>
> (aside: we tried autogenerating Eclipse files following previous comments
> but encountered problems with eclipse:eclipse which we are investigating)
No need to autogenerate; just don't store them with the default names or paths.
Perhaps store them under a resources/eclipse directory.
>
> Andy
>
> ---------------------------------------------------------------------
> 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Andy Seaborne <an...@apache.org>.
On 23/02/12 18:32, sebb wrote:
Hi sebb,
Thanks for the review,
>> == Staging repository
>>
>> https://repository.apache.org/content/repositories/orgapachejena-001/
> This contains zip and tar.gz binary and source archives, which should
> be deleted as they are not useful to Maven.
There are two addition classifiers used: source-release and distribution.
To take the file jena-tdb-0.9.0-incubating-source-release.zip
specifically, this gets there because
mvn release:perform -Papache-release
puts it there. This seems to be the practice elsewhere as well:
e.g.
https://repository.apache.org/content/repositories/releases/org/apache/sling/org.apache.sling.engine/2.2.4/
For "distribution":
We distribute through maven but also many of our users are not
experienced developers but students, including ones new to java.
To make it as easy as possible for this category of user, we ship a
distribution which is the collection of jars needed for use without a
maven/ivy infrastructure.
This is created in the maven target/ area - and it is then renamed into
the dist/ area as apache-jena* by the distribution build script. Maven
forces the name to be jena-tdb-.... on staging whatever assembly root
name is given.
I seem to have missed some document somewhere - what is the correct way
to handle this? Pointer?
>> == SVN tag
>> >
>> > The module is currently tagged with the version and "-RC-4". If voted on
>> > successfully, the tag will be changed ("svn mv") to the same but minus the
>> > "RC" labelling.
>> >
>> > https://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/tags/jena-tdb-0.9.0-incubating-RC-4/
> There are a lot of source files without AL headers.
> These need to be fixed.
>
Could you say which ones you mean?
Following the recent discussion on this (LEGAL-124), I thought the
conclusion was it wasn't necessary on short files with little or no
creativity or value.
The files in testing/ are short test files - we do put the ASF header on
the manifests.
e.g:
https://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/tags/jena-tdb-0.9.0-incubating-RC-4/testing/Pattern/pattern-1.rq
----
PREFIX : <http://example/OTHER>
SELECT *
{
:NoSuchNode ?p ?z .
?x ?p ?z
}
----
I found
A total of 118 files that do not contain th line
"Licensed to the Apache Software Foundation (ASF) under"
67 under testing/
25 are scripts
12 are NOTICE/LICENSE/DEPENDENCIES etc.
and then there setting and eclipse files that you have commented on before.
(aside: we tried autogenerating Eclipse files following previous
comments but encountered problems with eclipse:eclipse which we are
investigating)
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by sebb <se...@gmail.com>.
On 23 February 2012 20:11, Damian Steer <pl...@mac.com> wrote:
>
> On 23 Feb 2012, at 18:32, sebb wrote:
>
>>> == Proposed dist/ area:
>>>
>>> The following will be added to the existing distribution area:
>>>
>>> http://people.apache.org/~andy/dist-jena-tdb-0.9.0-incubating-RC-4/
>>
>> Where is the source that corresponds to:
>>
>> download/apache-jena-tdb-0.9.0-incubating.zip
>>
>> It's not easy to find.
>>
>> And the reverse is just as hard.
>
> I see only one file under source, and it seems to build everything found under dist.
>
>>> https://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/tags/jena-tdb-0.9.0-incubating-RC-4/
>>
>> There are a lot of source files without AL headers.
>> These need to be fixed.
>
> jena-tdb-0.9.0-incubating-RC-4 pldms$ ack -v -l 'Licensed to the Apache Software Foundation' .
> ...
> src-dev/dev/LongTermIssues.java
> ...
>
> Only one source file is missing this (plus a number of configuration files and shell scripts). Am I missing something obvious? (a: probably)
All of those should have AL headers.
> Damian
>
> ---------------------------------------------------------------------
> 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by Damian Steer <pl...@mac.com>.
On 23 Feb 2012, at 18:32, sebb wrote:
>> == Proposed dist/ area:
>>
>> The following will be added to the existing distribution area:
>>
>> http://people.apache.org/~andy/dist-jena-tdb-0.9.0-incubating-RC-4/
>
> Where is the source that corresponds to:
>
> download/apache-jena-tdb-0.9.0-incubating.zip
>
> It's not easy to find.
>
> And the reverse is just as hard.
I see only one file under source, and it seems to build everything found under dist.
>> https://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/tags/jena-tdb-0.9.0-incubating-RC-4/
>
> There are a lot of source files without AL headers.
> These need to be fixed.
jena-tdb-0.9.0-incubating-RC-4 pldms$ ack -v -l 'Licensed to the Apache Software Foundation' .
...
src-dev/dev/LongTermIssues.java
...
Only one source file is missing this (plus a number of configuration files and shell scripts). Am I missing something obvious? (a: probably)
Damian
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by sebb <se...@gmail.com>.
On 23 February 2012 21:21, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hi Sebb,
>
> On Feb 23, 2012, at 1:15 PM, sebb wrote:
>
>>>
>>> Yep, I'm not an expert, but we push tar.gz and .zip distributions in OODT, and
>>> then we have specialized assembly.xml descriptors in downstream OODT components
>>> that depend on the tarballs, and Maven will go and get them remotely.
>>>
>>> Paul Ramirez knows a ton about this in OODT: I've mainly just been a watcher of
>>> his "Maven magic" :) But, I do know they are useful, at least to us in OODT, and
>>> wanted to mention it.
>>
>> Sounds like that is specific to the way OODT does its resolution.
>
> Well not really. It's the Maven assembly plugin and specific to it.
I'm suprised that Maven - which normally handles dependency resolution
very well - should rely on components packaging their dependencies for
downstream components. It should be able to resolve the dependencies
from the pom, and then fetch them directly from the repo, rather than
having to unpack an archive.
But this is getting seriously OT for this thread.
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> ---------------------------------------------------------------------
> 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Sebb,
On Feb 23, 2012, at 1:15 PM, sebb wrote:
>>
>> Yep, I'm not an expert, but we push tar.gz and .zip distributions in OODT, and
>> then we have specialized assembly.xml descriptors in downstream OODT components
>> that depend on the tarballs, and Maven will go and get them remotely.
>>
>> Paul Ramirez knows a ton about this in OODT: I've mainly just been a watcher of
>> his "Maven magic" :) But, I do know they are useful, at least to us in OODT, and
>> wanted to mention it.
>
> Sounds like that is specific to the way OODT does its resolution.
Well not really. It's the Maven assembly plugin and specific to it.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by sebb <se...@gmail.com>.
On 23 February 2012 19:42, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hi Sebb,
>
> On Feb 23, 2012, at 12:13 PM, sebb wrote:
>
>>>
>>> On the contrary, they are plenty useful to Maven. They are used by its
>>> assembly plugin to allow for transitive dependencies and the ability to
>>> unpackage those distros as needed.
>>
>> Huh?
>> Are you sure?
>
> Yep, I'm not an expert, but we push tar.gz and .zip distributions in OODT, and
> then we have specialized assembly.xml descriptors in downstream OODT components
> that depend on the tarballs, and Maven will go and get them remotely.
>
> Paul Ramirez knows a ton about this in OODT: I've mainly just been a watcher of
> his "Maven magic" :) But, I do know they are useful, at least to us in OODT, and
> wanted to mention it.
Sounds like that is specific to the way OODT does its resolution.
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> ---------------------------------------------------------------------
> 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Sebb,
On Feb 23, 2012, at 12:13 PM, sebb wrote:
>>
>> On the contrary, they are plenty useful to Maven. They are used by its
>> assembly plugin to allow for transitive dependencies and the ability to
>> unpackage those distros as needed.
>
> Huh?
> Are you sure?
Yep, I'm not an expert, but we push tar.gz and .zip distributions in OODT, and
then we have specialized assembly.xml descriptors in downstream OODT components
that depend on the tarballs, and Maven will go and get them remotely.
Paul Ramirez knows a ton about this in OODT: I've mainly just been a watcher of
his "Maven magic" :) But, I do know they are useful, at least to us in OODT, and
wanted to mention it.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by sebb <se...@gmail.com>.
On 23 February 2012 18:58, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> On Feb 23, 2012, at 11:32 AM, sebb wrote:
>
>> On 23 February 2012 15:50, Andy Seaborne <an...@apache.org> wrote:
>>> The Jena PPMC has voted to release
>>>
>>> Apache Jena TDB 0.9.0-incubating
>>>
>>> and we would now be grateful if members of IPMC would review and vote for
>>> this release.
>>>
>>> == Major changes since RC-2
>>>
>>> + Distribution has it's own content for NOTICE/LICENSE files which
>>> rolls up information for the redistributed binaries.
>>> + jar file META-INF/NOTICE says "Apache Jena - module TDB" at the top.
>>> + source-release.zip does not contain a trunk/ copy.
>>> + New dist/ layout
>>>
>>> The existing released files will need to moved to this layout.
>>> The KEYS file is copied into the proposed dist/ area for clarity.
>>>
>>> == Project vote
>>>
>>> Result:
>>> http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201202.mbox/%3C4F4614CB.9010802%40apache.org%3E
>>>
>>> including 1 IPMC vote (Benson Margulies)
>>>
>>> Call for VOTE:
>>> http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201202.mbox/%3C4F40CE69.2080402%40apache.org%3E
>>>
>>> The following was noted in the jena-dev RC-4 vote:
>>>
>>> * The license information for Plugged-In software is in the distribution
>>> LICENSE file twice.
>>>
>>> == Staging repository
>>>
>>> https://repository.apache.org/content/repositories/orgapachejena-001/
>>
>> This contains zip and tar.gz binary and source archives, which should
>> be deleted as they are not useful to Maven.
>
> On the contrary, they are plenty useful to Maven. They are used by its
> assembly plugin to allow for transitive dependencies and the ability to
> unpackage those distros as needed.
Huh?
Are you sure?
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> ---------------------------------------------------------------------
> 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
On Feb 23, 2012, at 11:32 AM, sebb wrote:
> On 23 February 2012 15:50, Andy Seaborne <an...@apache.org> wrote:
>> The Jena PPMC has voted to release
>>
>> Apache Jena TDB 0.9.0-incubating
>>
>> and we would now be grateful if members of IPMC would review and vote for
>> this release.
>>
>> == Major changes since RC-2
>>
>> + Distribution has it's own content for NOTICE/LICENSE files which
>> rolls up information for the redistributed binaries.
>> + jar file META-INF/NOTICE says "Apache Jena - module TDB" at the top.
>> + source-release.zip does not contain a trunk/ copy.
>> + New dist/ layout
>>
>> The existing released files will need to moved to this layout.
>> The KEYS file is copied into the proposed dist/ area for clarity.
>>
>> == Project vote
>>
>> Result:
>> http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201202.mbox/%3C4F4614CB.9010802%40apache.org%3E
>>
>> including 1 IPMC vote (Benson Margulies)
>>
>> Call for VOTE:
>> http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201202.mbox/%3C4F40CE69.2080402%40apache.org%3E
>>
>> The following was noted in the jena-dev RC-4 vote:
>>
>> * The license information for Plugged-In software is in the distribution
>> LICENSE file twice.
>>
>> == Staging repository
>>
>> https://repository.apache.org/content/repositories/orgapachejena-001/
>
> This contains zip and tar.gz binary and source archives, which should
> be deleted as they are not useful to Maven.
On the contrary, they are plenty useful to Maven. They are used by its
assembly plugin to allow for transitive dependencies and the ability to
unpackage those distros as needed.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
Posted by sebb <se...@gmail.com>.
On 23 February 2012 15:50, Andy Seaborne <an...@apache.org> wrote:
> The Jena PPMC has voted to release
>
> Apache Jena TDB 0.9.0-incubating
>
> and we would now be grateful if members of IPMC would review and vote for
> this release.
>
> == Major changes since RC-2
>
> + Distribution has it's own content for NOTICE/LICENSE files which
> rolls up information for the redistributed binaries.
> + jar file META-INF/NOTICE says "Apache Jena - module TDB" at the top.
> + source-release.zip does not contain a trunk/ copy.
> + New dist/ layout
>
> The existing released files will need to moved to this layout.
> The KEYS file is copied into the proposed dist/ area for clarity.
>
> == Project vote
>
> Result:
> http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201202.mbox/%3C4F4614CB.9010802%40apache.org%3E
>
> including 1 IPMC vote (Benson Margulies)
>
> Call for VOTE:
> http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201202.mbox/%3C4F40CE69.2080402%40apache.org%3E
>
> The following was noted in the jena-dev RC-4 vote:
>
> * The license information for Plugged-In software is in the distribution
> LICENSE file twice.
>
> == Staging repository
>
> https://repository.apache.org/content/repositories/orgapachejena-001/
This contains zip and tar.gz binary and source archives, which should
be deleted as they are not useful to Maven.
> Direct link to TDB area in staging:
> http://s.apache.org/vcp
>
> == Proposed dist/ area:
>
> The following will be added to the existing distribution area:
>
> http://people.apache.org/~andy/dist-jena-tdb-0.9.0-incubating-RC-4/
Where is the source that corresponds to:
download/apache-jena-tdb-0.9.0-incubating.zip
It's not easy to find.
And the reverse is just as hard.
> will be added to:
> http://www.apache.org/dist/incubator/jena/
>
> Note: we will reorganise the current dist/ area to fit into this style of
> layout.
Both those layouts are difficult to follow; it's not immediately
obvious how to find the source for some of the binaries.
This is partly because of the directory structure and partly because
the source archive has a different naming convention from the binary
archive.
Some archives are prefixed apache-jena and some just jena.
As already explained, the source and binary archives for each
component should be at the same level.
Either together in a directory, or in parallel source and binary directories.
The latter is especially useful when there are OS-specific binaries.
I would not expect to find any jars in the dist area, only zip and
tar.gz, and if the binary archive has zip and tar.gz formats, so
should the source archive.
The dist area should also not contain maven-only POMs etc; these
should be in the source archive only.
> == Keys
>
> https://svn.apache.org/repos/asf/incubator/jena/dist/KEYS
>
> == SVN tag
>
> The module is currently tagged with the version and "-RC-4". If voted on
> successfully, the tag will be changed ("svn mv") to the same but minus the
> "RC" labelling.
>
> https://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/tags/jena-tdb-0.9.0-incubating-RC-4/
There are a lot of source files without AL headers.
These need to be fixed.
>
> Please vote on this release:
>
> [ ] +1 Approve the release of Apache Jena, module TDB 0.9.0-incubating
> [ ] -1 Don't release, because ...
>
> This vote will be open until:
> Sunday 26/February 23:59 UTC
> (72 hours from the same hour tonight).
>
> Andy
>
> ---------------------------------------------------------------------
> 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