Codebase list findbugs / e0e308a8-a55a-4870-ba26-02896280ae03/main src / doc / performingARelease.txt
e0e308a8-a55a-4870-ba26-02896280ae03/main

Tree @e0e308a8-a55a-4870-ba26-02896280ae03/main (Download .tar.gz)

performingARelease.txt @e0e308a8-a55a-4870-ba26-02896280ae03/mainraw · history · blame

Create a directory that contains exactly all the files to upload. For example:
  eclipsePlugin-1.3.6.20081104-source.zip                findbugs-1.3.6-rc3-source.zip  findbugs-1.3.6-rc3.zip
  edu.umd.cs.findbugs.plugin.eclipse_1.3.6.20081104.zip  findbugs-1.3.6-rc3.tar.gz

cd to that directory
sftp username,findbugs@frs.sourceforge.net
sftp> cd /home/frs/project/f/fi/findbugs/findbugs/RELEASE
sftp> mput findbugs-*
sftp> cd "../../findbugs eclipse plugin/RELEASE
fstp> mput edu.* eclipsePlugin*
fstp> quit

Add releases via:
	https://sourceforge.net/project/admin/editpackages.php?group_id=96405	


release daily/candidate/final eclipse plugins

From findbugs directory, do:
	rsync -avz web/ username,findbugs@web.sourceforge.net:htdocs/

For a full release, make a branch in the svn repository:


svn copy "https://findbugs.googlecode.com/svn/trunk" "https://findbugs.googlecode.com/svn/branches/1.X.X" 

For a release candidate, send email to findbugs-discuss and findbugs-core. For a full release, send email to findbugs-announce.