Merge just the weekly release related changes to a new branch
too many nots
Just use regular links to the source code so that release manage can see which file is expected to change and so that link checker will alert us if these files ever get moved.
Upload specific files
Separate the RPM build step...it needs to be watched carfully and may need some further explanation when pre-releases are introduced.
Remove the OSX instructions...we should always be performing the release in a vagrant Fedora20 environment.
Demonstrate sha1sum on the local source package
Try adding some warnings
Add checksum to the list of allowed words
Fix the link formatting
Lowercase virtualenv
Some justtification for not making the weekly release documentation the default.
If we create version specific recipe's we can link to those from the version specific documentation.
create ticket before assigning it.
The variable name is VERSION
use a variable name in the checkout
A note to update the installation narrative with version specific homebrew files and sample command output.
unconfuse sphinx with a blank line
Documentation is built for weekly releases
fullstop