[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] what @since tag to use when the API graduates?

the @since should follow the version of the manifest.
>From there the question is what will be the version of p2 in 3.6? I would say 2.0 since we are introducing breaking changes by removing some provisional API.

Inactive hide details for Susan Franklin McCourt ---10/28/2009 06:06:35 PM---I'm experimenting/playing with wild refactorings iSusan Franklin McCourt ---10/28/2009 06:06:35 PM---I'm experimenting/playing with wild refactorings in the p2 UI to see if there is a "bare minimum" set of UI classes that would


From:

Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>

To:

P2 developer discussions <p2-dev@xxxxxxxxxxx>

Date:

10/28/2009 06:06 PM

Subject:

[p2-dev] what @since tag to use when the API graduates?




I'm experimenting/playing with wild refactorings in the p2 UI to see if there is a "bare minimum" set of UI classes that would make sense as API. This mainly involves the operations and the policy objects. In moving classes around to API-named packages, I get API tooling @since tag errors because the tooling expects the @since tags to match the manifest version. However, so far I have been using Eclipse release conventions.

So...I have methods that currently use
@since 3.4

I was assuming that when things actually graduate, we would use
@since 3.6

but that would require a bunch of API problem filters because the tooling (rightfully?) expects to see
@since 1.1

We'll have to have a common strategy for this when we merge the branch back. Thoughts?

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


GIF image

GIF image