Just playing devil's advocate here...
When the "original" EMF Query is terminated, do we rename "EMF Query
2" to "EMF Query"?
If the EDP is the only roadblock, then we can be creative to work
out a solution.
From my POV, if the scope of the new project maps 1:1 with the
existing project, I'd rather see the transition occur within the
project. I don't mind creating a new project if it makes sense, but
it's a greater-than-zero-cost effort for everybody involved. I'd
rather focus the project-management energy that creating a new
project will require into getting stuff done.
What is the timeframe for retiring the "original" EMF Query? Does it
make sense to schedule a "last" release of "original" and then just
move forward with Query 2? What is the impact on the community? Is
there a continuity story between the frameworks?
Wayne
On 06/06/2011 10:19 AM, Anthony Hunter wrote:
"But due to lack of time from EMF
Query commiters, we decided not to proceed with it."
This one small statement sums up exactly
why I want to move EMF Query2 to it's own project. The new EMF
Query2 project
was supposed to release a replacement for EMF Query and we are
still waiting.
I cannot get anyone on my side to look at EMF Query2 until we have
a release.
I am not happy the implication is that the roadblock is the one
and only
"original" EMF Query committer and that would be myself.
We will restructure EMF Query into EMF
Query and EMF Query2. This will remove all roadblocks on the EMF
Query2
component to release their software.
I will be the lead and only committer
on EMF Query. Who would like to lead EMF Query2? All of the
committers
can move to EMF Query2, except for myself.
Hopefully after several EMF Query2 releases
we can terminate the "original" EMF Query, assuming things work
out.
Cheers...
Anthony
From:
Ashwani Sharma <ashw.kumar@xxxxxxxxx>
To:
Eclipse Modelling Framework
<emf-dev@xxxxxxxxxxx>,
Cc:
Anthony Hunter/Ottawa/IBM@IBMCA,
emo@xxxxxxxxxxx
Date:
06/04/2011 12:58 AM
Subject:
Re: [emf-dev]
EMF Query2 release
Hi,
When we started contributing to EMF Query2 project, we
have an understanding that EMF Query2 should be next generation
query language
and sometime in future might replace EMF Query. That has been the
main
motivation till date to keep everything part of one project.
EMF Query2 projects are build using tycho and EMF Query
is build using athena. Hence, both of them have separate update
sites.
I already made an attempt earlier for merger by bring EMF Query2
features
under EMF Query main feature and hence created a new release plan
for EMF
Query as well, where we included EMF Query2.
But due to lack of time from EMF Query commiters, we decided
not to proceed with it. We decided to have inclusion of EMF Query2
only
after indigo, so that it does not affect anything for EMF Query in
indigo.
Hence, i asked this question now on how to make the new
release after indigo.
The problem with approach of two separate projects
could be that there will be two projects for same purpose of
enable query
on emf models. Is it acceptable ?
Regards,
Ashwani Kr Sharma
On Fri, Jun 3, 2011 at 8:38 PM, Wayne Beaton <
emo@xxxxxxxxxxx >
wrote:
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
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev
|