-
Epic
-
Resolution: Not a Bug
-
Critical
-
None
-
2.9 GA
-
None
-
None
-
implement agile workflow in Github
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
To Do
-
0% To Do, 0% In Progress, 100% Done
Delivering of developed changes should be changed because of:
- more focus on delivering to Saas-like environments
- smaller release cycles
- and other upcoming changes(more inter-project integration).
All changes(bug fixes, new features) should be tested and documented(if needed) before they are merged into GIT branch determined as source for release candidate images.
Simple example:
- release frequency for Saas-like deployment X is 3 weeks(at the end of every sprint)
- 3scale images are built from GIT branch A and delivered to X QE team for integration testing
- there are just changes already tested by 3scale QE and documented by 3scale documentation team(if needed) in GIT branch A
All above requirements and goals can be achieved only if there is working and effective workflow in GIT for delivering changes to 3scale QE before changes are merged to branch A.