[FOLIO-594] document release procedure for Gradle-based projects Created: 09/May/17 Updated: 12/Nov/18 Resolved: 11/May/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | Marc Johnson |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint14 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
Integrate this with the release procedures document (see
|
| Comments |
| Comment by Marc Johnson [ 10/May/17 ] |
|
David Crossley Jakub Skoczen Adam Dickmeiss I've made an initial attempt at describing the release process for Gradle modules in this [branch](https://github.com/folio-org/folio-org.github.io/pull/43). All feedback welcome (on either the documentation or the process itself), in particular whether the approach to reference the maven procedure (what I've currently done) is preferable to duplicating much of the content. Hugs |
| Comment by David Crossley [ 11/May/17 ] |
|
Doc is great. Merged. I reckon referencing the other, as you have done, is the better approach. |