Hi, my two cents from out of the project development:
On 23/07/14 12:02, Rob Vesse wrote:
Obviously doing this kind of restructuring would be really painful with SVN so might I suggest that any such change should happen in conjunction with a move to Git?
+1 for switching to git. For those who have no experience could be a extra work, but it pays off the effort, believe me. It'll bring so many new useful workflows that would benefit the project development, both internal ans external.
The other alternative to such a trunk structure is to have each sub-project live in its own Git repository which does appear to be something that Infra supports - the list of repos athttps://git-wip-us.apache.org/repos/asf shows multiple repos for several projects (Accumulo, ActiveMQ, Ant to name just three near the top of the list) - so we could certainly go down that route if we wished? In that scenario then jena-parent would need to live in its own repository as well (probably the main jena repo would contain just jena-parent and pointers to the other repos). However this approach would complicate releases somewhat since you likely need to have multiple release votes and release artifacts since cutting a release might mean releasing from multiple releases and each would need reproducible sources.
Even if infra would allow you to have different repo, I'd not recommend you to use submodules in that way. Because it'd make a pain the release process.
Cheers, -- Sergio Fernández Senior Researcher Knowledge and Media Technologies Salzburg Research Forschungsgesellschaft mbH Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria T: +43 662 2288 318 | M: +43 660 2747 925 [email protected] http://www.salzburgresearch.at
