Ed,
I don't understand why you want a M6b since we don't have M6a ....
When platform M6 came up, we made a M6 build, why do we want a M6b
build when platform M6a arrives ?... We should probably be coherent
with our publication stream (M6, M6a, M6b) rather than "trying" to
follow the platform one
We haven't had any need to rebuild for Indigo M6, even though we
have used the incorrect platform repository. We have avoided the
problem since we don't have dependencies on the problematic plugins,
org.eclipse.search...
I will run/publish M6a build, but the question is...
Should we try make this build available in the EPP ?. Even if we had
a chance for that (I think that the eclipse indigo stating
repository, which feeds the EPP, has already been built and
published) I think that it could be risky. So I'm inclined to do a
M6a build as soon as we ensure we don't impact EPP publication.
I'll wait a little bit to obtain your +1 before doing the build.
Best Regards
Adolfo.
El 20/03/2011 15:24, ed@xxxxxxxxxxxxx escribió:
Hi Adolfo
The new build must not be M6a, since it appears that there will be an M6a
for all EPP to resolve a build dependency issue.
Please make the new build M6b.
I'm undecided about whether to encourage tutorial attendees to take the
extra installation step. It has important fixes:
- EnumerationLiterals work
- validation markers no longer persist after text is plausible again
but I'm not sure how much usage attendees will have time to make, so will
they care? There are many other M6 issues to worry about, so hopefully
attendees will appreciate the difference between an M6 and full release.
I very much doubt that I will commit any more fixes before tomorrow.
Regards
Ed
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|