Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] How to version a 2.1.1 improvement

I think we purposely don't use the fourth digit in the version to allow 
for what you are doing. So I would suggest It is definitely 
important to have a different number than what customers can download from 
the web. It is also important to have a higher number so that if they do, 
your version will still override it.

Doug Schaefer
Ottawa Lab, IBM Rational Software Division

"Ploett Norbert" <norbert.ploett@xxxxxxxxxxx> 
Sent by: cdt-dev-bounces@xxxxxxxxxxx
04/12/2005 08:26 AM
Please respond to
"CDT General developers list."

"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

[cdt-dev] How to version a 2.1.1 improvement

Hello all,
we are working on an eclipse-based product which needs a small improvement 
in the CDT (as suggested in, but this does not 
matter much for my question).
So I changed a few lines in managedbuilder.core and ui. Under which 
version should the new plug-in be distributed in our product? 
- 2.1.1 is almost correct, but not quite anymore. 
- 2.1.2 does not yet exist, but may be created one day.
- Is it possible to use a sort of sub-numbering scheme like 2.1.1.a or
- Should I actually change names for managedbuilder plugins? This would 
probably amount to creating a new feature.
Waiting for CDT 3.0 is not an option; it is too late for our planned 
Can anybody help, like by explaining a reasonable procedure or pointing me 
to documentation?
Norbert Ploett
Dr.-Ing. Norbert Plött
Siemens A&D ATS 1
Gleiwitzer Str. 555
90475 Nürnberg
Tel.: +49 911 895 3484
Fax: +49 911 895 3715
cdt-dev mailing list

Back to the top