Ed,
It's OK to me. No M1 build then.... just one thing
So lets do an M1 in a couple of days time, promote it, but not publicize it.
If we don't have an M1 today, why in 2/3 days time. BTW, from my point
of view promote = publish. Since you are promoting the build, you are
making it available from the downloads web page....
Maybe your changes could go in a published Integration build for
anybody interested in them. The next stable build which incorporate the
new changes would be M2.
I have to have lunch.
See you tomorrow (still without Internet access >.<)
Regards,
Adolfo.
And I'll put my patches in for it.
Ed
-----Original Message-----
From: mdt-ocl.dev-bounces@xxxxxxxxxxx
[mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Adolfo
Sánchez-Barbudo Herrera
Sent: 16 August 2010 16:21
To: mdt-ocl.dev@xxxxxxxxxxx
Subject: Re: [mdt-ocl.dev] 3.1.0 N-builds
Ed,
Please build and promote an M1 today. Nothing should have
changed. I won't
commit anything till tomorrow. I don't think that it
matters that all
(unchanged) plugin ids are 3.0.0.
The "final" build succeed. However, while checking the generated
artifacts I've noticed the following:
org.eclipse.ocl.all.sdk feature/feature.xml:
<url>
<update label="%updateSiteName"
url="" class="moz-txt-link-rfc2396E" href="http://download.eclipse.org/modeling/mdt/ocl/3_0/updates/">"http://download.eclipse.org/modeling/mdt/ocl/3_0/updates/"/>
<discovery label="%updateSiteName"
url="" class="moz-txt-link-rfc2396E" href="http://download.eclipse.org/modeling/mdt/ocl/3_0/updates/">"http://download.eclipse.org/modeling/mdt/ocl/3_0/updates/"/>
</url>
This kind of information should have been updated with the new update
site, the feature version increased, etc
We could consider promoting/publishing the M1 build without
any fear of
breaking something. However, giving such inconsistencies I'm not sure
what to do:
1. No publishing M1 build.
2. Publishing the current successful build.
3. Revising all the features (I think just the coordinating features)
rebuild and publish.
2) and 3) would also be pending on receiving commitment rights on
org.eclipse.indigo.build project
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=321857)
I think you prefer 1), and giving the circumstances I'm also
giving up
to produce the M1 build today....
Let me know what you prefer
Regards,
Adolfo.
--
Open Canarias, S.L.
*Adolfo Sánchez-Barbudo Herrera*
adolfosbh(at)opencanarias(dot)com
<mailto:adolfosbh%28at%29opencanarias%28dot%29com>
C/Elías Ramos González, 4, ofc. 304
38001 SANTA CRUZ DE TENERIFE
Tel.: +34 922 240231
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
|
