meonkeys opened a new pull request, #5116:
URL: https://github.com/apache/fineract/pull/5116

   ## Description
   
   Docs updates. Stuff I've collected while releasing 1.13.0, and now 
submitting as a patch to improve the 1.14.0 release process (or 1.13.1).
   
   * release step 6: emphasize "re-run the command above"
   * release step 9: link to Database Setup in e2e or integration section 
(currently links to e2e since `cucumber.adoc` precedes `integration.adoc` in 
`fineract-doc/src/docs/en/chapters/testing/index.adoc`)
   * release step 10: improve rc verify instructions in voting email, based on 
https://lists.apache.org/thread/jk2qzjxc89hd1c8xzvhtmlbbj1m8ktbl - thread: 
"release process improvement (was: 🗳️  1.13.0 for release)"
   * release step 15: use current mission statement from top-level readme in 
release announcement email
   
   see also: FINERACT-2397
   
   ## Checklist
   
   Please make sure these boxes are checked before submitting your pull request 
- thanks!
   
   - [x] Write the commit message as per 
https://github.com/apache/fineract/#pull-requests
   - [x] Acknowledge that we will not review PRs that are not passing the build 
_("green")_ - it is your responsibility to get a proposed PR to pass the build, 
not primarily the project's maintainers.
   - [x] Create/update unit or integration tests for verifying the changes made.
   - [x] Follow coding conventions at 
https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.
   - [x] Add required Swagger annotation and update API documentation at 
fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with 
details of any API changes
   - [x] Submission is not a "code dump".  (Large changes can be made "in 
repository" via a branch.  Ask on the developer mailing list for guidance, if 
required.)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to