Andy Seaborne wrote:
On 12/09/11 11:00, Ross Gardler wrote:
On 12 September 2011 09:24, Paolo Castagna
<castagna.li...@googlemail.com> wrote:
...
In relation to releases:
Maybe one way to speed up things would be to separate the "doing an
Apache
release" from "restructuring Jena modules". If we want to do the two
at the
same time, in one shot. It will necessarily take more time.
My concern is that cutting Apache release is something new we all
need to
learn and the best way to learn this IMHO is just doing it and
quickly repair
to any of mistakes we might do with minor bug fix releases.
Another difficulty is the fact that we have modules with different
version
numbers and different life-cycles (or speeds). I do not know how this
is best
managed in other Apache projects.
For the benefit of the archives this is being discussed elsewhere on
the list (e.g. [1] and [2]).
Ross
[1] http://markmail.org/message/avebupsajpwpp25q
[2] http://markmail.org/thread/znkllczykfgmrzxk
We have some significant new functionality available now and I'd like to
put in the users' hands. Fortunately, my day-job would also benefit
from some proper releases with versions numbers.
The current issues are:
1/ Sorting out the last of the copyrights.
I've been sorting out mime recently.
I think we can document contributions (under BSD) now and release from
the current codebase.
2/ Tweaking the assemblies to put in the Apache files, which is just XML
programming.
3/ Mass source code license change - the conversion script (in ARQ as
I've been starting there) does a reasonable job so the only reason for
not running it is it removes the previous record of contributors in a
few places.
This are in SVN history anyway. No information is lost.
4/ Anything else.
It is a long time since the last Jena release.
I remember there were some problems with the -sources included in the
dependencies, but I think this is fixed now. I am saying just to double
check and not to forget in case there are still issues. If so, please,
create a JIRA issue for it and assign it to me.
We should upgrade SL4J dependencies in Jena to the latest stable SL4J
release. I keep getting workings about having a mismatch but I did not
tracked down all the details of this. It is easy enough to use the same
SL4J version in all our modules.
As we begin release things in Apache, it is not a bad idea, initially
at least, to plan for frequent bug fix releases (in case small issues
or problems appear). It is also a good way to get used to the release
process.
Paolo
Andy
