Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rdf4j-dev] Split RDF4J Project

Sounds like a good idea if the releases can then also be staggered (but obviously tested in tandem).

I would recommend strongly AGAINST having a "convenience" git submodule arrangement as it means you easily get wondering commit states in different checkouts, similar to what easily happened with svn. 

A daily SNAPSHOT build system means Devs can work on just one of the repositories at a time, without having to git pull the others to stay up to date.

Obviously if someone is planning breaking changes that affect multiple repos they would have to build both every day (or change their local snapshot policy), but that is not different than today's situation with a single repo.


Have you tested that the proposed structure don't introduce any circular dependencies between the (modules of) the new git repos? 

On 28 Aug 2017 2:39 pm, "James Leigh" <james.leigh@xxxxxxxxxxxx> wrote:
Hi all,

I'd like to split the main github project into a four smaller ones.

RDF4J is already separated into modules. However, any small change
takes time to go through verification stages. This creates a barrier to
entry for contributions that encourages shortcuts. Currently it takes
over an hour to verify the distribution. By splitting the project up
the verification phase can be more focused and modular.

I propose the following setup:

 * /rdf4j           rio, repository-api, and http client
 * /rdf4j-storage   repository-sail, and all sail impls
 * /rdf4j-tools     server, workbench, console, runtime, bom, assembly
 * /rdf4j-testsuite benchmark and testsuites
 * /rdf4j-doc       remains the home of documentation guides

Compliance tests would be split up into the corresponding module. Each
github project would be a fork of the current and each would have
master/develop branches and each would be setup to be built nightly.

Issues and Pull-Requests would also be separated, but github allows
referencing issues and PRs in separate projects to aid with
integration.

Thoughts?

James


_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rdf4j-dev

Back to the top