[
https://issues.apache.org/jira/browse/COMMONSRDF-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493679#comment-14493679
]
ASF subversion and git services commented on COMMONSRDF-16:
-----------------------------------------------------------
Commit ecb5e33136497d0552e95e692e0a0dbd44834379 in incubator-commonsrdf's
branch refs/heads/COMMONSRDF-16 from [~wikier]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-commonsrdf.git;h=ecb5e33 ]
COMMONSRDF-16: followed the guidelines for podling versions
> Sketch versioning scheme
> ------------------------
>
> Key: COMMONSRDF-16
> URL: https://issues.apache.org/jira/browse/COMMONSRDF-16
> Project: Apache Commons RDF
> Issue Type: Bug
> Reporter: Sergio Fernández
> Assignee: Sergio Fernández
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> As we discussed in the mailing lists:
> http://markmail.org/message/c2mcomocs7x2b4bc
> in order to move forward with our first release a detail we have to take a
> look is how the versioning scheme of our two artifacts.
> The current proposal to validate is:
> * both get released separately
> * api is always versioning without patch number (i.e., only x.y)
> * simple impl can release patch versions (x.y.z), but then it's clear the
> api version it is implementing
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
