Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and Outlook for RC4 +2 day

On Jun 9, 2010, at 9:43 AM, David M Williams wrote:

Perhaps a litmus test is as follows ... if the build failed, could you live without it?

Yes, we could, but it won't be good.

Trick question ... if so, then why do it at all, so late?

We do it so late, because we first wanted to freeze the code.
I think there's no better thing you can do during the RC phase than to improve documentation.

The idea is that if the build breaks there will be ways to publish the documentation differently.
However, I'm pretty confident that the build won't break.

But, it is your release, quality is important.  For a case like "documentation improvements" I think a review/request from
your PMC/Planning Council rep would be in order, before I push the build button.

Ok, if that's the formal thing to do. 

Thanks ... sorry I didn't think to emphasize this quiet week concept, and document it better.

Yes, it wasn't clear to me. I see that building a simultaneous release is a big challenge, but I cannot freeze all my developers a couple of weeks before the release. Maybe the main problem here is that the documentation is bound to the binaries and therefore needs rebuilds.


Back to the top