Skip to content

Commit 231cd8c

Browse files
committed
Release 2019.3: updates to release notes and procedures
1 parent c63eca4 commit 231cd8c

File tree

2 files changed

+27
-13
lines changed

2 files changed

+27
-13
lines changed

docs/new-release-procedure.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,24 +4,24 @@
44

55
1. In the `rc-yyyy.x` branch, Edit the release notes and do the following:
66
- Modify the note for the unreleased version to remove the `(unreleased, current development)` from the title
7-
- After looking at tags make sure all the important changes are included in the notes.
7+
- After looking at docker tags make sure all the important changes are included in the notes.
88
- Start a new section for the next release, mark in the title with `(unreleased, current development)`
99
- Make sure you edit the docker tags section of this release
1010

1111
1. Merge and Push
1212
- merge the `rc-yyyy.m` branch back into `dev`
1313
- push both branches
1414

15-
1. Tag the `rc-yyyy.m` branch with the release `release-yyyy.m.r`
16-
- _example:_ the second release from branch `rc-2019.2` will the tagged with `release-2019.2.1`
15+
1. Git tag the `rc-yyyy.m` branch with the release `release-yyyy.m.r`
16+
- _example:_ the second release from branch `rc-2019.2` with the git tagged with `release-2019.2.1`
1717

1818
1. Push tags to GitHub: `git push origin --tags`
1919

20-
1. Build the docker with the following tags: `rc-yyyy.m`, `release-yyyy.m`,`release-yyyy.m.r`, `latest`
20+
1. Build the docker with the following docker tags: `rc-yyyy.m`, `release-yyyy.m`,`release-yyyy.m.r`, `latest`
2121
- _example:_ from the example above the release would be built with: `rc-2019.2`, `release-2019.2`,`release-2019.2.1`, `latest`
2222
- _notes:_
23-
- the `rc-yyyy.m` tag does not represent the release, it is just the most recent build of the branch
24-
- the `release-yyyy.m` tag always represents the latest release of the version
23+
- the `rc-yyyy.m` docker tag does not represent the release, it is just the most recent build of the branch
24+
- the `release-yyyy.m` docker tag always represents the latest release of the version
2525

2626
1. Go the the Firefly page on docker hub. https://cloud.docker.com/u/ipac/repository/docker/ipac/firefly
2727
- Edit the markdown to include the recent tags

docs/release-notes.md

Lines changed: 21 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,19 @@ Firefly builds and the notes for using running it are on the [Docker Page](https
44

55
See Firefly docker guidelines [here](firefly-docker.md).
66

7-
### Version 2019.3 (unreleased, current development)
7+
### Version 2019.4 (unreleased, current development)
88

9-
##### _General_
109
- docker tag: `nightly`
11-
- This release is focused on bug fixes and stability
10+
11+
### Version 2019.3
12+
13+
This release is focused on bug fixes and stability
14+
15+
##### _Docker tags, releases and patches_
16+
17+
- 2019.3 latest - `release-2019.3`
18+
- 2019.3.0 - `release-2019.3.0` - original release
19+
1220

1321
##### _UI_
1422
- New Table of loaded Images tool to control and order which images are displayed or hidden ([Firefly-175](https://github.com/Caltech-IPAC/firefly/pull/873))
@@ -20,10 +28,14 @@ See Firefly docker guidelines [here](firefly-docker.md).
2028
##### _API_
2129
- Plotly.js charting library was updated from version 1.38.3 to version 1.49.4. Plotly.js 1.43 converted `title` properties (e.g. `layout.title`) from strings into objects that contain `text` property along with new title placement properties `x`, `y`, `xref`, `yref`, `xanchor`, `yanchor` and `pad`. It also moved existing `title*` properties (e.g. `layout.titlefont`) under the `title` object (e.g. `layout.title.font`). See see [plotly.js change log](https://github.com/plotly/plotly.js/blob/master/CHANGELOG.md#1494----2019-08-22) for more information. ([Firefly-266](https://github.com/Caltech-IPAC/firefly/pull/883))
2230

31+
##### _Patches details for 2019.3_
32+
No patches
33+
2334

2435
### Version 2019.2
25-
##### _General_
26-
- docker tag: `release-2019.2.1`
36+
##### _Docker tags, releases and patches_
37+
38+
- 2019.2.1 - `release-2019.2.1` - only available 2019.2 release
2739

2840
##### _UI_
2941
- WCS Matching has have been completely revamped. ([Firefly-75](https://github.com/Caltech-IPAC/firefly/pull/825),[Firefly-173](https://github.com/Caltech-IPAC/firefly/pull/857))
@@ -36,8 +48,10 @@ See Firefly docker guidelines [here](firefly-docker.md).
3648
- nothing of interest
3749

3850
### Version 2019.1
39-
##### _General_
40-
- docker tag: `release-2019.1.0`
51+
52+
##### _Docker tags, releases and patches_
53+
54+
- 2019.1.0 - `release-2019.1.0` - original release
4155

4256
##### _UI_
4357
- TAP search Implemented (Multiple tickets and PRs)

0 commit comments

Comments
 (0)