I have a few bash one-liners to wget and check the checksums and gpg
sigs, if you need them.
Christopher L Tubbs II
On Fri, Nov 8, 2013 at 4:47 PM, Josh Elser <[EMAIL PROTECTED]> wrote:
> With 1.6.0, I plan to make a document that will be a more functional
> (step-by-step) walkthrough.
> I think I have a ticket somewhere for that.
> On 11/8/13, 4:19 PM, Sean Busbey wrote:
>> Under "Testing"
>> On Nov 8, 2013 3:14 PM, "Joey Echeverria" <joey+[EMAIL PROTECTED]>
>>> 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.