[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipselink-dev] Branching for 1.2 today...
|
Yes, there is. Good Question.
Several people have mentioned that it was odd to be building 1.1.1,
1.1.2, and 1.1.3 on a branch named 1.1.0. Doug suggested that we
standardize on branches using only the first two digits, and this makes
a lot of sense.
The version numbers of a release are defined as
Major.Minor.Service."qualifier string". Where Major would be incremented
for an "API breaking change"; Minor would increment for "externally
visible" changes - additions to API, performance changes, major rework;
the Service number would increment on non-API changes - manifest
updates, bug fixes, changes to compiler settings. The Qualifier is a
string used to differentiate one "release" from another. We use it to
identify each build. The definitions can be found here:
http://wiki.eclipse.org/Version_Numbering
Since a development "stream" or "branch" will include the initial and
follow-up maintenance releases, it makes sense to name the branch (not
the release) using only the Major and Minor version numbers.
I hope this helps.
-Eric
Edwin Tang wrote:
Hi Eric,
Since the previous branch is 1.1.0, I thought this branch were 1.2.0. Just curious, are there any reasons we call it 1.2 instead of 1.2.0?
Thanks,
Edwin
-----Original Message-----
From: Eric Gwin
Sent: August 26, 2009 10:52 AM
To: Dev mailing list for Eclipse Persistence Services
Subject: [eclipselink-dev] Branching for 1.2 today...
I will be branching for 1.2 today. There was one test issue that is
being resolved and once it passes cb, I will be creating the branch.
I will then have the builds turned off for a bit while I setup the crons
for three nightly builds and three branch cbs hourly.
I'm hoping to have everything up and running again by noon
-Eric
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev