-
Notifications
You must be signed in to change notification settings - Fork 126
Home
Devkit2 is ready for public use! Devkit2 is a massive upgrade over Devkit1, particularly in its ability to support long term maintenance of multiple games. Most significantly, Devkit2 revamps the dependency system so that every application has its own local copy of the devkit runtime and any modules (formerly called addons) it requires. This means you can explicitly manage dependencies between applications without changing what is available on your entire system.
Check out the milestones list for the current set of development priorities.
To facilitate fixing as many issues as possible, we are going to implement some light structure for issue tracking, including a detailed tagging system to help keep things organized. Issues with solid reproductions (platform info, commands, necessary files/code, etc) will be prioritized and 'stale' issues (no repro, no contact from OP or other users) will be closed.
Everyone should contribute to the issue list if they have information - adding extra details, additional reproductions, or just sharing insight is extremely helpful. Additionally, everyone should feel free to help with curating the issue list and submitting patches for them. If you are tackling an issue, consider commenting about your progress so others don't duplicate your effort.
For the moment we are adopting the AngularJS Commit message format as a whole. This will make our commit history easy to quickly understand and will allow automatically generating change logs.
NOTE: this will almost certainly be amended/replaced soon
The help wanted page lists particular priorities for the current development cycle. Contributing patches for these topics will be the most effective way to move Devkit2 forward.
The requirements for contributing to Devkit2 are the same as for the original devkit release - please review the information there to sign the necessary CLAs.
We will do our absolute best to review pull requests and get fixes merged in to the current codebase. Pull requests that are concise, well-documented, and relevant to the current development targets are the most likely to get merged in. All commit messages must follow the correct format - see the 'Commit Message Policy' section above for details.