Some comments in line.
Wayne
On 08/02/2012 02:37 PM, István Ráth wrote:
All this means is that we didn't catch it the first time.
It is important to emphasize again that "the amount of code
in the contribution" equals to the "original plus the delta".
Nevertheless, I do completely agree with you that each of the
developers should be promoted to committers; to my knowledge,
this has not been possible under the GMT umbrella.
More importantly, the project *must* start working in accordance
with the Eclipse Development Process.
I think the error is on our part in this case. The word
"release" has been historically used to mark milestones in
VIATRA2 development, and is *not* intended to imply that this
is a "release" in the Eclipse.org sense.
Statements like "The VIATRA2 Release 3.1 has been approved by
Eclipse.org!" seem to contradict this. Or at very least, somebody is
mixing up an IP team approval of a contribution with a release in
the Eclipse Development Process sense.
To anybody looking at the project (if I can speak on behalf of
everybody), it sure looks like the project is making official
releases in very much the same way that the EMF project does.
Is there a guide somewhere on how to do this? I'd really
like to resolve all problems as soon as possible.
You can't you're not a committer. You need to have commit rights on
the project make the required changes.
http://wiki.eclipse.org/Development_Resources/HOWTO/Conforming_Incubation_Branding
--
Istvan RATH, PhD
Research associate
Budapest University of Technology and Economics
Fault Tolerant Systems Research Group
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse
Projects
|