This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 512319 - Give rights to rebase in Gerrit to all Eclipse committers
Summary: Give rights to rebase in Gerrit to all Eclipse committers
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: PMC (show other bugs)
Version: 4.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-16 12:41 EST by Lars Vogel CLA
Modified: 2017-02-23 10:34 EST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2017-02-16 12:41:36 EST 
Currently Gerrit is configured to allow the author and the committer of the corresponding project. I suggest to give all committers the right to rebase.
Comment 1 Dani Megert CLA 2017-02-17 08:02:01 EST 
This is problematic. If you don't know what's going on in that project/repo then you might put the change into a bad state, e.g. get compile errors. The change can then no longer be tested and reviewed without manual work.

I would not want that everyone can rebase my changes.
Comment 2 Lars Vogel CLA 2017-02-17 08:14:57 EST 
(In reply to Dani Megert from comment #1)
> This is problematic. If you don't know what's going on in that project/repo
> then you might put the change into a bad state, e.g. get compile errors. The
> change can then no longer be tested and reviewed without manual work.

Can you always retrieve all exiting changesets from Gerrit, so if you want to have the state before the rebase that is possible.
Comment 3 Dani Megert CLA 2017-02-17 08:52:18 EST 
(In reply to Lars Vogel from comment #2)
> (In reply to Dani Megert from comment #1)
> > This is problematic. If you don't know what's going on in that project/repo
> > then you might put the change into a bad state, e.g. get compile errors. The
> > change can then no longer be tested and reviewed without manual work.
> 
> Can you always retrieve all exiting changesets from Gerrit, so if you want
> to have the state before the rebase that is possible.

I guess you wanted to say "You can ...". True.

OK then.
Comment 4 Dani Megert CLA 2017-02-23 10:34:22 EST 
The PMC rejected this: https://wiki.eclipse.org/Eclipse/PMC