ReleaseProcess - Update for the github release process

Scripts/ReleaseProcess

@@ -13,17 +13,13 @@ Generating release packages and updating source control (git)
 - Edit ~/sharppcap_releases/SharpPcap_X.Y.Z+1_ReleaseNotes.txt with any additional
   notes about the changes in the newly released version
 
-Pushing changes out to the world
-- Log into the sourceforge website and go to 'Files'                
-- Click on the SharpPcap folder to expand it
-- Click on 'Add Folder' and create a new folder with a name of the version, like '4.0.0'
-- Click on the name of the new folder
-- Upload files by clicking on 'Add File'        
--- Upload the release notes txt file, the bin file and the source files
--- Click on the 'i' next to the bin file and select Windows, Linux, MacOS and BSD
-   and click save
--- Click on the 'i' next to the src file and select Solaris and Others and click
-   save
-- Rename the release notes file to 'README' so it is properly detected as the README file by SourceForge
 
+Pushing changes out to the world
 
+- Go to the github project page
+- Click	on the 'releases' tab
+- Click	on 'Draft a new	release'
+- Select the release tag from the dropdown
+- Use the new version as the release name
+- Copy the release notes file content into the text box
+- Attach the .zip of the binary release to the release