On 02/05/17 20:40, [email protected] wrote:
Oh, glory!
You know better than I how annoying it is to keep typing the version. We
could lock all the versions to be the same and use the properties, but
that has its own problems...
Nope - that doesn't seem to work. I thought it would but it will still
ask and then make a mess of the POMs because it writes in the given
version, not the property.
If all the same version and configure the release-plugin with
<autoVersionSubmodules>true</autoVersionSubmodules>
then it seems to work.
What we need is examples of other builds that do this - it's a bit of a
faff to play with this as it only happens at release time.
Andy
---
A. Soroka
Andy Seaborne wrote on 5/2/17 3:38 PM:
Yes - 3.4.0-SNAPSHOT
It does not come from the POM - it's the maven release plugin
suggesting 3.3.1-SNAPSHOT. It suggests a.b.(c+1)
BTW I think I have found a way to do away with (nearly) all those
questions.
Andy
On 02/05/17 15:13, [email protected] wrote:
I am starting the work now.
The release setup is offering to go to 3.3.1-SNAPSHOT, but didn't we
decide to go directly to 3.4.0? I admit, I've gotten mixed around in the
discussion and doing this while physically cleaning out twenty years of
accumulated stuff in my office is not clarifying my memory. :grin:
---
A. Soroka
Andy Seaborne wrote on 5/1/17 11:35 AM:
On 01/05/17 14:16, [email protected] wrote:
Andy-- I know I volunteered for this, so I'm happy to do it starting
with a vote call tomorrow morning. I haven't been very on top of
things
(traveling most of last week and preparing for new $job) but I'm back
now and can pick it up.
---
A. Soroka
That would be great - if it turns out that life/new-$job gets in the
way, then I can do it. (The dry run looked OK.)
Andy
I have already drafted an email:
(look for the @@ for things to complete)
------------------------------------------------
Subject: [VOTE] Release vote : Apache Jena 3.3.0
Hi,
Here is a vote on a release of Jena 3.3.0
(with Fuseki 2.6.0)
This is the first proposed candidate for this release.
== Dependency changes:
jena-text: Lucene v6.4.1
New module:
jena-text-es
Elasticsearch: v5.2.2 License : AL2
https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
[*] Full list of recursive dependencies at the end
== Updates:
guava (shaded) to version 21.
== Key features of the release:
* Drop support for solr4j, add support for Elastic Search
JENA-1301 - Drop Solr
JENA-1305 - Elastic Search support
Contributions from Anuj Kumar
* Add VCARD4 (JENA-1205)
Contribution from Bart Hanssens
* RDFParser (JENA-1306)
New low level, detailed setup of parsers for special cases.
RDFDataMgr is still the main way to read data (it now uses
RDFParser).
* RDFWriter (JENA-1323)
* Bad URIs in RDF/XML are now warnings (model.read) inline with RDF
1.1.
(JENA-1324)
~39 JIRA
See https://s.apache.org/jena-3.3.0-jira
== Release
Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release.
Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-@@/
Proposed dist/ area:
https://dist.apache.org/repos/dist/dev/jena/
Keys:
https://svn.apache.org/repos/asf/jena/dist/KEYS
Git commit (browser URL):
https://git-wip-us.apache.org/repos/asf/jena/commit/@@
Git Commit Hash:
@@
Git Commit Tag:
jena-3.3.0-rc1
Please vote to approve this release:
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This vote will be open to at least
@@
If you expect to check the release but the 72 hour limit does not work
for you, please email within the schedule above with an expected time
and we can extend the vote period.
Thanks,
@@
Checking needed:
+ does everything work on Linux?
+ does everything work on MS Windows?
+ does everything work on OS X?
+ are the GPG signatures fine?
+ are the checksums correct?
+ is there a source archive?
+ can the source archive really be built?
+ is there a correct LICENSE and NOTICE file in each artifact
(both source and binary artifacts)?
+ does the NOTICE file contain all necessary attributions?
+ have any licenses of dependencies changed due to upgrades?
if so have LICENSE and NOTICE been upgraded appropriately?
+ does the tag/commit in the SCM contain reproducible sources?
--------------------------------------------------
[*]
org.elasticsearch dependencies (recursive) other than org.apache
artifacts:
org.elasticsearch:elasticsearch:jar:5.2.2
net.sf.jopt-simple:jopt-simple:jar:5.0.2
com.carrotsearch:hppc:jar:0.7.1
joda-time:joda-time:jar:2.9.5
org.yaml:snakeyaml:jar:1.15
com.tdunning:t-digest:jar:3.0
org.hdrhistogram:HdrHistogram:jar
net.java.dev.jna:jna:jar:4.2.2
io.netty:netty:jar:3.10.6.Final
com.github.spullara.mustache.java:compiler:jar:0.9.3
