blt/results.md

## results.md

      
    Raw
  

              results.md
            
          
    I modified the appropriate section of v1to2.sh to look like:
echo "UPGRADING NODE TO 0.1.1"
./bin/beat-0.1.0 upgrade "0.1.1/beat"

echo "DOWNGRADE NODE TO 0.1.0"
./bin/beat-0.1.0 upgrade "0.1.0/beat"
and the result when running was:
===> Resolving available OTP Releases from directories:
          /Users/blt/projects/us/troutwine/beat/apps
          /Users/blt/projects/us/troutwine/beat/deps
          /Users/blt/.kerl/installs/R15B03/lib
          /Users/blt/projects/us/troutwine/beat/_rel

===> Resolved beat-0.1.1
===> release successfully created!
===> relup successfully created!
===> tarball /Users/blt/projects/us/troutwine/beat/_rel/beat-0.1.1.tar.gz successfully created!
STARTING NODE
UPGRADING NODE TO 0.1.1
Unpacked Release "0.1.1"
Installed Release "0.1.1"
Made Release "0.1.1" Permanent
DOWNGRADE NODE TO 0.1.0
escript: exception error: no case clause matching 
                 {error,{no_such_file,"/tmp/beat/releases/0.1.1/beat.tar.gz"}}
                 
                
Installing the old release from the attached console worked great! Being able to use the startup script to make downgrades would be pretty snazzy, too.