Replies: 3 comments 3 replies
-
As a suggestion, unless you intend to take on the extra workload of maintaining a stable version, you don't need to create a stable branch. Just do Releases off the main or master branch. |
Beta Was this translation helpful? Give feedback.
-
An initial Release Candidate for v3.4 has been published as a Development Snapshot. It is available on the Releases page or via the dev branch. If you design or distribute hardware that runs RomWBW, this would be a good release to use to confirm that v3.4 is working on your hardware. Thanks, Wayne |
Beta Was this translation helpful? Give feedback.
-
Closing this discussion since v3.4 has been released! |
Beta Was this translation helpful? Give feedback.
-
Hi all,
I am in the process of finalizing a new stable release of RomWBW (v3.4.0). I intend to publish this release by the new year. If anyone has any issues or contributions that you want considered for this release, please contact me ASAP or reply in this discussion.
NOTE: I will be changing the branch conventions when this release is published. Currently, the master branch is the latest stable version of the code and the dev branch is used for development. I will be changing to using master for development and will create a branch called stable for the latest stable release. This is more consistent with typical repository conventions. I will be removing the dev branch at some point.
Thanks!
Wayne
Beta Was this translation helpful? Give feedback.
All reactions