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

Tom and I have looked at the new patch and agree it looks good.  The bug report has been updated.

As for the process stuff, you could have/should have/might have/... several things but that doesn't change the fact that we are 5 weeks past the API freeze and at the start of warmup builds for functional freeze looking to commit new function and API.  There is a reason we have a rampdown process.  It is not meant to block things but rather to give a chance for sober second thought and check that we are not doing something stupid in the heat of the "crap I forgot to ..." moment.  In this case some really good feedback on the API came from several sources so the process seems to have done its job.  Thanks to all.

Jeff


On 2011-04-20, at 10:42 PM, Pascal Rapicault wrote:

1) only if this means 3.7.1.
2) Not sure if this is possible since the classes are in a public package.
3) I think we are making an overly big deal of this whole thing.
The API proposed has been reviewed by Dave and others a long time ago and it has not changed since then.
The feedback from the last few days has only been focused on naming... which, as we know too well in Equinox, is a sign that there is no other issues.
The other thing to remember is that should I had the chance to commit this API right after EclipseCon, the crappy names that I would have come up would have been carved in stone and we would not be here...

I have attached a new patch to the bug report.


On 2011-04-20, at 10:35 AM, Thomas Watson wrote:

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



<graycol.gif>Jeff 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

<ecblank.gif>
From:
<ecblank.gif>
Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>
<ecblank.gif>
To:
<ecblank.gif>
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
<ecblank.gif>
Cc:
<ecblank.gif>
P2 developer discussions <p2-dev@xxxxxxxxxxx>
<ecblank.gif>
Date:
<ecblank.gif>
04/20/2011 09:29 AM
<ecblank.gif>
Subject:
<ecblank.gif>
Re: [equinox-dev] [p2-dev] Equinox/p2 meeting minutes posted





      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 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


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

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