Hi Denis,
thanks for the detailed explanation. I'm going to try it by myself
for getting a little bit more familiar with the process.
best regards,
Martin
Am 13.11.2012 17:15, schrieb Denis Roy:
If you want to save your time, I can submit the contribution for
you. Just let me know.
Denis
On 11/13/2012 11:14 AM, Denis Roy
wrote:
Hi Martin,
First, thank you for inquiring about the process. Indeed, the 2
java files in the patch contain 310 LOC. From here, we must
submit the patch through the IP review.
1. Go to https://portal.eclipse.org
and log in using your committer User ID (not your email
address).
2. Locate the Eclipse Projects portal, and next to
technology.babel hit [view]
3. [contribution]
of code to be maintained at eclipse.org
4. Fill out the short form
5. Once you get a confirmation email with an IPZilla CQ number,
go attach the actual patch.
Once IP has cleared, you can commit the patch. At your
discretion, you can also elect Stefan as a committer using the
same Portal.
Denis
On 11/13/2012 03:03 AM, Martin
Reiterer wrote:
Hi,
we are currently working on contributing new features &
bug fixes that have been developed in parallel to our initial
contribution of the message editor enhancements and the I18n
tool suite. One of these enhancements has been written by
Stefan Reiterer (Committer in the Eclipse Mylin Reviews
project) and is documented in the Bugzilla bug [0].
Following the IP Due Diligence Process, the contributed patch
needs to be reviewed by the IP team, because it is contributed
from a non-babel committer and exceeds 250 LOC. Since I'm not
completely familiar with this process, I'm not sure how we
have to proceed. Is it sufficient to set the Bugzilla flag
"iplog" to "+"?
[0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=394054
Thanks,
Martin
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
|
