[MXS-298] Please tag in git your release versions and provide better linking to the download locations Created: 2015-07-31 Updated: 2017-12-01 Resolved: 2016-01-05 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Documentation |
| Affects Version/s: | 1.2.1 |
| Fix Version/s: | 1.3.0 |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Simon J Mudd | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
It is convenient to be able to check the source for a given built package. I see there is a link to the new MaxScale 1.2 release here: https://mariadb.com/kb/en/mariadb-enterprise/mariadb-maxscale/mariadb-maxscale-12-release-notes/ but it's not clear exactly how you are labelling these versions. I know the software is relatively new but being precise for this later is quite convenient. I notice in github.com that there's a 1.2.0 tag so I assume that this is the same version. Making your documentation clearer about this would be good, as I imagine that bug fixes may come out later for 1.2, so it would be good to be able to easily distinguish minor version differences. Also I see references to the binary packages you are currently building but there are no links from this page to where the software can be downloaded. That requires me to poke about to find it. Perhaps it might be possible to change these references to links to the appropriate download page(s)? |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2015-08-04 ] |
|
In the releases notes we should add a link to github branch of the source code for the release. |
| Comment by Timofey Turenko [ 2015-08-12 ] |
|
markus makela could you please add comments to Release Notes? |
| Comment by Johan Wikman [ 2016-01-05 ] |
|
The release note contains now a link to the source code at GitHub and a link to mariadb.com where packages can be downloaded. |