Skip to content

Latest commit

 

History

History
35 lines (25 loc) · 2.54 KB

CONTRIBUTING.md

File metadata and controls

35 lines (25 loc) · 2.54 KB
Raw

This project is governed by a Code of Conduct.

General gist

Before writing any code, please open an issue, or let's have a discussion about any features or ideas that you may have.

No-nos! Saying this upfront, please do not upgrade any NuGet dependencies and please do not modify any licensing information and please do not update the copyright year. I have strong opinions on how I like these to be managed.

Okay, once you have discussed an idea or feature... it's hacking time!

  1. Fork it
  2. Branch it
  3. Hack it
  4. Save it
  5. Commit it
  6. Push it
  7. Pull-request it

The above is respectively taken from the Clearwater framework repository.
Kudos to Jamie Gaskins for succinctly framing the process.

Branching information

Given there are now multiple versions of Contentment that support multiple versions of Umbraco, please make note of the branching structure.

  • The main develop branch is where the latest work happens. This defaults to the most recent version of Contentment, (at the time of writing, this is v3.x).
  • The dev/v1.x branch is for Contentment v1.4.x patch releases, this targets Umbraco v8.6.1.
  • The dev/v2.x branch is for Contentment v2.2.x patch releases, this targets Umbraco v8.14.0.
  • The dev/v3.x branch is for Contentment v3.4.x patch releases, this targets both Umbraco v8.17.0 and v9.0.0.
  • The dev/v4.x branch is for Contentment v4.6.x releases, this targets Umbraco v8.17.0, v9.5.0, v10.0.0, v11.0.0, v12.0.0 and v13.0.0.
  • The dev/v5.x branch is for Contentment v5.x (current) releases, this will target Umbraco v13.2.0 only.
  • The dev/v6.x branch will be for Contentment v6.x (next) releases, this will target Umbraco v14.0.0.
  • The dev/v7.x branch will be for Contentment v7.x (future) releases, this may target Umbraco v14.0.0, v15.0.0, v16.0.0 and v17.0.0.