You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Work in progress...

General getting started information here

tbd

 

Additional Information

 

BEFORE you unzip the release candidate

1a Check that Checksums are valid

Add information about tools to use, tips, and tricks for checking this information.

1b Check that PGP signature is valid

Add information about PGP tools, procedure.

AFTER you unzip the release candidate

2 Check the commit ID matches the VOTE email

The idea here is to check that the commit ID in the downloaded file matches that in the VOTE email. You will use a command line terminal.

Approach 1 (clone the git repository, checkout the commit id, and compare to release candidate)

This approach uses Git commands to compare the downloaded release candidate to a cloned git repository. You will clone one copy and unzip the other copy in such a way that will "trick" Git into thinking you are comparing two versions that you have edited. (I'm missing part of the picture here. What is the end configuration you want before you use git status to compare files?)

  1. Make a new directory and change to that directory (e.g., mkdir 1 ; cd 1)
  2. Git clone that-repository (which repository?? from where??)
  3. Checkout the commit id from the repository you just created: git checkout <commit_id>
  4.  rm -rf* (remove a directory? I don't understand this step.)
  5. Unzip the release candidate (e.g., apache-taverna-parent-2-incubating-source-release.zip) (into the same directory?)
  6. mv apache-taverna-"/*. (one level up) (Move the release candidate up one level? Because it zips into a new folder?) 
  7. git status

Git will then check the checksums of every file and let you know what has "changed." If there are NO CHANGES, then the commit ID in the VOTE email matches the release candidate.

Approach 2 (download git commit from GitHub and compare to release candidate)

This approach uses the commit id from the VOTE email to download that commit from GitHub, which is then compared to the release candidate using the diff command.

  1. Download the git commit corresponding to the email by browsing for it on GitHub. Use a URL that follows this pattern: https://github.com/apache/incubator-taverna-language/tree/<hash>

 

3a Check the incubator disclaimer

tbd

3b Check the file names include "incubating"

tbd

4 Check the top-level LICENSE and NOTICE files

tbd

5 Check the source file headers

tbd

6 Check the provenance

tbd

7 Check the dependencies

tbd

8 Check that the source code does not include any binaries

tbd

Build

9 Check for BUILD SUCCESS

detailed information about how to build (run mvn clean install command from distribution directory? send output to files using > textfile1.txt 2> textfile2.txt ?)

AFTER the Build

10 Does the build produce the binaries

tbd



  • No labels