| 1 |
On Sat, 2019-04-13 at 12:07 +0900, Alice Ferrazzi wrote: |
| 2 |
> > The point is, that if a developer keeps breaking stuff and doesn't |
| 3 |
> > listen to reminders to be more careful, there is a point when QA should |
| 4 |
> > be able to issue a ban to make the developer realize he can't go on |
| 5 |
> > like |
| 6 |
> > this. |
| 7 |
> |
| 8 |
> I think such problems have to be dealt by using continuous integration checks on commits, not by banning people around. |
| 9 |
|
| 10 |
And how does that help, if the developer doesn't fix the breakage |
| 11 |
introduced? Effectively he's blocking things for everyone else until |
| 12 |
somebody does the work needed to fix his action. |
| 13 |
|
| 14 |
Also, you can't detect everything via CI. Some things just require |
| 15 |
thinking. |
| 16 |
|
| 17 |
-- |
| 18 |
Best regards, |
| 19 |
Michał Górny |
Archives