gnuastro-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnuastro-commits] master faa28a8 1/2: Preparations for release of versi


From: Mohammad Akhlaghi
Subject: [gnuastro-commits] master faa28a8 1/2: Preparations for release of version 0.12
Date: Wed, 20 May 2020 11:42:02 -0400 (EDT)

branch: master
commit faa28a87bf9875ec1174e2a2d3c3252d8c979dcf
Author: Mohammad Akhlaghi <address@hidden>
Commit: Mohammad Akhlaghi <address@hidden>

    Preparations for release of version 0.12
    
    Some minor corrections were necessary for the 12th release of Gnuastro.
---
 NEWS                         |  2 +-
 doc/announce-acknowledge.txt |  7 ++-----
 doc/gnuastro.en.html         | 10 ++++++----
 doc/gnuastro.fr.html         |  8 ++++----
 doc/gnuastro.texi            | 15 ++++++++-------
 doc/release-checklist.txt    |  2 +-
 6 files changed, 22 insertions(+), 22 deletions(-)

diff --git a/NEWS b/NEWS
index 923de68..f918dd3 100644
--- a/NEWS
+++ b/NEWS
@@ -3,7 +3,7 @@ GNU Astronomy Utilities NEWS                          -*- 
outline -*-
 Copyright (C) 2015-2020 Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
-* Noteworthy changes in release X.XX (library X.X.X) (YYYY-MM-DD) [stable]
+* Noteworthy changes in release 0.12 (library 10.0.0) (2020-05-20) [stable]
 
 ** New features
 
diff --git a/doc/announce-acknowledge.txt b/doc/announce-acknowledge.txt
index 45699ec..8065cab 100644
--- a/doc/announce-acknowledge.txt
+++ b/doc/announce-acknowledge.txt
@@ -1,10 +1,7 @@
 Alphabetically ordered list to acknowledge in the next release.
 
-Raúl Infante-Sainz
-Raphael Morales
-Alejandro Serrano Borlaff
-Zahra Sharbaf
-Joseph Putko
+
+
 
 
 Copyright (C) 2015-2020 Free Software Foundation, Inc.
diff --git a/doc/gnuastro.en.html b/doc/gnuastro.en.html
index ed5ee0e..d078a61 100644
--- a/doc/gnuastro.en.html
+++ b/doc/gnuastro.en.html
@@ -86,9 +86,9 @@ for entertaining and easy to read real world examples of using
 
 <p>
   The current stable release
-  is <a href="http://ftp.gnu.org/gnu/gnuastro/gnuastro-0.11.tar.gz";>Gnuastro
-  0.11</a> (November 25th, 2019).
-  Use <a href="http://ftpmirror.gnu.org/gnuastro/gnuastro-0.11.tar.gz";>a
+  is <a href="http://ftp.gnu.org/gnu/gnuastro/gnuastro-0.12.tar.gz";>Gnuastro
+  0.12</a> (May 20th, 2020).
+  Use <a href="http://ftpmirror.gnu.org/gnuastro/gnuastro-0.12.tar.gz";>a
   mirror</a> if possible.
 
   <!-- Comment the test release notice when the test release is not more
@@ -99,7 +99,7 @@ for entertaining and easy to read real world examples of using
   To stay up to date, please subscribe.</p>
 
 <p>For details of the significant changes in this release, please see the
-  <a 
href="https://git.savannah.gnu.org/cgit/gnuastro.git/plain/NEWS?id=gnuastro_v0.11";>NEWS</a>
+  <a 
href="https://git.savannah.gnu.org/cgit/gnuastro.git/plain/NEWS?id=gnuastro_v0.12";>NEWS</a>
   file.</p>
 
 <p>The
@@ -275,11 +275,13 @@ mailing list for advice.</p>
 
 <dl>
 
+<!--
 <dt>Google Summer of Code 2020</dt>
 
 <dd>Gnuastro has some <a 
href="https://www.gnu.org/software/soc-projects/ideas-2020.html#gnuastro";>suggested
 projects</a> for Google Summer of Code (GSoC) 2020.
   Generally, if you are interested in any of the Gnuastro <a 
href="https://savannah.gnu.org/task/?group=gnuastro";>open tasks</a> for the 
GSoC please get in touch.
   We are also open to any new suggestion to contribute to Gnuastro through 
GSoC 2020.</dd>
+-->
 
 <dt>Test releases</dt>
 
diff --git a/doc/gnuastro.fr.html b/doc/gnuastro.fr.html
index 619360f..e7db1b1 100644
--- a/doc/gnuastro.fr.html
+++ b/doc/gnuastro.fr.html
@@ -85,15 +85,15 @@ h3 { clear: both; }
 <h3 id="download">Téléchargement</h3>
 
 <p>La version stable actuelle
-  est <a href="https://ftp.gnu.org/gnu/gnuastro/gnuastro-0.11.tar.gz";>Gnuastro
-  0.11</a> (sortie le 25 novembre
-  2019). Utilisez <a 
href="https://ftpmirror.gnu.org/gnuastro/gnuastro-0.11.tar.gz";>un
+  est <a href="https://ftp.gnu.org/gnu/gnuastro/gnuastro-0.12.tar.gz";>Gnuastro
+  0.12</a> (sortie le 20 mai
+  2020). Utilisez <a 
href="https://ftpmirror.gnu.org/gnuastro/gnuastro-0.12.tar.gz";>un
   miroir</a> si possible.  <br />Les nouvelles publications sont annoncées
   sur <a 
href="https://lists.gnu.org/mailman/listinfo/info-gnuastro";>info-gnuastro</a>.
   Abonnez-vous pour rester au courant.</p>
 
 <p>Les changements importants sont décrits dans le
-  fichier <a 
href="https://git.savannah.gnu.org/cgit/gnuastro.git/plain/NEWS?id=gnuastro_v0.11";>
+  fichier <a 
href="https://git.savannah.gnu.org/cgit/gnuastro.git/plain/NEWS?id=gnuastro_v0.12";>
   NEWS</a>.</p>
 
 <p>Le lien
diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index e3748a4..0f05717 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -1424,6 +1424,7 @@ Floriane Leclercq,
 Alan Lefor,
 Sebasti@'an Luna Valero,
 Guillaume Mahler,
+Raphael Morales,
 Juan Molina Tobar,
 Francesco Montanari,
 Dmitrii Oparin,
@@ -9359,7 +9360,7 @@ Concatenate/add the columns of this option's value (a 
filename) with the main in
 The concatenation is done after any column selection (for example with 
@option{--column}) or row selection (for example with @option{--range}) is 
applied to the main input argument.
 
 If the file given to this option is a FITS file, its necessary to also define 
the corresponding HDU/extension with @option{--catcolhdu}.
-Also note that no column or row selection is applied to the table given to 
this topion.
+Also note that no column or row selection is applied to the table given to 
this option.
 This option may be called multiple times (to add columns from more than one 
file into the final output), the columns will be added in the same order that 
this option is called.
 
 @item -u STR/INT
@@ -9898,7 +9899,7 @@ In such cases, it is best to crop out the larger region 
you want, then mask the
 
 @item --polygonsort
 Sort the given set of vertices to the @option{--polygon} option.
-For a concave polyton it will sort the vertices correctly, however for a 
convex polygon it there is no unique sorting, so be careful because the crop 
may not be what you expected.
+For a concave polygon it will sort the vertices correctly, however for a 
convex polygon it there is no unique sorting, so be careful because the crop 
may not be what you expected.
 
 @cindex Convex polygons
 @cindex Concave polygons
@@ -9906,7 +9907,7 @@ For a concave polyton it will sort the vertices 
correctly, however for a convex
 @cindex Polygons, Concave
 Polygons come in two classes: convex and concave (or generally, non-convex!), 
see below for a demonstration.
 Convex polygons are those where all inner angles are less than 180 degrees.
-By contrast, a convex polygon is one where an inner angle may be more than 180 
degress.
+By contrast, a convex polygon is one where an inner angle may be more than 180 
degrees.
 
 @example
             Concave Polygon        Convex Polygon
@@ -15581,7 +15582,7 @@ $ awk '!/^#/' out_c.txt | sort -g -k1,1 -k2,2
 @end example
 
 @item --sfmagnsigma=FLT
-Value to multiply with the median standard deviation (from a @command{MEDSTD} 
keyword in the Sky standard deviation image) for estimating the surface 
brightenss limit.
+Value to multiply with the median standard deviation (from a @command{MEDSTD} 
keyword in the Sky standard deviation image) for estimating the surface 
brightness limit.
 Note that the surface brightness limit is only reported when a standard 
deviation image is read, in other words a column using it is requested (for 
example @option{--sn}) or @option{--forcereadstd} is called.
 
 This value is a per-pixel value, not per object/clump and is not found over an 
area or aperture, like the common @mymath{5\sigma} values that are commonly 
reported as a measure of depth or the upper-limit measurements (see 
@ref{Quantifying measurement limits}).
@@ -21342,7 +21343,7 @@ Parse @code{fitsdate} as a FITS date format string 
(most generally: @code{YYYY-M
 Therefore it needs to be freed afterwards (if it isn't @code{NULL})
 When there is no sub-second portion, this pointer will be @code{NULL}.
 
-This is a relatively low-level function, an easier function to use is 
@code{gal_fits_key_date_to_seconds} which will return the subseconds as double 
precision floating point.
+This is a relatively low-level function, an easier function to use is 
@code{gal_fits_key_date_to_seconds} which will return the sub-seconds as double 
precision floating point.
 
 Note that the FITS date format mentioned above is the most complete 
representation.
 The following two formats are also acceptable: @code{YYYY-MM-DDThh:mm:ss} and 
@code{YYYY-MM-DD}.
@@ -21719,7 +21720,7 @@ under the same name in @ref{Generic data container}.
 Each column will have @code{numrows} rows and @code{colinfo} contains any
 further information about the columns (returned by
 @code{gal_fits_tab_info}, described above). Note that this is a low-level
-function, so the output data linked list is the inverse of the input indexs
+function, so the output data linked list is the inverse of the input indexes
 linked list. It is recommended to use @code{gal_table_read} for generic
 reading of tables, see @ref{Table input output}.
 @end deftypefun
@@ -21832,7 +21833,7 @@ It is recommended to use @code{gal_table_read} for 
generic reading of tables in
 
 @deftypefun {gal_data_t *} gal_txt_image_read (char @code{*filename}, 
gal_list_str_t @code{*lines}, size_t @code{minmapsize}, int @code{quietmmap})
 Read the 2D plain text dataset in file (@code{filename}) or list of strings 
(@code{lines}) into a dataset and return the dataset.
-If the necessaryspace for the image is larger than @code{minmapsize}, don't 
keep it in the RAM, but in a file on the HDD/SSD.
+If the necessary space for the image is larger than @code{minmapsize}, don't 
keep it in the RAM, but in a file on the HDD/SSD.
 For more on @code{minmapsize} and @code{quietmmap}, see the description under 
the same name in @ref{Generic data container}.
 
 @code{lines} is a list of strings with each node representing one line 
(including the new-line character), see @ref{List of strings}.
diff --git a/doc/release-checklist.txt b/doc/release-checklist.txt
index 1b8073c..61641c5 100644
--- a/doc/release-checklist.txt
+++ b/doc/release-checklist.txt
@@ -35,7 +35,7 @@ all the commits needed for this release have been completed.
 
        $ git checkout master
        $ git tag -d debian/$ver-1
-       $ git reset --hard HEAD~1        # To go to the merge with upstream.
+       $ git reset --hard HEAD~1            # To go to the merge with upstream.
        $ git reset --hard HEAD~1            # To go to last Debian release.
        $ git checkout pristine-tar
        $ git reset --hard HEAD~1



reply via email to

[Prev in Thread] Current Thread [Next in Thread]