Bug 23161 - We need to document the release process for this project?
Summary: We need to document the release process for this project?
Status: NEW
Alias: None
Product: Project Infrastructure
Classification: Unclassified
Component: Mana-kb (server) (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-19 13:20 UTC by Martin Renvoize (ashimema)
Modified: 2019-06-19 13:20 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize (ashimema) 2019-06-19 13:20:32 UTC 
Right now I just have lots of questions:

1) What do we envisage the process for bugfixes being? (reported in gitlab or bugzilla or synced between the two?)
2) What do we envisage the process for enhancements being? (reported gitlab or bugzilla or synced between the two?)
3) Do we follow the same Testing/SO/QA process?
4) Are we running one and only one instance of Mana or are we running different versions in parallel to support the different koha versions that will be out there in the world?
5) Who is responsible for merging once a bug/enhancement has been given the go ahead?
6) When do releases happen (in step with Koha releases?)
7) What is our policy on breaking changes?
8) Should we have a deployment pipeline triggered via merges to master?