[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] [equinox-dev] Equinox/p2 meeting minutes posted

So here are the options as I see them.

1) postpone this new API until next release
2) propose the API as provisional (i.e. use x-internal etc)
3) work on the API as much as possible to gain confidence that it is API we can live with and support in future releases.

3) seems rather risky at this point in time. Is 2) an acceptable approach?

Tom



Inactive hide details for Jeff McAffer ---04/20/2011 09:29:49 AM---If there is no objection I will release that during the weekJeff McAffer ---04/20/2011 09:29:49 AM---If there is no objection I will release that during the week so we can actually work on the code together. I'm not a real fan o


From:

Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>

To:

Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

Cc:

P2 developer discussions <p2-dev@xxxxxxxxxxx>

Date:

04/20/2011 09:29 AM

Subject:

Re: [equinox-dev] [p2-dev] Equinox/p2 meeting minutes posted





I'm not a real fan of this approach in the last week of M7. If bogus API gets into M7 then we'll have a hell of a time removing/changing it. We almost always end up regretting those last minute pushes. For the code itself I don't care but releasing API that is not baked is less than optimal.

Jeff

On 2011-04-19, at 1:30 PM, Pascal Rapicault wrote:
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


GIF image

GIF image