Hi Anthony.
It's probably easier for everybody if the EMF Query project works
toward a consolidated release schedule. We could make an exception
this time if there is a plan element to converge on a shared
schedule with common version numbering.
Having two different sets of committers within the same project
managed via social convention is IMHO a Good Thing(tm).
AFAICT, there is only one Bugzilla component for EMF Query.
Likewise, there is only one entry for EMF Query in IPZilla. I assume
that you mean that the two could be relatively easily separated.
Frankly, the only representation that I see of them being separate
is on the EMF project website. As I look more at the project, it
seems very clear that Query 2 is already acting very much like a
separate project.
Ultimately, it's up to you. If the two different streams are
irreconcilable, then they probably make sense as two separate
projects. I recommend a restructuring review that pulls Query 2 out
of Query into it's own separate sibling project. That will require
some effort to identify those bugs/ipzilla records, and source that
need to be moved.
HTH,
Wayne
On 06/03/2011 09:45 AM, Anthony Hunter wrote:
Hi Wayne,
I figure I should ask the EMO this question.
The EMF Query project has two components,
1) the original EMF Query component
contributed by IBM when the project was started.
2) a new EMF Query 2 component contributed
by SAP.
As I said below, EMF Query and EMF Query2
are two completely separate components in one project with
separate committers,
bugzillas, builds and IP.
EMF Query is doing a release in Indigo.
EMF Query2 did not do a release in Indigo
but now wants to do a post Indigo release.
How is this going to work when EMF Query
is one project from the EMO perspective? Maybe a restructure of
EMF Query2
into a separate project is the only way?
Cheers...
Anthony
From:
Anthony Hunter/Ottawa/IBM@IBMCA
To:
Eclipse Modelling Framework
<emf-dev@xxxxxxxxxxx>,
Date:
06/03/2011 09:38 AM
Subject:
Re: [emf-dev]
EMF Query2 release
Sent by:
emf-dev-bounces@xxxxxxxxxxx
Hi Ashwani,
I really think it is time to consider a restructure. EMF Query and
EMF
Query2 are two completely separate components in one project with
separate
committers, bugzillas, builds and IP.
It would be so much easier if we separated them.
What do you all think?
Cheers...
Anthony
From: Ashwani
Sharma <ashw.kumar@xxxxxxxxx>
To: Eclipse
Modelling Framework <emf-dev@xxxxxxxxxxx>,
Date: 06/03/2011
12:48 AM
Subject: [emf-dev]
EMF Query2 release
Sent by: emf-dev-bounces@xxxxxxxxxxx
Hi,
I am a committer for EMF Query2.
Currently, EMF Query2 sources are under EMF Query cvs project
location.
We have made EMF Query2 sources ready for release.
Since EMF Query2 was decided to be part of EMF Query with
different namespace,
having them under same update site will be better. This change
should happen
after indigo release is completed, since we don't want to
contribute in
simultaneous release of indigo.
Can you please guide us on how we should proceed with this ?
We want to get ready, so that we can make a release once the
indigo release
is done by eclipse.
Thanks and Regards,
Ashwani Kr Sharma
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev
|
