Closed ansell closed 12 years ago
This has been on my mind as well, although for the sake of continuity I would rather tag the current develop branch as a definitive 1.6 release and bump to 1.7-SNAPSHOT. The problem is that projects already depending on 1.6 will have failed to get the most recent artifacts out of the repository, but jumping to 1.7 for the release won't change that.
That sounds good to me.
Removing your release-1.6 branch may also be a good idea unless we are planning on using it for bug fixes before the next release.
Right, that branch should go away. Can you add a bullet to the wiki on uritranslator? Any other changes to go in before the release? Btw. I'll leave jsonld in for now.
I just added a bullet point to the README.md file on my fork along with the same line to the wiki.
JSONLD isn't actually in the reactor right now, as its module is commented out of the pom.xml file:
""
Unless you have configured your Jenkins differently to mine, this will mean that it is not released by Jenkins at least. You may need to release it manually.
The https://github.com/tristan/jsonld-java implementation isn't quite stable enough to be used yet, as highlighted by a few issues right now https://github.com/tristan/jsonld-java/issues . In addition, it has a dependency on both Jena and Jackson as its JSON library right now, so we may want to address that before using it above the stanbol library. There has been talk of splitting it so that there are pure Sesame and Jena modules that use a common base module, so that will remove the Jena dependency. Replacing Jackson with org.json could be possible, but the library would need to be stable first, as I don't want to maintain a separate version of the JSONUtils class if it is regularly changing.
I will rebase my "feature/fixjsonld" branch against the 1.7-SNAPSHOT develop branch after you create it, so it isn't a new feature for this release.
That sounds good. I will bump the version numbers to 1.7-SNAPSHOT on my current develop branch now that the 1.6 release is done.
I think we need to do a version bump, or at least switch to a -SNAPSHOT version for the develop branch.
Non-snapshot versions are generally thought to be immutable, or at most, only in limbo for a day or two.
I would prefer to release the current develop branch to master as 1.7 and then bump the develop branch to 1.8-SNAPSHOT.