Re: Module Structuring and Release Cycles

[Andy Seaborne <an...@apache.org>]

On 30/07/14 14:33, Sergio Fernández wrote:
> 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.

I think we're heading for git (except for the website).

CVS -> SVN -> git -> ??

!!

>
>> 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.

It does seem to be at best hard-code assumptions about what and how to 
release whereas one repo is neutral.  As the repo is long term choice, 
it's nice to have it independent of release requirements.

	Andy

>
> Cheers,
>