Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Bleeding Edge on Release #142

Closed
jaswrks opened this issue Aug 28, 2016 · 1 comment
Closed

Update Bleeding Edge on Release #142

jaswrks opened this issue Aug 28, 2016 · 1 comment
Labels
enhancement

Comments

@jaswrks
Copy link
Contributor

jaswrks commented Aug 28, 2016 •
edited
Loading

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.
@jaswrks
Copy link
Contributor Author

jaswrks commented Sep 1, 2016

Referencing: https://github.com/websharks/wpsharks.com/issues/13

jaswrks pushed a commit that referenced this issue Sep 1, 2016
Preparing pull request. See: #142
564f6a5
@jaswrks jaswrks mentioned this issue Sep 1, 2016
Merged
jaswrks pushed a commit that referenced this issue Sep 1, 2016
Automate bleeding edge on official release. See: #142
52dd86e
@jaswrks jaswrks closed this as completed Sep 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jaswrks