[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [modeling-pmc] Action items for the Juno release
|
I agree that we need to have a PMC meeting soon.
2) The EMF build for Juno has been set up to run against Eclipse 4.2. We're still using Buckminster and have no plans of switching to anything else. UML2 has also been migrated to Bucksminster for Juno (and is building against Eclipse 4.2).
3) UML2 has been migrated to git and I hope EMF and XSD will follow suit in the near future. The process is actually very easy - open a bug against Webmaster (Community / Git) and ask for him to migrate your source (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=351781, for example).
Kenn
On Tue, Aug 30, 2011 at 1:04 PM, Ed Merks
<ed.merks@xxxxxxxxx> wrote:
Anthony,
Comments below.
On 30/08/2011 8:21 AM, Anthony Hunter wrote:
Hi Team,
It has been a while since our
last modeling
PMC meeting. We likely should schedule one next month to prepare
for the
Juno release.
Yes, it's been ages.
Traditionally, the modeling
projects
in the yearly simultaneous release shared many common aspects in
their
release. I would like to confirm we all intend to do the same
thing during
Juno.
Off the top of my head, there are
currently
three, maybe there are more?
1) Platform Support
Eclipse 4.2 is the primary
platform,
the one used for EPP Packages. ( see http://wiki.eclipse.org/Planning_Council/August_03_2011
)
Unfortunately I missed that meeting.
We need a statement
in our release plans with regards to Eclipse 3.8.
Historically, we have communicated that we have no interest in
actively
supporting modeling on multiple versions of platforms. Are we
all going
to go with "No support for 3.8 based apps." or something else?
That's a good question. It's hard to imagine having time to create
new improved EMF UI bundles that exploit 4.x and don't rely on any
compatibility layer. To avoid forking EMF, we'd need to go with a
similar approach
and provide a compatibility layer. The
resources for such an effort simply don't exist.
I'm also not sure what we should be say about not supporting 3.8. I
was more imagining for EMF we'd build and test against 3.8 and then
it would be nice to also test against 4.2 (or assume that a whole
bunch of downstream clients will test against 4.2 so we don't have
to).
2) Builds on 4.2
Since we ship on 4.2, we need to
move
our builds to 4.2.
I'm not sure that's a forgone conclusion. Shouldn't we be producing
results that work on 3.8 and on 4.2, expecting the same result to
work in both places, and if they don't, it's a problem the platform
team needs to address in the compatibility layer?
Has there been
success so far? We used to have a common
modeling build, but since then, we have many build technologies.
I am looking
for something that works on 4.2 for some of the projects I lead.
3) GIT migration
I cannot find the reference,
perhaps
someone can help me, but we have a mandate to migrate from CVS
to GIT.
Has this been a successful migration?
Again, whether resource exists to migrate to GIT isn't a forgone
conclusion. I'd certainly very much like to migrate "my projects"
(EMF core and XSD) to GIT.
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
