On 6 December 2012 19:00, Robert Matthews <[email protected]>wrote:
> How do you propose we collaboratively work on this? I'm going to set some > time aside for this, but I'm not sure how proceed safely. > > Jeroen was over in the UK yesterday and again today, so he and I are actually working through on this ... as you'll see from the commits I've been pushing through. The position as of this morning (Fri 7th Dec) is that we've moved all the modules around into their correct directories (at least as defined in the current wiki page), and we're about to start renaming the groupId/artifactIds. There was one issue that came up during this work, to do with oai.core:isis-integtestsupport module's dependencies. I'll comment on that in a separate post. ~~~ To your original question, the most valuable thing to do when you have time is to check out the codebase and go through the actions of putting out a release of - say - the scimpi and nosql components, (though without actually doing so). The whole point of this exercise is to enable releases easier to do, so that's the criteria to determine if we've got it right. For example, I suspect that we'll need to configure the supplemental-models.xml for each of the components, and the RAT tool, and to make sure the release management profile stuff from org.apache:apache is inherited correctly. I intend to do this for core and for the jdo, wicket and restfulobjects components, so that'll be something to work from. But I'm aware that I'm the only person who's had to grok all this stuff to date - for example, there's the release key that you need to create [1] - so there'll be a bit of a learning curve to go up. Another thing we need to discuss is versioning strategy, eg whether to use semantic versioning [2]. But that's probably a post for a different thread. Dan [1] http://isis.apache.org/contributors/key-generation.html [2] http://semver.org > Rob > >
