Open nicolaiskogheim opened 8 years ago
This will make our master
branch and Laravel/Socialite's master
very out of sync, but I don't think that will be a problem. It would be a mess trying to merge one into the other already because we have done much styling and structural alterations to the code base.
This would of course not be totally kosher if anyone had forked this repo, but they haven't.
Suggestion: Rename
2.0
tomaster
, and only have that branch.Laravel/Socialite does experimental work, possibly preparing for a 3.0 of Socialite, on their
master
branch, while having a somewhat stable2.0
branch. This makes sense for them, but not for us because we aren't interested in maintaining the2.0
version. Laravel does that.We will most likely create a stable release some time in the future, and then it will make sense to have branches to keep track of that version.
Note: This will require us to change the
composer
instructions to point to themaster
branch.