New release format to reflect new development work

pmoneoingen / myschedule

Automatically exported from code.google.com/p/myschedule

0 stars 0 forks source link

New release format to reflect new development work #104

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

The current myschedule-1.x for quartz 1.8 and myschedule-2.x for quartz 2.x 
might not be enough to indicate next major development for myschedule. We will 
like typical 3 versions values for the myschedule itself, and yet another for 
quartz version indicator.

Perhaps something like this is better.

myschedule-3.0.0_q1
myschedule-3.0.0_q2

Original issue reported on code.google.com by saltnlight5 on 29 Nov 2012 at 4:36

GoogleCodeExporter commented 9 years ago

This issue was closed by revision cbdee406e1b9.

Original comment by saltnlight5 on 29 Nov 2012 at 4:48

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Original comment by saltnlight5 on 29 Nov 2012 at 4:50

Added labels: Release-3.0.0_q2

GoogleCodeExporter commented 9 years ago

I have decided to use myschedule-x.y.z_q21 version format for quartz 2.1.x 
series of dependencies.

Original comment by saltnlight5 on 24 Feb 2013 at 2:16

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Never mind. I decided to use even simpler format: a.b.c.d format. Where 

"a" MySchedule major version
"b" indicates the quartz major version. 
"c" MySchedule minor version
"d" MySchedule bug fix version.

Original comment by saltnlight5 on 8 Jun 2013 at 3:36