On Fri, Nov 8, 2013 at 3:16 PM, Christopher <[email protected]> wrote: > We won't be able to get rid of all the resulting warnings. So, > automating it would probably just encourage people to ignore these > warnings instead of address them. I'd rather just make it a point to > explicitly check during testing before releasing, and to encourage > people to consider dependencies throughout development.
Do we have a document on how to test a release? In particular, I'm thinking of a process to follow after an RC is cut to determine if it should get a +1 to become the release. -Joey
