[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdt-ocl.dev] Go for RC2 and RC3... plans
|
Sure, reviewing is good.
I'll see when the enhancement reaches me how much of a change it would
be and how close to either RC2/RC3 it would be. We'll play it through
Bugzilla, so you can easily defer it to 3.1.1 by a -1.
Ok?
Cheers,
-- Axel
On 5/23/2011 1:00 PM, Willink, Ed wrote:
Hi Axel
The review requirements for examples treated as documentation are more lax,
but not non-existent. After RC2, I expect any non-releng commit beyond the
core
plugins to be approved by at least one other committer for safety; i.e. no
risk of
interesting new extension points or models or registrations upsetting
something else.
While there is an RC3, my recollection was that last year RC4 didn't really
happen,
and so RC3 was pretty much the last version, so we want to be very very sure
that
RC3 has no problems, because we cannot count on respins; they will only
happen
for major issues that cannot be worked around, and anything in 'examples'
has the
simple workaround of don't install the examples.
Rather than rush something for RC3, you too might think in terms of what
could be
in a very early 3.1.1, remembering that 3.1.1 would be a maintenance release
so
no really new functionality. Derived property impact analysis seems like a
bug
fix, so no problem doing that in 3.1.1.
Regards
Ed
-----Original Message-----
From: mdt-ocl.dev-bounces@xxxxxxxxxxx
[mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Axel Uhl
Sent: 23 May 2011 11:31
To: MDT OCL mailing list
Subject: Re: [mdt-ocl.dev] Go for RC2 and RC3... plans
Hi Ed,
Axel: if you're going to the OCL workshop in Zurich we can plan the
exploitation of the new pivot evaluator. (Since I
registered a Conflict
of Interest, I have no idea whether your paper was accepted or not.)
accepted, going. Let's meet there and discuss.
For RC3, I plan only major oopses found while writing documentation.
These should be +1'd even for examples, so it would be good
if you make
time on Friday/Sunday to review documentation and other
patches for at
least lack of impact beyond the scope of the examples/documentation.
I have a student under SAP contract work on impact analysis
for derived
properties. We'll see if he gets it ready before RC2 or RC3, but my
understanding is that in the examples areas we're free to
commit up to
the latest point in time before release. Also, the APIs shouldn't
change. Just a few additional tests around derived properties
that will
then be added will work then.
Cheers,
-- Axel
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
Please consider the environment before printing a hard copy of this
e-mail.
The information contained in this e-mail is confidential. It is intended
only for the stated addressee(s) and access to it by any other person is
unauthorised. If you are not an addressee, you must not disclose, copy,
circulate or in any other way use or rely on the information contained in
this e-mail. Such unauthorised use may be unlawful. If you have received
this e-mail in error, please inform us immediately on +44 (0)118 986 8601
and delete it and all copies from your system.
Thales Research and Technology (UK) Limited. A company registered in
England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne
Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number:
774298
Thales UK Limited. A company registered in England and Wales. Registered
Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone,
Weybridge, Surrey KT15 2NX. Registered Number: 868273
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
