[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ease-dev] consider new strategy for submitting changes to Gerrit
|
Good idea. So far we do not have problems due to untested merge commits
but getting rid of those extra commits would look better in the project
history.
Created https://bugs.eclipse.org/bugs/show_bug.cgi?id=493545 to track this.
Christian
On 05/12/2016 02:40 PM, Jonah Graham wrote:
At the moment the EASE repo does "Merge if Necessary" when submitting
changes. That leaves the many merge commits in the history and also
commits (or combinations) that have never been run through the
ease-verify-core hudson job.
CDT uses the "Rebase if Necessary" strategy, meaning that the only
merge commits are ones done when integrating a new topic branch.
The Eclipse platform uses "Fast forward only", meaning changes can
only be submitted if they are for the current tip of master.
As the EASE builds are wonderfully fast, I would vote for "Fast
forward only" to ensure every commit to master has been run through at
least one test run.
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com
_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev
