Opened 16 years ago
Closed 16 years ago
#160 closed task (fixed)
Prepare "binary" release
| Reported by: | Stephen Siegel | Owned by: | zirkel |
|---|---|---|---|
| Priority: | critical | Milestone: | Release 1.0 |
| Component: | Administration | Version: | 1.0 |
| Keywords: | release binary | Cc: |
Description
We need a binary release that makes it as easy as possible for someone to download and start using TASS. Someone needs to look into the license issues, to find out what we can bundle together with our code without violating the terms of any license. Our license is the GPLv3. Should there be 32-bit and 64-bit versions? Should there be versions for Linux, OS X, and Windows?
Change History (3)
comment:1 by , 16 years ago
| Status: | new → accepted |
|---|
comment:2 by , 16 years ago
Include the examples in the binary release.
When we prepare the release archive file, include the svn revision number in the filename so that we will know exactly which revision it came from. (Similar to what we are doing with source releases.)
All of it needs to be scripted.
comment:3 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
TIm has done it. New tickets can be filed if necessary to change things about the release process.
I've been looking into the licensing, and from what I understand it's fine for us to redistribute CVC3 (they have their own license, but it reads pretty much like the BSD license), ANTLR (BSD license), and GMP (LGPL) provided we give notice that these other pieces of software are being used, and include copies of their licenses.
I'm working on the binary bundles. My priority will be OS X, then Linux, then Windows.