Re: [jdt-core-dev] Current state of BETA_JAVA8

[Daniel Megert <daniel_megert@xxxxxxxxxx>]

Jesper,

first of all thanks for offering your
help - it is very welcome!

Instead of GitHub you could upload your
work to the Gerrit instance at Eclipse.org. This is similar to working
with a branch and makes it easier to check out the code,  review it
and comment on it. JDT Core is already enabled for Gerrit.

Mike, regarding Gerrit, we wait for
quite some time now that the IP process around Gerrit gets simplified [1].
So, if you want to help us on this, that would be great. Regarding the
250 line limit and CQ, the overhead could maybe be limited if we could
point to ta Gerrit change from the CQ - just an idea.

Dani

[1] Bug
381105: Record
keeping on inbound contributions (adopt Signed-off-by or not)

From:	Jesper Steen Møller <jesper@xxxxxxxxxxxxx>
To:	mike.milinkovich@xxxxxxxxxxx, "Eclipse JDT Core developers list." <jdt-core-dev@xxxxxxxxxxx>,
Date:	24.01.2013 19:07
Subject:	Re: [jdt-core-dev] Current state of BETA_JAVA8

---

On 24/01/2013, at 17.21, Mike Milinkovich wrote:


The obvious solution to the 250 line limit is that Jesper achieve committer
status after demonstrating that his patches have demonstrated the necessary
merit.

Srikanth has been very welcoming, and helpful in how
to structure the contributions.

Perhaps creating a JDT incubator sub-project to help bring
new people
along would be a good idea? That approach has worked with other teams in
the
past.


In this particular case, it's the "feature branch"
approach that's useful.
Patches are fine for single fixes, but for big-feature
work, it'd be really helpful to have easy
access to a repo that the committers could review in,
without requiring full committer status.
I chose GitHub for that, for now.

-Jesper
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev