They are down to the minute because they are generated and no longer humanly set, right?
From: platform-releng-dev-bounces@xxxxxxxxxxx [mailto:platform-releng-dev-bounces@xxxxxxxxxxx]
On Behalf Of Paul Webster
Sent: February-21-13 9:56 AM
To: Eclipse platform release engineering list.
Subject: Re: [platform-releng-dev] CBI based 4.3.0 I-Build: I20130214-2011 <== Finally!
On Thu, Feb 21, 2013 at 9:44 AM, Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx> wrote:
One case that I’m really worried about is one where one of the bundles gets the version that is the same than the one with the highest version. To be concrete
Feature F has
Bundle A v2013
Bundle B v2012
In this case Feature F version is v2013.
Now Bundle B needs to be rebuilt and gets the version v2013, the feature version will still be v2013
and the expected change will not be delivered.
This may sound theoretical but in the reality will happen when we iterate very quickly over RC builds.
except our qualifiers are down to the minute. So F used to be v20130125-1800 (because of A) and when B gets rebuilt as v20130221-0855 then F goes to v20130221-0855
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR