This is another interesting issue of consuming components which may have a process that does not strictly adhere to the eclipse one or may be at a different stage in their release cycle. IMO, since we are consuming a component that exports API, I would argue that it is important for us consumers to run the API check on it just so we can detect if any change affects us. However once we are clear that a change is not affecting us, we should add it to our exclusion list since the component is not necessarily under our PMC, or even organization.
As for this particular case, I propose that we add it to the exclusion list
once Scott will have confirmed this is something he intended to do.
PaScaL
|------------>
| From: |
|------------>
>-------------------------------------------------------------------------------------------------------------------------------------------------|
|Olivier Thomann/Ottawa/[EMAIL PROTECTED]
|
>-------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>-------------------------------------------------------------------------------------------------------------------------------------------------|
|equinox-dev@eclipse.org
|
>-------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>-------------------------------------------------------------------------------------------------------------------------------------------------|
|05/09/2008 10:03 AM
|
>-------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>-------------------------------------------------------------------------------------------------------------------------------------------------|
|[equinox-dev] New API method in ECF (org.eclipse.ecf.identity) since
3.4M6 |
>-------------------------------------------------------------------------------------------------------------------------------------------------|
Hi,
I noticed in the last integration build that a new method
org.eclipse.ecf.core.util.StringUtils#String replaceAllIgnoreCase(String,
String, String) has been added since 3.4M6. It is located in the bundle
org.eclipse.ecf.identity.
This is considered to be a new API added after API freeze and therefore it
would require PMC approval.
I don't know whether ecf bundles are part of the API freeze or not. If
not, then I should add this entry to the exclude list.
If yes, then it would be nice to send a note to the eclipse-pmc mailing
list to request approval for the new API with a bug report associated with
this change.
The template is:
GOALS/BENEFITS:
...
AFFECTED BUGS:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=myBugID
RISKS:
...
PERFORMANCE IMPACTS:
...
Like this we can then add it to the exclude list with the appropriate bug
id reference and we have a tracecability of API changes post 3.4M6a.
Thank you,
Olivier
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
