>> Do we need extra zeros here like 1.1.x or are 2 digits enough?

Depends on how we want to version. So generally the first digit is major, the 
second minor, and the 3rd maintenance. If this goes against a standard, please 
enlighten me :)

So new features go into minor releases and major features, changes, etc, go 
into a major. Or if we think the product has changed enough to warrant a major 
release, bump up the version.

Ex: 1.1 is a typical feature release, 2.0 is a big release. 1.2.1 is a 
maintenance release for 1.2.

So yes, we can track the full release numbers. Just depends on how we want to 
manage versions.

Thoughts?


________________________________
 From: Werner Keil <[email protected]>
To: "[email protected]" <[email protected]>; 
Reza <[email protected]> 
Sent: Thursday, July 17, 2014 10:48 AM
Subject: Re: Jira
 

Do we need extra zeros here like 1.1.x or are 2 digits enough?

Any component or POM module in TRUNK that was tagged and expects changes in
the coming days or hours please don't forget to raise the version number in
the subsequent POMs to
either 1.1.0-SNAPSHOT or 1.0.1-SNAPSHOT (that depends on how we want to
increase the next number) as well as 1.5.0-SNAPSHOT or 1.4.2-SNAPSHOT for
browsermap.

Thanks,
Werner


On Thu, Jul 17, 2014 at 4:34 PM, Reza <[email protected]>
wrote:

> So I think I have all the components of the project here:
>
>
> https://issues.apache.org/jira/plugins/servlet/project-config/DMAP/components
>
>
> Ive added a few more tasks to the list this morning. In particular, I
> created an Epic to capture the W3C tasks since there will be several:
>
> https://issues.apache.org/jira/browse/DMAP-49
>
>
> As for versions, not sure if there is a way to give different components
> their own versioning scheme. The reason being is that im not sure its going
> to be practical to keep all the components on the same versioning. Its
> important to try and track tasks with versions (ie: a roadmap), so maybe we
> label the version with its component, ex: 1.1 (java-client), 1.1 (data),
> 1.5 (browsermap)
>

Reply via email to