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

Merge develop into master #9

Closed
texdc opened this issue Nov 10, 2014 · 1 comment
Closed

Merge develop into master #9

texdc opened this issue Nov 10, 2014 · 1 comment

Comments

@texdc
Copy link
Contributor

texdc commented Nov 10, 2014

I know I initially requested it, but I think it's overkill to have the develop branch. It's really only necessary for projects with lots of changes. Since I renamed the class and reorganized things for PSR-4 autoloading, I wanted to get the changes reviewed before releasing. I would like for it to be tested in a staging environment before tagging a release, but master should be sufficient for that.
@texdc texdc closed this as completed Oct 5, 2017
@chrismetcalf
Copy link
Contributor

Awesome, thanks, and sorry for the delay!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chrismetcalf @texdc