Commit 0261160969189c089b4002d39e6862db5a4e6b1b

Authored by Jürgen Knödlseder
1 parent e2a42f93

Update release information

Showing 3 changed files with 53 additions and 32 deletions
ChangeLog
1   -2014-01-17 Juergen Knoedlseder <jurgen.knodlseder@irap.omp.eu>
  1 +2014-01-18 Juergen Knoedlseder <jurgen.knodlseder@irap.omp.eu>
2 2  
3 3 * Version 0.8.0 released
4 4 ========================
... ...
... ... @@ -2,7 +2,7 @@ vNew Features and Important Changes in GammaLib 00-08-00
2 2  
3 3 Author(s) : Juergen Knoedlseder
4 4  
5   -17 January 2014
  5 +18 January 2014
6 6  
7 7  
8 8 1. Introduction
... ...
1 1 GammaLib information
2 2 ====================
3   -Version: 00-08-00 (January 31st, 2013)
  3 +Version: 00-08-00 (18 January 2014)
4 4 Author: Juergen Knoedlseder (jurgen.knodlseder@irap.omp.eu)
5 5  
6 6  
... ... @@ -92,7 +92,7 @@ The file INSTALL details more about using configure. Also try
92 92 % ./configure --help.
93 93  
94 94 The `make check' command will run an extensive unit test to verify that
95   -GammaLib was correctly built. Make sure that all tests were successful.
  95 +GammaLib was correctly built. Make sure that all tests were successful.
96 96  
97 97  
98 98 Macintosh OS X Installation
... ... @@ -145,14 +145,14 @@ will generate a universal build which contains 32-bit and 64-bit code.
145 145  
146 146 BSD Installation
147 147 ================
148   -GammaLib has been tested on FreeBSD successfully. Follow the Linux
  148 +GammaLib has been tested on FreeBSD successfully. Follow the Linux
149 149 installation instructions above.
150 150  
151 151  
152 152 Solaris Installation
153 153 ====================
154 154 GammaLib compiles on Solaris and openSolaris using the GNU compiler
155   -collection. Follow the Linux installation instructions above.
  155 +collection. Follow the Linux installation instructions above.
156 156 GammaLib also compiles using the Sun Studio compiler, but due to
157 157 some unexpected handling of global variables, it is not fully
158 158 working (see "Known problems" below).
... ... @@ -175,11 +175,25 @@ extensive unit test by typing:
175 175 If everything works successfully you should see
176 176  
177 177 ===================
178   - All 18 tests passed
  178 + All 20 tests passed
179 179 ===================
180 180  
181   -at the end of the test. If no Python support was compiled in, the
182   -number of tests performed will be reduced by one.
  181 +or
  182 +
  183 +============================================================================
  184 +Testsuite summary for gammalib 0.8.0
  185 +============================================================================
  186 +# TOTAL: 20
  187 +# PASS: 20
  188 +# SKIP: 0
  189 +# XFAIL: 0
  190 +# FAIL: 0
  191 +# XPASS: 0
  192 +# ERROR: 0
  193 +============================================================================
  194 +
  195 +at the end of the test (depending on your automake version). If no Python
  196 +support was compiled in, the number of tests performed will be reduced by one.
183 197  
184 198  
185 199 Setting up your environment
... ... @@ -227,43 +241,50 @@ Documentation
227 241 =============
228 242 The doc directory (usually at /usr/local/gamma/share/doc/gammalib)
229 243 contains the most recent set of updated documentation for this release.
230   -A detailed documentation can be created using Doxygen by typing:
  244 +A detailed documentation can be created by typing:
  245 +
  246 + % make doc
231 247  
232   - % make doxygen
  248 +before installing the library. Two types of documentation exist:
  249 +* code documentation
  250 +* user documentation
233 251  
234   -before installing the library. Doxygen can be obtained from
235   -http://www.stack.nl/~dimitri/doxygen/
  252 +Code documentation is created using Doxygen. You need Doxygen on your
  253 +system to generate the code documentation. This includes man pages.
  254 +Doxygen can be obtained from http://www.stack.nl/~dimitri/doxygen/.
236 255  
237   -This is a development release and the documentation is largely, but
238   -not entirely up to date. We are working on it. Please be patient or
239   -volunteer to help.
  256 +User documentation is created using Sphinx. You need Sphinx on your
  257 +system to generate the user documentation. Sphinx can be obtained
  258 +from http://sphinx-doc.org/install.html.
240 259  
241 260  
242 261 Bug reports
243 262 ===========
244 263 To report or search for bugs, please use the GammaLib Bug Tracker at
245   -https://sourceforge.net/tracker/?group_id=282143&atid=1196795.
  264 +https://cta-redmine.irap.omp.eu/projects/gammalib. Before using the
  265 +tracker, please read
  266 +https://cta-redmine.irap.omp.eu/projects/gammalib/wiki/Submission_guidelines
246 267  
247 268  
248 269 Known problems
249 270 ==============
250 271 Python support
251 272 GammaLib comes with Python wrappers so that all classes can be
252   - directly used from Python. To compile-in Python support, GammaLib
  273 + directly used from Python. To compile-in Python support, GammaLib
253 274 needs the Python.h header file, which on many distributions is not
254 275 installed by default.
255 276 To make Python.h available, install the Python developer package
256   - in your distribution. Otherwise you will not be able to use GammaLib
  277 + in your distribution. Otherwise you will not be able to use GammaLib
257 278 from Python.
258 279  
259 280 Readline support
260 281 Many distributions do not have the readline header files and symbolic
261   - link to the shared library set up by default. The same is true for the
262   - ncurses library that is needed by readline. To properly compile-in
  282 + link to the shared library set up by default. The same is true for the
  283 + ncurses library that is needed by readline. To properly compile-in
263 284 readline support in GammaLib, make sure that the redline header files
264   - exist and that the symbolic links are set. In many distributions,
  285 + exist and that the symbolic links are set. In many distributions,
265 286 the shared redline and ncurses are located in /lib, while the symbolic
266   - links are in /usr/lib. Make sure that you have symbolic links with
  287 + links are in /usr/lib. Make sure that you have symbolic links with
267 288 names
268 289  
269 290 libreadline.so
... ... @@ -279,23 +300,23 @@ Readline support
279 300 Solaris
280 301 Although GammaLib builds on Solaris using the Sun compiler, there are
281 302 problems with global symbols in the shared library that prevent the
282   - model registry to work correctly. Furthermore, GammaLib is not able
  303 + model registry to work correctly. Furthermore, GammaLib is not able
283 304 to catch its own exceptions, which prevents the FITS interface to work
284 305 correctly.
285 306 GammaLib has however been built and tested successfully using the GNU
286 307 compiler, and this is the only build method that is currently supported.
287 308 Problems have also been encountered when compiling cfitsio versions
288   - more recent than 3.250. The problems have been reported to the cfitsio
289   - developer team, and are likely to be solved in the future. For the
  309 + more recent than 3.250. The problems have been reported to the cfitsio
  310 + developer team, and are likely to be solved in the future. For the
290 311 time being, it is recommended to use cfitsio version 3.250 on Solaris.
291 312  
292 313 OpenSolaris
293 314 On OpenSolaris, the same problems concerning the SunStudio compiler
294 315 occur as for Solaris, and also here, the GNU compiler is the recommended
295   - tool to build GammaLib. Also here, cfitsio version 3.250 is the
  316 + tool to build GammaLib. Also here, cfitsio version 3.250 is the
296 317 recommended library as more recent version feature relocation
297 318 problems. GammaLib has been tested using gcc 4.3.2 on
298   - OpenSolaris 2009.06. Make sure to create the symbolic links
  319 + OpenSolaris 2009.06. Make sure to create the symbolic links
299 320  
300 321 ln -s /usr/bin/gcc4.3.2 /usr/bin/gcc
301 322 ln -s /usr/bin/g++4.3.2 /usr/bin/g++
... ... @@ -303,12 +324,12 @@ OpenSolaris
303 324 which are not there by default to avoid excess warnings during
304 325 compilation.
305 326 For OpenSolaris 2009.06, no readline package is available, hence
306   - readline support is not readily available. Readline support can however
  327 + readline support is not readily available. Readline support can however
307 328 be enabled by directly installing the GNU ncurses and readline packages
308   - from source (http://ftp.gnu.org/gnu). This has been done successfully
309   - on OpenSolaris 2009.06 for ncurses-5.9 and readline-6.2. Make sure
  329 + from source (http://ftp.gnu.org/gnu). This has been done successfully
  330 + on OpenSolaris 2009.06 for ncurses-5.9 and readline-6.2. Make sure
310 331 to specify the `--with-shared' option when configuring ncurses, so
311   - that the shared library will be built and installed. Otherwise,
  332 + that the shared library will be built and installed. Otherwise,
312 333 relocation errors may occur during compilation of GammaLib.
313 334  
314 335  
... ...