Commit 52fc164d authored by Jure's avatar Jure

docs: clarify maintainer role and add release docs

parent 096cc68e
PubSweet consists of many software packages maintained by its community. Contributions are welcome and accepted from anyone, and there is additionally a group of people, that can also accept merge requests and do releases of PubSweet - we call them... :drum: :drum:... :rocket: **"THE MAINTAINERS"** :rocket:
PubSweet consists of many software packages maintained by its community. Contributions are welcome from anyone, and discussed with the community as a whole before being accepted.
Additionally, there is a group of people, that can accept merge requests and do releases of PubSweet - we call them... :drum: :drum:... :rocket: **"THE MAINTAINERS"** :rocket:
Here they are in alphabetical order:
......@@ -7,4 +9,4 @@ Here they are in alphabetical order:
- Jure Triglav @jure (Coko)
- Peter Hooper @diversemix (eLife)
*This summer. Four keyboards, one mission. No bug is safe, no documentation outdated.*
\ No newline at end of file
_This summer. Four keyboards, one mission. No bug is safe, no documentation outdated._
......@@ -39,3 +39,7 @@ Before merging, all MRs must fulfill these three simple rules:
1. It must pass the tests.
2. It must not reduce the test coverage.
3. If the MR is a bug fix, it must include a regression test.
# Releases
Releases are done with a `lerna publish` command from the main `pubsweet/pubsweet` repository. This releases all packages (about 50 of them) with the 'latest' tag on npm. Should you wish to do a release using a different tag (e.g. a prerelease with the 'next' tag), you can use e.g. `lerna publish --dist-tag next`. Be careful with releses!
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment