Use Semantic Versioning Where Possible

[daniel-dgi]

We should be using semantic versioning for the overall version number of the software in addition to each 'sub-project' (e.g. sync, services, etc...). Drupal modules will remain in the Drupal versioning scheme.

[ruebot]

I agree.

How about we do this:

Drupal modules: 7.x-2.x (the initial release will be 7.x-2.0)

All other components start at 0.0.1? And, do we create a documentation matrix saying what works with what?

[daniel-dgi]

Sounds fair to me. Drupal adheres to their non-semantic versioning and everything else does it semantically. Probably the best we'll get considering all the ground we cover.

[ruebot]

Do we need to get setup with sonatype? This is where things get uncomfortable for me. Maybe @acoburn or even @awoods could lend expertise there.

...and if we're publishing our maven packages, we should add our code signing keys to the committers document like fcrepo does https://wiki.duraspace.org/display/FF/Fedora+Committers

[daniel-dgi]

Yes?

I don't imagine that's something we want to host ourselves unless we have to.

We will probably have a boatload of artifacts up there. We're basically creating one per java package. Hopefully that's not a problem?

[acoburn]

Setting things up in sonatype is pretty easy. It is all described here: http://central.sonatype.org/pages/ossrh-guide.html

In short, you create a JIRA account with them and create an issue for your project. You'll need to supply the groupId you'll plan to use.

[ruebot]

Excellent. I've created a ticket: https://issues.sonatype.org/browse/OSSRH-18137

[ruebot]

Ok, we're setup for sonatype now. If y'all setup JIRA accounts with them, we can get you added so you can do releases.

[ruebot]

@Islandora-CLAW/7-x-2-x-committers I propose the following; if y'all agree, I'll created a documentation page and outline this. This is also related to #182 and discussion we had on yesterday's call:

#49 (comment)

---

• Drupal modules (anything currently in the 'Drupal' directory in the repo) get standard Drupal version numbers.
• Chullo, and PHP microservices get semantic version numbers, and they are independent of the Drupal version numbers. This would be similar to what happens in the Fedora community with fcrepo4-exts and fcrepo4-labs projects.
• Java components get their own semantic version number and are released on sonatype/maven central.

---

Am I missing anything else?

[ruebot]

See also: #182

[ruebot]

Pull request: #307

[ruebot]

Resolved with a2b376e