Re: [mdt-ocl.dev] Helios SR RC1

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi Adolfo

Mid air ... distracted ...

I'm not clear which build you would like me/Alex to promote. The buckminster build still shows your permission problem? The old nightly builds are failing for stupid reasons. Do you know why? The old integration buiold fails because it can't find
org.eclipse.test_0.0.0; I suspect we need to advance our core Eclipse dependency.

The build.cfg at the root of the build gives you a flattened view of the config files. The directory.txt is a flattened view of the map files. You can probably tell what's going on from these without needing to ssh and peek at live files, some of which you can see via the Workspace link on the Hudson Project Page.

I think the first commit to a 3.0.0 plugin must update the version numbers of the plugin and all including features.

I've been thinking that getting all the examples code properly reviewed for Indigo may involve an unrealistic number of late reviews and activities, so it may be more sensible to promote the examples immediately after Helios; that is we do 3.1.0. in October and 3.2.0 for Indigo, 4.0.0 for Indigo+1. This avoids inflicting a major version change on our users till we've done more thorough exercising, and may be our users can then do their corresponding major version change at the same time.

    Ed

On 10/08/2010 13:27, Adolfo Sánchez-Barbudo Herrera wrote:

Hi All,

I've read http://wiki.eclipse.org/Version_Numbering#Versioning_features which confirms that if no plugin has changed, and therefore any containing feature, all the version of plugins and features should stay as 3.0.0 regardless we are producing a "3.0.1 Service Release". So I'll revert the version's increasing I made on Sunday.

A new question arises:

If any of us does any change to a plugin, is his responsibility changing the plugin and/or feature version ? or it's a responsibility of the releng to revise all the changes to properly fix said versions ?. Fortunately I know that API tooling helps to fix plugins versions when you do a change which implies a major or service version change. No idea about what happens with minor changes (bug fixing which doesn't have an API impact) and if the features also are error-marked because they need a version increase....

Cheers,
Adolfo.

--

Adolfo Sánchez-Barbudo Herrera adolfosbh(at)opencanarias(dot)com C/Elías Ramos González, 4, ofc. 304 38001 SANTA CRUZ DE TENERIFE Tel.: +34 922 240231

_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
  

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.851 / Virus Database: 271.1.1/3061 - Release Date: 08/09/10 19:35:00