|
6 | 6 |
|
7 | 7 | This document outlines our project management processes for REST framework. |
8 | 8 |
|
9 | | -The aim is to ensure that the project has a high |
| 9 | +The aim is to ensure that the project has a high |
10 | 10 | ["bus factor"][bus-factor], and can continue to remain well supported for the foreseeable future. Suggestions for improvements to our process are welcome. |
11 | 11 |
|
12 | 12 | --- |
@@ -38,27 +38,27 @@ Members of the maintenance team will be added as collaborators to the repository |
38 | 38 | The following template should be used for the description of the issue, and serves as the formal process for selecting the team. |
39 | 39 |
|
40 | 40 | This issue is for determining the maintenance team for the *** period. |
41 | | - |
| 41 | + |
42 | 42 | Please see the [Project management](http://www.django-rest-framework.org/topics/project-management/) section of our documentation for more details. |
43 | | - |
| 43 | + |
44 | 44 | --- |
45 | | - |
| 45 | + |
46 | 46 | #### Renewing existing members. |
47 | | - |
| 47 | + |
48 | 48 | The following people are the current maintenance team. Please checkmark your name if you wish to continue to have write permission on the repository for the *** period. |
49 | | - |
| 49 | + |
50 | 50 | - [ ] @*** |
51 | 51 | - [ ] @*** |
52 | 52 | - [ ] @*** |
53 | 53 | - [ ] @*** |
54 | 54 | - [ ] @*** |
55 | | - |
| 55 | + |
56 | 56 | --- |
57 | | - |
| 57 | + |
58 | 58 | #### New members. |
59 | | - |
| 59 | + |
60 | 60 | If you wish to be considered for this or a future date, please comment against this or subsequent issues. |
61 | | - |
| 61 | + |
62 | 62 | To modify this process for future maintenance cycles make a pull request to the [project management](http://www.django-rest-framework.org/topics/project-management/) documentation. |
63 | 63 |
|
64 | 64 | #### Responsibilities of team members |
@@ -116,7 +116,7 @@ The following template should be used for the description of the issue, and serv |
116 | 116 | - [ ] Make a release announcement on the [discussion group](https://groups.google.com/forum/?fromgroups#!forum/django-rest-framework). |
117 | 117 | - [ ] Make a release announcement on twitter. |
118 | 118 | - [ ] Close the milestone on GitHub. |
119 | | - |
| 119 | + |
120 | 120 | To modify this process for future releases make a pull request to the [project management](http://www.django-rest-framework.org/topics/project-management/) documentation. |
121 | 121 |
|
122 | 122 | When pushing the release to PyPI ensure that your environment has been installed from our development `requirement.txt`, so that documentation and PyPI installs are consistently being built against a pinned set of packages. |
@@ -165,7 +165,7 @@ Here's how differences between the old and new source files will be handled: |
165 | 165 | When a translator has finished translating their work needs to be downloaded from Transifex into the REST framework repository. To do this, run: |
166 | 166 |
|
167 | 167 | # 3. Pull the translated django.po files from Transifex. |
168 | | - tx pull -a |
| 168 | + tx pull -a --minimum-perc 10 |
169 | 169 | cd rest_framework |
170 | 170 | # 4. Compile the binary .mo files for all supported languages. |
171 | 171 | django-admin.py compilemessages |
|
0 commit comments