RE: [mylyn-dev] tracking of api changes

["Mik Kersten" <beatmik@xxxxxxx>]

Agreed.  

Contributors: please note that for the time being we are committed to not
making any breaking API changes.  As part of the 3.0 planning we will decide
when we merge backwards compatible changes into breaking changes, but for
now we are limited to the changes that are very well described by Jim des
Rivières' excellent document:

  http://wiki.eclipse.org/Evolving_Java-based_APIs

All contributors making patches to or with commit rights on API components
need to read this document.  I'm brushing up on it myself since Jim has
added some good content on generics.

Steffen: I like your options (2) and (3) and suggest you create both the 2.0
and 3.0 porting documents.  On the Mylyn Porting Guide we can link both
documents and relevant resources like those from Eclipsepedia's API Central.


Mik

> -----Original Message-----
> From: mylyn-dev-bounces@xxxxxxxxxxx [mailto:mylyn-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Steffen Pingel
> Sent: Tuesday, July 03, 2007 6:59 PM
> To: mylyn-dev@xxxxxxxxxxx
> Subject: [mylyn-dev] tracking of api changes
> 
> We need to start tracking API changes for the post 2.0 release cycle.
> Here are
> the options I have come up with so far:
> 
>  1) Add it to the existing porting guide Mylar_Porting_Guide marking
> new
> entries with the expected release version
>  2) Start a new page Mylyn_Porting_Guide_3_0
>  3) Move the existing page to Mylyn_Porting_Guide_2_0 and add new
> entries to
> Mylar_Porting_Guide
> 
> We should also make sure that we add @since tags to all new API
> methods.
> 
> Steffen
> 
> --
> Steffen Pingel - steffenp@xxxxxx - http://steffenpingel.de
> _______________________________________________
> mylyn-dev mailing list
> mylyn-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-dev