jaswrks
commented
8 years ago Referencing: https://github.com/websharks/wpsharks.com/issues/13
Closed jaswrks closed 8 years ago
jaswrks
commented
8 years ago Referencing: https://github.com/websharks/wpsharks.com/issues/13
An official release should always be accompanied by an automatic update of the latest bleeding edge as well. This way we avoid a scenario where the lead developer forgets to update the bleeding edge, resulting in the latest official release being more up-to-date than the latest bleeding edge is.
In short, when a new release is done, that should represent the latest bleeding edge as well. Then, a lead developer can choose to update the latest bleeding edge moving forward, without doing another official release; e.g., to do a soft release, of sorts, mostly for testing purposes.