On Oct 23, 2008, at 3:45 AM, Andrey Razumovsky wrote:
> I agree that it's high time for M5. As for CAY-1077, Andrus, how
> exactly
> would you like this dialog to behave?
Let's start a separate thread on that.
>
> I'm currently working on CAY-1119, this is nested contexts for ROP.
> In fact,
> half of the work is already done on the trunk. Still, I have some
> nested
> tests failing yet. Anyways, this is major commit and requires API
> change
> (moving methods up from DataContext to BaseContext and
> ObjectContext) and
> surely be after M5.
Could you elaborate on what changes you envision in the ObjectContext
interface?
> Also I foresee I will soon work with ROP much more, and I'd like
> some other
> features on ROP to be done, like maybe lifecycle callback-like
> functionality. So I'd rather we limit "no more API changes" later than
> sooner.
I am sure that will take sometime until the beta feature freeze. We'll
still allow occasional API changes related to bug fixes. Also we can
fork a branch for 3.1 (or create a STABLE branch for 3.0, and develop
3.1 on trunk) if needed, so the new stuff can be developed in parallel
with stabilizing the final release. And then by the date of 3.0 final
people won't care about it, as trunk will have a bunch of new cool
things :-). Anyways, there are fairly straightforward ways to
accommodate your own development priorities and the release schedule.
Andrus
This archive was generated by hypermail 2.0.0 : Thu Oct 23 2008 - 12:05:23 EDT