hi folks,
Just a heads up that tomorrow we release rdf4j 3.0.0. To get a bit of a head start I'd like to tag the release in github already, so that I can start working on migration to the mono-repo. I will do this in an hour or so. The actual release (uploading to central, news announcement, SDK upload, etc) won't happen until tomorrow though.
Immediately after, I want to start work on migrating us back to a mono-repo. Here's how I plan to do this:
2. merge develop into master and close the develop branch. At this point I should only have a single branch to worry about for migration: master. All PRs are merged, no feature branch will be transferred (I've got an open PR myself that is not yet stable, I will leave that out and just replay it when we're done with migration).
3. in the rdf4j repo, reorganize directory structure (probably move the top-level modules into a 'core' directory or something like that - details may change depending on what I find works well).
4. copy over master branch of rdf4j-storage (including history and tags) to rdf4j, to a storage/ directory.
4. copy over master branch of rdf4j-tools (including history and tags) to rdf4j, to a tools/ directory.
5. copy over master branch of rdf4j-testsuites (including history and tags) to rdf4j, to a testsuites/ directory.
6. reorganize rdf4j master branch further to get maven setup consistent (edit poms, dependencies, move a few (test) modules around again).
7. commit and push the whole shebang. Watch Jenkins freak out.
8. Tweak Jenkins setup to deal with the new reality.
9. Create a new develop branch.
Until the above procedure is completed (or at least until step 7 is complete), there is a complete code freeze in place. I am hoping to get things in shape in a day or two, but there's a good chance that it will take until after the weekend to get everything right.
Cheers,
Jeen
