Re: [eclipse-dev] Write access to repos for release engineering

[Daniel Megert <daniel_megert@xxxxxxxxxx>]

Hi Chris

Sorry to be the party crasher here,
but, -1 from me - at least for all projects that I have control over. Commit
rights must be earned on the concrete projects by proving domain knowledge
and pom changes do not count for me. I strongly disagree that pom files
need to be managed by us, see e.g. https://bugs.eclipse.org/387802
and https://bugs.eclipse.org/386114.
If we/I don't respond quick enough to patches, then let me know personally.
I expect that at some point we reach a point, where pom tweaking is not
required, because we still follow the manifest-first approach.

Dani

From:	Krzysztof Daniel <kdaniel@xxxxxxxxxx>
To:	eclipse-dev@xxxxxxxxxxx,
Date:	13.03.2013 22:23
Subject:	[eclipse-dev] Write access to repos for release engineering

---

Hello Eclipse masters,

The CBI team (especially Andrew and Thanh) worked hard to get the build
working and provided patches for many of your plugins. Unfortunately, as
a consequence of the switch, your responsibilities got bigger. You're
now expected to know and manage your poms, and you're responsible for
keeping your part of Eclipse building.

There's no Kim the build fixer. 

I know that everyone is stretched to the limits, so I'd like to propose
a write access to *all* CBIzed projects to Thanh. Having someone with a
good knowledge of the entire CBI should be beneficial for everyone - and
restore the tradition of a releng engineer being able to fix (or break)
everything.

Thoughts?

--
Best regards,
Chris

_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev