Repository (WP & GitHub)
Between WordPress and GitHub, there is a basic workflow. Majority of the development is first carried out on GitHub. Once a release candidate has been decided, a new version is uploaded to WordPress. The relation between the two is fundamental, but within GitHub's environment there is an essential workflow to reduce merge conflicts and keep development organized.
WP's dev environment may be limiting, but they do offer some support for those who are interested in looking into such essential matters.
- WP-APL Webpage
- Changelog
-
Developers
- SVN Log
- SVN Address
https://plugins.svn.wordpress.org/advanced-post-list/ - Trac Browser
Majority of the development activity will be on GitHub. Here are a few common links for those who are interested.
Workflow
APL follows a pretty simple Workflow for branches. The Master branch will always be a stable branch for version releases, which is commonly used to stage a release on WordPress. Both also serve as an outlet for public browsing.
There are also Version Branches for scenarios that require continued development for old version releases. Currently, there is no plan to continue development for old versions, and nor will there be, but for those that do continue old versions are more than welcome to submit a merge/pull request.
Additional branches may come and go depending on how development is being carried out. For more information on how APL follows these guideline can be found at A Successful Git Branching Model.
Wiki The knowledge base on GitHub is open for the public to add and modify content on the Wiki. This is in hopes to allow the Wiki to be more organic and helpful, and allow others who otherwise couldn't make contributions in terms of APL code.
If you have a question that you believe to be more frequent than isolated. Feel free to create a ticket with [Question] in the title and/or use the Label "T-Support/Question". More information, please check out Submit a Bug/Idea.