Community
Participate
Working Groups
Platform's M1 is on April 12. and last build for M1 is at Apr 10, 6PM eastern. Is there a new version which we can consume for M1
There definitely will be a version. As always it will be the latest version available here: https://download.eclipse.org/modeling/emf/emf/builds/milestone/latest/index.html Currently it references this builld: http://download.eclipse.org/modeling/emf/emf/builds/milestone/S201903211221 But I haven't contributed that to SimRel yet. When I do so, I'll update this Bugzilla with the specific build.
New Gerrit change created: https://git.eclipse.org/r/140293
Gerrit change https://git.eclipse.org/r/140293 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=72f7f9b3367f653acfae2c151df5b6d745bb5c97
It looks like you already did the change to pull from this build: http://download.eclipse.org/modeling/emf/emf/builds/milestone/S201904050820 I just contributed it to SimRel 2019-06 as well.
Platform's M2 is on May 3rd. and last build for M2 is at May 2nd, 6PM eastern. Is there a new version which we can consume for M2?
Yes there is a new build: http://download.eclipse.org/modeling/emf/emf/builds/milestone/S201904250840 I will update now.
New Gerrit change created: https://git.eclipse.org/r/141456
Gerrit change https://git.eclipse.org/r/141456 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=a4287382ad7de22e7d723ec3aa4bedfcd76cac4e
Platform's M3 is on May 24th. and last build for M3 is at May 23rd, 6PM eastern. Any further versions to consume? [In case no new versions expected for 2019-06 please resolve the bug]
No, I don't anticipate the need for a new build before Wednesday.
(In reply to Ed Merks from comment #11) > No, I don't anticipate the need for a new build before Wednesday. Hi Ed, Will you be able to provide a release build for EMF 2.18 before RC1 or RC2?
It's not clear if there will be further builds before the release. That depends on whether any serious bugs are reported. At this point there are no such bugs open.
I've published a new build that I'll contribute to SimRel 2019-06 on Friday (after the M3 contributions are done): http://download.eclipse.org/modeling/emf/emf/builds/milestone/S201905280646
New Gerrit change created: https://git.eclipse.org/r/143211
Gerrit change https://git.eclipse.org/r/143211 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=1da9bdc0ee58dd25d1426ca8f5b61be95397863f
(In reply to Ed Merks from comment #14) > I've published a new build that I'll contribute to SimRel 2019-06 on Friday > (after the M3 contributions are done): > > http://download.eclipse.org/modeling/emf/emf/builds/milestone/S201905280646 I updated to this milestone build, but I can update again when you have a release build.
I assume we need an URL for the release repo and update before we ship?
(In reply to Dani Megert from comment #18) > I assume we need an URL for the release repo and update before we ship? I just ran the build to produce the release repository: http://download.eclipse.org/modeling/emf/emf/builds/release/2.18 It contains the identical bits as http://download.eclipse.org/modeling/emf/emf/builds/milestone/S201905280646 So of course there is no need to rebuild but you likely want to change your target platform to reference this because the milestone build will be deleted when the first milestone build for EMF 2.19 is published.
New Gerrit change created: https://git.eclipse.org/r/143624
Gerrit change https://git.eclipse.org/r/143624 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=82a840b198c67a3db33c23785190b29e44f03bdf
New Gerrit change created: https://git.eclipse.org/r/143656
Gerrit change https://git.eclipse.org/r/143656 was merged to [R4_12_maintenance]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=5e42e1d75e2d6d658d35e1d4ffe73da516b05b53
Merged to R4_12_maintenance branch as well
I suppose we need a new Bugzilla just like this one for 4.13 now...
