cszcms.com - Contribute

CSZ CMS | Contribute | CSZ CMS Official Website

Cszcms.com Spined HTML

CSZ CMS | Contribute | CSZ CMS Official Website Toggle navigation HomeDocs Product DownloadDemoArticleGalleryBlog About About UsContributeContact Us Contribute!=================================== Contributing to CSZCMS Project =================================== About ===== This document provides a set of weightier practices for CSZCMS contributions - bug reports, lawmaking submissions / pull requests, etc. Submitting bugs =============== Due diligence ------------- Before submitting a bug, please do the following: * Perform **basic troubleshooting** steps: * **Make sure you're on the latest version.** If you're not on the most recent version, your problem may have been solved already! Upgrading is unchangingly the weightier first step. * **Try older versions.** If you're once *on* the latest release, try rolling when a few minor versions (e.g. if on 4.0.x, try 3.3.x) and see if the problem goes away. This will help the devs narrow lanugo when the problem first arose in the commit log. * **Search the project's bug/issue tracker** to make sure it's not a known issue. * If you don't find a pre-existing issue, consider **checking with the user forums** in specimen the problem is non-bug-related. What to put in your bug report ------------------------------ Make sure your report gets the sustentation it deserves: bug reports with missing information may be ignored or punted when to you, delaying a fix. The unelevated constitutes a yellowish minimum; increasingly info is scrutinizingly unchangingly better: * **What version of PHP/MySQL/Apache are you using?** * **Which version or versions of the software are you using?** Ideally, you followed the translating whilom and have ruled out (or verified that the problem exists in) a few variegated versions. * **How can the developers recreate the bug on their end?** If possible, include a reprinting of your code, or reproduce the steps in details, etc. * A worldwide tactic is to pare lanugo your lawmaking until a simple (but still bug-causing) "base case" remains. Not only can this help you identify problems which aren't real bugs, but it ways the developer can get to fixing the bug faster. Contributing changes ==================== Version tenancy branching ------------------------- * Use ``develop`` workshop for development, don't use ``master`` branch. We reserve master workshop for well-spoken releases & tags. *Unchangingly**make a new branch** for your work, no matter how small. This makes it easy for others to take just that one set of changes from your repository, in specimen you have multiple unrelated changes floating around. * A corollary: **don't submit unrelated changes in the same branch/pull request**! The maintainer shouldn't have to reject your superstitious bugfix considering the full-length you put in with it needs increasingly review. * **Base your new workshop off of the towardly branch** on the main repository: * **Bug fixes** should be based on the workshop named without the **oldest supported release line** the bug affects. * E.g. if a full-length was introduced in 3.3, the latest release line is 4.0, and a bug is found in that full-length - make your workshop based on 3.3. The maintainer will then forward-port it to 4.0 and master. * Bug fixes requiring large changes to the lawmaking or which have a endangerment of stuff otherwise disruptive, may need to wiring off of **develop** instead. This is a judgement undeniability -- ask the devs! * **New features** should workshop off of **the 'master' branch**. * Note that depending on how long it takes for the dev team to merge your patch, the reprinting of ``develop`` you worked off of may get out of date! If you find yourself 'bumping' a pull request that's been sidelined for a while, **make sure you rebase or merge to latest master** to ensure a speedier resolution.Lawmakingformatting --------------- * **Follow the style you see used in the primary repository**! Consistency with the rest of the project unchangingly trumps other considerations. It doesn't matter if you have your own style or if the rest of the lawmaking breaks with the greater polity - just follow along. English ไทย Build © 2016 - 2019 CSKAZA.Sitemap | License Powered by CSZ CMS Version 1.2.1 English ไทย Build © 2016 - 2019 CSKAZA.Sitemap | License Powered by CSZ CMS Version 1.2.1