-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
PSR-0 to PSR-4 change #35
Comments
Hi, I have started to work on this issue. |
@MadCat34 Thanks. |
thanks for the work @MadCat34 |
@matwright No worries. We are all busy with other projects. At the same time, going to PSR-4 changes the src directory structure. Anyone that has forked the repo, made changes and wants to sync with upstream will be in for a surprise... but I guess that if one forked it and made changes, then one has to be ready to deal with changes upstream. I think that we should make a 3.6 version. I would just hold a little bit such that we can include resolutions for some of the other issues like #40 and #39. Any thoughts |
Possibly include #31 in a 3.6 version? |
Yes, I'm leaning to a 3.6 version too. While this has backward breaking updates it isn't really cause for a major version release. |
As a somewhat related discussion, we need to start thinking of a version 4. I created issues in the LmcRbac and LmcRbacMvc to sollicit and track proposals for enhancements. I can do the same for LmcUser. |
Closed by #36 |
Need to change the directory structure from PSR-0 to PSR-4. @visto9259, please add a task list which in your experience needs to be fulfilled. I remember you mentioning about breaking of tests. Thanks!
The text was updated successfully, but these errors were encountered: