|
@@ -48,9 +48,9 @@ getting free help.
|
48
|
48
|
|
49
|
49
|
## Discuss your design
|
50
|
50
|
|
51
|
|
-The project welcomes submissions. If you want to change or add something,
|
52
|
|
-please let everyone know what you're working on—[file an issue](https://github.com/go-gitea/gitea/issues/new)!
|
53
|
|
-Significant changes must go through the change proposal process
|
|
51
|
+The project welcomes submissions. If you want to change or add something,
|
|
52
|
+please let everyone know what you're working on—[file an issue](https://github.com/go-gitea/gitea/issues/new)!
|
|
53
|
+Significant changes must go through the change proposal process
|
54
|
54
|
before they can be accepted. To create a proposal, file an issue with
|
55
|
55
|
your proposed changes documented, and make sure to note in the title
|
56
|
56
|
of the issue that it is a proposal.
|
|
@@ -69,8 +69,8 @@ and keep the compatibility on upgrade. To make sure you are
|
69
|
69
|
running the test suite exactly like we do, you should install
|
70
|
70
|
the CLI for [Drone CI](https://github.com/drone/drone), as
|
71
|
71
|
we are using the server for continous testing, following [these
|
72
|
|
-instructions](http://readme.drone.io/usage/getting-started-cli). After that,
|
73
|
|
-you can simply call `drone exec` within your working directory and it will try
|
|
72
|
+instructions](http://readme.drone.io/usage/getting-started-cli). After that,
|
|
73
|
+you can simply call `drone exec` within your working directory and it will try
|
74
|
74
|
to run the test suite locally.
|
75
|
75
|
|
76
|
76
|
## Vendoring
|
|
@@ -100,7 +100,7 @@ Generally, the go build tools are installed as-needed in the `Makefile`.
|
100
|
100
|
An exception are the tools to build the CSS and images.
|
101
|
101
|
|
102
|
102
|
- To build CSS: Install [Node.js](https://nodejs.org/en/download/package-manager)
|
103
|
|
- with `npm` and then run `npm install` and `make stylesheets`.
|
|
103
|
+ with `npm` and then run `npm install` and `make generate-stylesheets`.
|
104
|
104
|
- To build Images: ImageMagick, inkscape and zopflipng binaries must be
|
105
|
105
|
available in your `PATH` to run `make generate-images`.
|
106
|
106
|
|
|
@@ -111,7 +111,7 @@ makes the change, even if they are an owner or a maintainer. We use GitHub's
|
111
|
111
|
pull request workflow to do that. And, we also use [LGTM](http://lgtm.co)
|
112
|
112
|
to ensure every PR is reviewed by at least 2 maintainers.
|
113
|
113
|
|
114
|
|
-Please try to make your pull request easy to review for us. And, please read
|
|
114
|
+Please try to make your pull request easy to review for us. And, please read
|
115
|
115
|
the *[How to get faster PR reviews](https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#best-practices-for-faster-reviews)* guide;
|
116
|
116
|
it has lots of useful tips for any project you may want to contribute.
|
117
|
117
|
Some of the key points:
|
|
@@ -174,11 +174,11 @@ obtain a final version that is maintained in this branch. A release is
|
174
|
174
|
maintained by issuing patch releases to only correct critical problems
|
175
|
175
|
such as crashes or security issues.
|
176
|
176
|
|
177
|
|
-Major release cycles are bimonthly. They always begin on the 25th and end on
|
178
|
|
-the 24th (i.e., the 25th of December to February 24th).
|
|
177
|
+Major release cycles are bimonthly. They always begin on the 25th and end on
|
|
178
|
+the 24th (i.e., the 25th of December to February 24th).
|
179
|
179
|
|
180
|
|
-During a development cycle, we may also publish any necessary minor releases
|
181
|
|
-for the previous version. For example, if the latest, published release is
|
|
180
|
+During a development cycle, we may also publish any necessary minor releases
|
|
181
|
+for the previous version. For example, if the latest, published release is
|
182
|
182
|
v1.2, then minor changes for the previous release—e.g., v1.1.0 -> v1.1.1—are
|
183
|
183
|
still possible.
|
184
|
184
|
|