You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: v2-community/README.md
+22-3Lines changed: 22 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -266,6 +266,18 @@ Should you wish to build Phaser from source you can take advantage of the provid
266
266
267
267
Run `grunt` to perform a default build to the `dist` folder.
268
268
269
+
### Packaging a new release
270
+
271
+
Releases of new versions of Phaser CE are under the communities control. If you feel there are sufficient fixes, or important ones that warrant a new version release, then please do the following:
272
+
273
+
1. Make sure the version number is increased, in line with semver policies, in the following files: `package.json` and `src/Phaser.js`
274
+
275
+
2. Make sure that you have added details of the new version to the `README.md` and `CHANGELOG.md`. This should include a summary of changes made in the version. You can usually obtain this from the commit / PR history. It's nice to credit who made the changes by linking to their GitHub user ID, but isn't a requirement.
276
+
277
+
3. From the root of the `v2-community` folder, run `grunt jshint` and make sure there are no jshint errors. If there are, please fix them, or request that the original author of the code does so.
278
+
279
+
4. Once jshint passes run `grunt release`, sit back, and wait. It will build all of the versions of Phaser required, update the doc files, TypeScript defs and lots more. When finished, commit all of the new files and make sure to include a clear message in your commit saying you want this release pushed to npm. Be sure to tag me when doing this, i.e. 'Phaser CE Version 2.X.X. Please publish to npm @photonstorm' - I'll see it, and then publish as soon as I can (often the same day).
280
+
269
281

270
282
<aname="games"></a>
271
283
@@ -314,6 +326,13 @@ If you code with [TypeScript](http://www.typescriptlang.org/) there are comprehe
* Added tempPoint argument / undefined block to Graphics.containsPoint
333
+
* Fixed Text.setCharacterLimit conditional check
334
+
* Added resolution argument to LoaderParser.jsonBitmapFont
335
+
317
336
## Version 2.7.2 - 6th December 2016
318
337
319
338
### New Features
@@ -432,11 +451,11 @@ The [Contributors Guide][contribute] contains full details on how to help with P
432
451
433
452
- Found a bug? Report it on [GitHub Issues][issues] and include a code sample.
434
453
435
-
- Pull Requests should only be made against the `dev` branch. *Never* against `master`.
454
+
- Pull Requests should only be made against the `v2-community` folder version of Phaser, never `v2`.
436
455
437
-
- Before submitting a Pull Request run your code through [JSHint](http://www.jshint.com/) using our [config](https://github.com/photonstorm/phaser/blob/master/.jshintrc).
456
+
- Before submitting a Pull Request run your code through [JSHint](http://www.jshint.com/) using our [config](https://github.com/photonstorm/phaser/blob/master/v2-community/.jshintrc).
438
457
439
-
- Before contributing read the [code of conduct](https://github.com/photonstorm/phaser/blob/master/CODE_OF_CONDUCT.md).
458
+
- Before contributing read the [code of conduct](https://github.com/photonstorm/phaser/blob/master/v2-community/CODE_OF_CONDUCT.md).
440
459
441
460
Written something cool in Phaser? Please tell us about it in the [forum][forum], or email support@phaser.io
0 commit comments