So the version shown in the major increment.txt file (there is only one version shown per IU) is the SR0 version? I don’t get it. You have CDT IUs in there and I know we haven’t done a major release of anything in years.
Anyway, I think you’ve stated the point. Doing minor releases at an SR like we’re doing now is bad. People consider it to be truly an SR, not a minor release. And we do have the rule that you can only do a major release at SR0.
Photran may be violating the rule, assuming they didn’t also ship 9.0.0 at SR0 (I.e. Forgot to update the version number. Happens out there…)
Doug.
Doug,
I know we don't version the train explicitly. But there is perceived notation of what our releases mean, as Max was alluding to. We call the fall release an SR, but really it includes over 1,000 IUs that have incremented their minor release number, and
a handful that have incremented their major release number. So, to put this in a more direct way: what is the current rules around changing the versions of bundles that are included in the train?
Regarding what I attached, those are a list of IUs (and their version in SR2) that had a major version increment. For example org.eclipse.photran.core shpped version 9.0.0.201502031411 in SR2 and shipped version 8.0.0.201406102021 in SR0. If someone depends
on photran.core, would they consider our February Luna release an SR, Minor, or Major update?
Cheers,
Ian