On 06/09/13 23:20, Charles Li wrote:
Is there a release time yet?
We don't have fixed plans - this isn't a resourced project that can
commit to plans. People contribute. Things happen when they happen.
Any plans would be wrong about 30 seconds after deciding them!
Projects are highly independent at Apache. The Jena community is
responsible for Jena - no one else. The large projects (httpd, Hadoops,
tomcat, ...) can make (and stick to) schedules because they have more
resources.
When it's an incremental release (2.10.0->2.10.1), the work is usually
just to execute the process. This is our process:
https://cwiki.apache.org/confluence/display/JENA/Release+Process
This is a big release with several new things going to the build all at
the same time and we're not at the stage of build able to do the final
build.
All this gets discussed on the dev@ list.
What you can do to help is to test the snapshots in anyway you can and
report success or issues arising. Do subscribe and join in the fun.
In an Apache project, anyone can call for a release at any time; they
have to persuade people it's a good idea. "Anyone" does mean only
committer or PMC member - it really is anyone. That "anyone" has to
convince people it is a good time to release and they have to do the
release work, then call the VOTE.
Jena operates on a "clean trunk" policy - the svn trunk should always
build. That's what the snapshots are:
https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
and they get built and tested every night (actually about 8am UTC).
This is our Jenkins setup:
https://builds.apache.org/user/andy/my-views/view/Jena/
(and if you see a build with a maven error code of 143, that means it
succeeded! We don't know why this occasionally happens.)
Any formal release, not a snapshot, is officially the source code, not
the binaries (jars files, Fuseki server etc). The official release is
the signed source-release zip file in the
http://www.apache.org/dist/jena/source area. Binaries are optional extras!
The project uses maven for binary distribution, and it's that actually
imposes the additional condition it has to be a committer who does the
release because the build goes via Apache Nexus server.
Andy
Thanks!
- Charles
On Sep 6, 2013, at 4:54 PM, Andy Seaborne <[email protected]> wrote:
We're working towards a release.
This will be Jena 2.11.0 and Fuseki 1.0.0.
This release includes several new things:
(all links are to the staging site)
* New website design
http://jena.staging.apache.org/
with thanks to Samuel Croset
* Text search
http://jena.staging.apache.org/documentation/query/text-query.html
* Spatial search
http://jena.staging.apache.org/documentation/query/spatial-query.html
developed by Google summer of code student, Ying Jiang.
* SPARQL over JDBC
http://jena.staging.apache.org/documentation/jdbc/index.html
developed by Rob Vesse
* Security policy module
http://jena.staging.apache.org/documentation/security/
developed by Claude Warren
In addition, SDB will become part of release process and not a separate
download. SDB includes an adapter to SAP HANA contributed by Fergal Monaghan.
Andy
