Difference between revisions of "Developers/Release process"
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
		
	
| Uwe Hermann (talk | contribs) m | Uwe Hermann (talk | contribs)   (Creating Windows installers.) | ||
| Line 21: | Line 21: | ||
| ** Freshmeat | ** Freshmeat | ||
| ** ... | ** ... | ||
| === Windows installers === | |||
| In order to create a self-contained Windows installer EXE file for sigrok-cli, you can do the following (currently must be done on a Windows/MinGW system): | |||
| Build and install libsigrok, libsigrokdecode, and sigrok-cli into '''/usr/local'''. | |||
| Download the Windows Python 3.2 installer into c:\: | |||
|  $ '''cd /c''' | |||
|  $ '''wget http://www.python.org/ftp/python/3.2/python-3.2.msi''' | |||
| Create the installer (assumes all required libs in certain directories) via: | |||
|  $ '''cd sigrok-cli''' | |||
|  $ '''./configure''' | |||
|  $ '''cd contrib/nsis''' | |||
|  $ '''makensis sigrok-cli.nsi''' | |||
| This will create a '''sigrok-cli-$VERSION-installer.exe''' self-extracting installer. | |||
Revision as of 10:24, 31 March 2012
This is a list of steps we perform when creating a new sigrok release:
- Check if the manpages are up-to-date.
- Test that make distcheck works without errors and creates a .tar.gz file. Unpack that file somewhere.
- Test that no files are missing, and no extra/unneeded files are in there (non-public header files, *.o files, and that kind of stuff).
- Test that building sigrok from that unpacked directory works without errors.
- Test that installing sigrok from there works.
- Test that running the newly installed sigrok works fine.
- Test at least the demo driver, one hardware LA, one non-default input- and output driver, and one protocol decoder. The more tests the better, of course.
 
- Do all of the above tests on all supported platforms if possible, e.g. Linux, Windows, Mac OS X, FreeBSD.
- Write release notes (containing user-visible, important changes) in the wiki.
- Increase the sigrok version number.
- If there were any backwards-incompatible changes in libsigrok and/or libsigrokdecode, increase their version number too.
- Then, push your current status, including the version number change commit via git push.
 
- If everything works OK, tag the new release in git via: git tag -a v0.1 -m "sigrok 0.1 release".
- Verify that the tag is placed correctly via git tag or gitk.
- Then, push it via git push --tags.
 
- Now create the final tarball via make distcheck as described above, and upload it to SourceForge.
- Announce the new release in various places:
- Short announce email on the sigrok-devel mailing list, mentioning the new version, and the link to the release notes.
- Freshmeat
- ...
 
Windows installers
In order to create a self-contained Windows installer EXE file for sigrok-cli, you can do the following (currently must be done on a Windows/MinGW system):
Build and install libsigrok, libsigrokdecode, and sigrok-cli into /usr/local.
Download the Windows Python 3.2 installer into c:\:
$ cd /c $ wget http://www.python.org/ftp/python/3.2/python-3.2.msi
Create the installer (assumes all required libs in certain directories) via:
$ cd sigrok-cli $ ./configure $ cd contrib/nsis $ makensis sigrok-cli.nsi
This will create a sigrok-cli-$VERSION-installer.exe self-extracting installer.