Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] New API in 7.0.2

On Tue, Sep 28, 2010 at 10:24 AM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:
About plugin versions, if I make an API-compatible change in a plugin,
what do I do with the plugin version?  Do I leave it alone or go up (the first time only)
from 3.0 to 3.0.1?

Going up is the right thing to do. We should be doing that for any changes to the plugins. Although as we're always using the timestamp as the qualifier in recent years, the update mechanism works even if you don't change it.

 
Also, what do we do about the feature that contains the plugin?
Vivian had said we must update the version, but it wasn't clear to me when this should be done.

Yeah, we used to upversion all the features to reflect the CDT version, i.e. all the features would move to 7.0.2 to get ready for the next SR. But I'm not sure what policy we're following now.
 
 
Thanks
 
Marc


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Tuesday, September 28, 2010 7:58 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] New API in 7.0.2

Nope.

On Mon, Sep 27, 2010 at 2:06 PM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:
Hi,
 
I am trying to fix a regression in Helios wich requires to add a new constructor to a class.
That means an API change and having to up the version of the plugin from 3.0 to 3.1
 
Is this allowed in a maintenance branch?
 
Thanks
 
Marc
 

 

Marc Khouzam
Software Designer, Methods and Tools

 

Ericsson Canada Inc

EMC/Q
8500 Decarie Blvd.
H4P 2N2, Mont-Royal, Qc, Canada
www.ericsson.com

Office: +514 345 7900 x42350
Fax: +514 345 6159
Mobile: +514 951 7191
Email: Marc.Khouzam@xxxxxxxxxxxx



Ce courriel est confidentiel et uniquement destiné à son ou ses destinataires. Il est défendu de le consulter, de l'utiliser, de le dévoiler ou de le diffuser sans autorisation. Si ce message vous est parvenu par erreur, merci d'en aviser l'expéditeur par retour de courrier et de le détruire sans le divulguer.  Un courriel et ses pièces jointes peut être sans autorisation corrompu, interrompu, amendé, altéré et infecté. L'entreprise ne reçoit et n'envoie de courriel qu'avec l'entente qu'elle n'est responsable d'aucune corruption, interception, modification, altération, infection ou conséquence possible.

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.  E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.

 

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



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



Back to the top