Skip to content

Commit 337d517

Browse files
authored
remove issue text as we now have a template
1 parent 7077823 commit 337d517

File tree

1 file changed

+0
-18
lines changed

1 file changed

+0
-18
lines changed

doc/deployment/Creating-a-release.md

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -9,24 +9,6 @@
99
release/*
1010
```
1111

12-
## Understanding Java Licensing
13-
Make sure you [understand how Java is licensed](/processes/dev_processes/Understanding-Java-Licensing), so that we do not inadvertently make ISIS liable for licensing fees.
14-
15-
## Release tickets
16-
17-
Text for release ticket:
18-
19-
> As a developer I want an IBEX release so I can install it on the instrument machines for the start of machine physics on 26th.
20-
>
21-
> Acceptance Criteria:
22-
>
23-
> - [ ] [Pre Testing Steps](#creating_release_pre_testing_steps)
24-
> - [ ] [Testing steps](#creating_release_testing_steps)
25-
> - [ ] [Post Testing](#creating_release_post_testing_steps)
26-
> - [ ] [Create a ticket to update dependencies to latest versions and test](/processes/dev_processes/Dependency-Updates)
27-
> - [ ] [Create a ticket to give instrument demos](https://github.com/ISISComputingGroup/IBEX/wiki/Timetable-for-Instrument-Demos)
28-
> - [ ] Distribute release notes via email [Instrument scientist release email](#updating_instrument_new_release_email_template)
29-
3012
## Standard Release
3113

3214
Project is ready to be released not for a specific event, e.g. at the end of a sprint. Script Generator version number always differs to the client's.

0 commit comments

Comments
 (0)