-
- [ ] (DEV) Close or defer all tickets in the epics (code complete/scope closure) - code freeze
- [ ] (DEV) Create release candidate branch (branching, tagging)
- [ ] (Business Owner) Identify de…
-
Documentation checklist to prepare for and deliver the ansible-core 2.18 release. See follow-on comment for the full checklist.
-
I think we should revise our release checklist:
- Mark 90%+ things for automation and start implementing
- Remove things we barely ever do (cpplint?)
- Deprecate things (upload to Sourceforge?)
-
It would be very useful to be able use Vexl feature also as ouside of chat with copy / paste table so We can move from Vexl to other chat applications.
-
Fbuild hasn't had a release in years. It's time for that to change!!
- [ ] Make sure MinGW works again.
- [ ] Clean up the flags vs cflags vs lflags debacle.
- [x] ~~Add the ability to add flags …
-
JIRA Issue: [KIEKER-328] Additional automation in release creation process
Original Reporter: Andre van Hoorn
***
E.g.,
Step 6 (Download all release files) of wiki:DevGuide#CreatingaRelease, i.e…
-
- [x] theme 3
- [x] clean up theme 4
- [x] victory theme
- [ ] clean up hint text timing
- [x] better two-line intro text
- [ ] make release version
-
Issue to track tasks necessary pre/post release of occ variant.
All checklists in comments below should be ticked before / immediately after release.
-
1. Smoke testing
- [x] Setup Account
- [x] Send
- [ ] Up-selling
- [x] Change Token
- [x] My Account
- [ ] Pin Options
- [ ] Help
2. Other
- [ ] Translations
- [ ] Voucher Lists Render…
-
It would be nice to have a standardized release checklist that is available to all SpinKube contributors.