Documentation Process for next release
-
Transifex has the current release of the documentation.
- The "Current Release Documentation" (master) remains on Transifex until the new release candidate is ready.
- See details in Documentation Process for next release step 1
-
Developers work on the documentation for the next release using ReStructuredText:
- A Developer will create documentation of a "new function"
- A Developer will modify documentation of a "modified function" maybe because of changes in the functionality
- User's and translators findings of typos and grammar are posted on [Issue 200] (https://github.com/pgRouting/pgrouting/issues/200)
- An English reviewer will modify documentation for typos or grammar findings.
-
Preparing Transifex and github for the "next release candidate":
- Transifex managers download the "current release translations".
- Update github of the "current release" (master) with the latest translation.
- Documentation for the "next release" (develop) is uploaded into Transifex
- Transifex managers download the "next release translations".
- Update github of the "next release candidate" (develop?) with the latest translation.
-
Translators time for translating.
- Translation is performed while the release candidates are reviewed
- Translation Process
-
Preparing Transifex for the "next release":
- Transifex managers download the "next release translations".
- Update github of the "next release candidate" (develop?) with the latest translation.
-
"New Release" is announced
- Github managers perform the process for the release.
- pgRouting Release Process Checklist
- Current Translations Documentation Process for next release step 1
- English Documentation Documentation Process for next release step 2
- Preparing for Next release candidate Documentation Process for next release step 3
- Translating Documentation Process for next release step 4
- Preparing for Next release Documentation Process for next release step 5
