-
Notifications
You must be signed in to change notification settings - Fork 157
GeoDa Release Instructions
Parallels vms should be used to prepare installers for the following platforms:
- windows 32-bit (windows 7 Dev 32-bit)
- windows 64-bit (windows 7 Dev 64-bit)
- Mac OSX 10.6 (OSX 10.6)
- Mac OSX 10.7+ (OSX 10.7)
- Ubuntu 14.04 64-bit (Ubuntu 14.04 64-bit Dev)
- Ubuntu 16.04 64-bit (Ubuntu 16.04 64-bit Dev)
- Centos 7 rpm (CentOS 7 Dev)
- Centos 7 non-root compressed (no installer needed) (CentOS 7 Dev)
Note: all installers should be tested on corresponding platforms (related vms)
The structure of GeoDa Auto-Upgrade is the following: Directory: version number (e.g. ./1.8.16.4/) contains files that used for upgrading. Different platforms will have different directories. (e.g. ./1.8.16.4/osx106/ for Mac OSX 10.6, ./1.8.16.4/win32/ for Windows 32-bit etc.)
Files:
- checklist.macosx106.txt
- checklist.macosx107.txt
- checklist.win32.txt
- checklist.win64.txt
Each file will be checked by GeoDa application if there is any new versions described in related checklist.xxx.txt file. If there is a new version, GeoDa will prompt a dialog to ask user for updating. If user click "Update" button, then GeoDa will download the files listed in related checklist.xxx.txt file, and replace the original files. After all files been downloaded and replaced, a dialog will be prompted to user to restart GeoDa to run new version GeoDa.
- test.checklist.macosx106.txt
- test.checklist.macosx107.txt
- test.checklist.win32.txt
- test.checklist.win64.txt
Same with above files, these files have prefix "test" will be used when user uncheck the box "Stable Version and Bug Fixes Only" in "About GeoDa" dialog. These files are helpful to test internal builds, and test Auto-Upgrade before official release.
Note: use test.checklist.xxx.txt to make sure all files are working well for auto-upgrading. If all verified, copy test.checklist.xxx.txt files to checklist.xxx.txt for official release.