[ros-dev] Prelude to voting for the Testing Coordinator Roles andResponsibilities.

Casper Hornstrup ch at csh-consult.dk
Mon Oct 17 10:15:26 CEST 2005

> -----Original Message-----
> From: ros-dev-bounces at reactos.org [mailto:ros-dev-bounces at reactos.org] On Behalf Of WaxDragon
> Sent: 17. oktober 2005 02:22
> To: ReactOS Development List
> Subject: Re: [ros-dev] Prelude to voting for the Testing Coordinator Roles andResponsibilities.
> The main issue from my standpoint is that the Release Coordinator
> should work with the Testing Coordinator.  Brandon and I were trying
> to work with Robert to train another on doing releases, and when I got
> back that afternoon from shopping, RC1 was built and up on sourceforge
> with a rather large bug.  Had we simply waited a day, we would have
> been able to ship an RC1 without that single bug.  I just wanted us to
> look good.
> I think the TC is an important position that ReactOS needs, due to
> it's complexity.  However, I have decided to no longer continue as TC,
> if I was even TC to start with.
> It's arguments like these that hurt ReactOS more than anything.
> WD
[CSH] So, unless you get the right to block a release on your own, you
won't be TC?

TC and RC can work together, but blocking a release indefinitely is
not acceptable IMHO. Get a new release date, tell everyone about the
new release date (and why the release is delayed). If people disagree,
they can call for a vote on the subject to settle the matter.


More information about the Ros-dev mailing list