-
Notifications
You must be signed in to change notification settings - Fork 0
Project Guidelines
DaJoker29 edited this page Oct 12, 2013
·
4 revisions
- Dont' be stupid
- Keep things simple
- Shorter is better
To test a new release, follow the WordPress Theme Testing Guidelines in order. Any bugs and errors should be reported in the issue tracker.
All work should be done on a local fork. Feature branches will be where most work is done and then merged into development. After certain milestones, release branches will be created for debugging and testing for new minor or major release. After testing release branch will then be merged into master and development and the branch will be deleted.
Scheme: vX.Y.Z-build
example: v4.2.0-rc
- X = major release with change in overall compatiblity
- Y = minor release with features added or modified
- Z = patch release with bugfixes and minor enhancements
- build = stage of development if not stable and tested. (pre-alpha, alpha, beta, rc)
Scheme: versionNumber-build -- (codeName)
example: 4.2.0-release-candidate -- Arthur Dent
- versionNumber = X.Y.Z version number without preceding "v"
- build = Build stage used in version scheme, spelled out entirely
- codeName = major or minor release code name attached to project