Major version upgrade plan #488
Comments
|
we need this frr |
|
I'll set the release goal for the first week of Jan. Feel free to ping me obsessively if I don't! |
When is official release for bs5? |
|
After we tag 1.6, Tõnis will issue a PR for it. |
|
1.6.0 released, we can move forward. |
|
@TonisOrmisson how would you like to proceed? Shall I create a |
|
This is how I imagined it, yes. Any better ideas are welcome of course. BTW my bs5 version still lacks all changes in documentation. But if you create a new branch I will happily submit a PR there |
|
https://github.com/2amigos/yii2-usuario/tree/v2.0.0-dev So as for now I'll keep merging stable stuff into |
|
ok, seems I have a bit of an old state of views in my bs5 version so I'll recreate my bs5 changes on a fresh copy of views not to make a mess. Hope to submit that in a couple of days to this out to testing asap. |
|
Merge master to v2.0.0-dev @maxxer ? |
|
Done! |
|
Merge master to v2.0.0-dev @maxxer ? |
|
Done! |
|
I have started migrating my some projects to use with the new v2 and BS5 based views. So far no major issues. But a question to all of you. Since v2 is a major version change, I suggest also to drop support for php 7. Please do speak out loud if you oppose this :) Post an emoji to here for pro/con |
|
we have done most of the plan for preparing v2 release. How can we move forward? I suggest we should copy the current master branch to a new v1 branch and then merge the v2.0.0-dev into master if we are ready to do so. also we have an "old" usuario-2.0-dev branch that should be renamed to refer that it is basically an abandoned branch and not related to actual v2 Any ideas what would need to be done before merging? |
|
Merge master to v2.0.0-dev again @maxxer to keep in sync ? |
Bootstrap here is outdated, no releases lately make hard to implement breaking changes. I suggest a plan for getting past this
1. I have created a dev branch here:
https://github.com/TonisOrmisson/yii2-usuario/tree/bootstrap-5
This branch will:
2. create a new bs5 branch
Since there has not been a release for quite a long time and I am guessing many are using the module via "dev-master". I do not want to make a PR into master to start with. I suggest to implement the changes in a TEMP parallel branch. Eg v2 or similar.
3. Make a release
Make a release of the current work (eg 1.6) and announce a deadline for the merge of the TEMP branch into master. Suggest users to avoid using "dev-master" and use the latest tagged release instead (breaking changes incoming). I suggest no longer than 6 months for the deadline.
4. Tag a v2 release on the TEMP branch to be able to pull a versioned new release.
5. Merge
after the "deadline" merge the Temp branch to master and kill the temp branch.
related to #437 #476 #289 #406 #485
The text was updated successfully, but these errors were encountered: