RC working without TC is a nonsense.
RC: "We release" TC: "There are lots of bugs" RC: "I don't care, release date is already set".
Does this look serious? I don't think so. Indefinite delaying of the release due to bugs also shouldn't be allowed, if bugs aren't blockers of course.
Before, I thought that RC and TC position could be merged, but now I don't think it's good option - project is growing quickly.
Bytheway, can someone please point me how to find a thread with elections of Release Coordinator? Our email archive doesn't support search, I tried google, but didn't find it. We usually had Release Engineer? Or is it just rename?
WBR, Aleksey Bragin.
----- Original Message ----- From: "WaxDragon" waxdragon@gmail.com To: "ReactOS Development List" ros-dev@reactos.org Sent: Monday, October 17, 2005 4:21 AM 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