-
Notifications
You must be signed in to change notification settings - Fork 2k
The ultimate SemVer discussion: how? #411
Comments
Sorry, quick answer:
Note: Following SemVer doesn't mean we have to start from scratch or from a major version. We can assume (and document) that we start following SemVer from 4.1. PS: @gfosco, thanks for mentioning me in the last Roundtable! :) |
Nice! So it actually might be easier than I thought!
True. I've been doing a lot of talks/blogs about 4.1 being a complete rewrite, but I think it'd be better to just market this as 5.0 from now on so that future developers won't need the same "here's our SemVer history for why things are all versioned strangely". :) Laravel had the same issue where they were talking about 4.3 for a long time and at last minute they changed it to 5.0. Sigh... the joys of being a developer. :) @yguedidi When you get more time, can you provide specific steps for @gfosco to get master rocking as 5.0? :)
Ha! Indeed it is... :)
Good point. I think it might be confusing to resurrect it. Maybe we just alias the new SemVer package as |
PS @yguedidi One of these days I'm going to get you on the Roundtable! :) |
@gfosco Do you want to go ahead and start marketing 4.1 as 5.0? Highly recommended! :) If so I'll update the docs, etc. |
Yeah.... Let's do it. 5.0. It'll take a little longer to get out, but we'll figure out all the renaming and whatever else. |
W00t! ... And now to go back through months of blogs/docs and update the version number. Lol. |
Hooray! @gfosco you made my day! We have to be sure about how to rename this repo/packagist/etc... PS: @SammyK haha maybe once I release my SDK (which is currently more like a vaporware...), but you'll need to speak sooo slowly and a live voice translator for my french-flavored english :) |
@yguedidi Is there a way we can alias both
Deal! :) |
@SammyK according those lines in Composer, we can't... |
A solution would be to create a real branch |
How's about we create a Then, in "branch-alias": {
"dev-master": "5.x-dev"
} And in the "branch-alias": {
"4.1.x-dev": "5.x-dev"
} And we can keep the branch alias in the Would that work? I'm not familiar with the |
@SammyK branch aliasing is useless when the real branch exists. I suggest to create a Then, we can alias @gfosco, you can optionally rebase the PS: about removing branch @gfosco can you remove the old |
Ok... I created a branch What's next? I'm getting close to getting approval to launching docs on github... but we'll have to convert all the XHP table widgets to standard markdown :\ |
Can I offer any help about the XHP issue? Please clarify what is the required medications, and I will help on that |
@gfosco I made a mistake... According this function of Composer, branches can just be named Then:
|
I'll do more research about renaming this repo, I do not have the time now. |
@yguedidi Yes, but as far as I can tell it's being regexed before it gets sent to that method. I just called upon the twittersphere for help on this one. :)
@gfosco Yay!!!!! Does that mean the developer site will just link to the GitHub version? And do you mean a GitHub static site or a wiki on the repo?
That's cool. I can work on that after I update the docs to refer to 5.0. :) |
@SammyK regarding the 301 redirects on Github, they are indeed doing it for repo renamings on the web. For the API (which include the download URLs used by Composer in its lock file), this should be supported in a few months (it is currently in preview but composer does not use the preview accept header): https://developer.github.com/changes/2015-04-17-preview-repository-redirects/ |
Ok, I'm okay with that for now. |
So yeah, we're going live with the awkward v4 name for now. Closing this. |
Hi, just so you know, the 301's seem to be working (or at least, are working for me) |
It has been a year since this issue was closed. I wonder when this issue will be solved completely? I am an all-new FB PHP SDK user who is trying to install the latest stable version and the awkward name of this repo costs me time to research "Why?" :( |
You heard it on PHP Roundtable first ladies and gentlemen! Straight from the horse's mouth, @gfosco is open to supporting SemVer! Yay! :D
But! The question is: how?
The current repo is prefixed with
-v4
. I know we can rename, but GitHub doesn't support 301 redirects which can be problematic for all the links pointing to this repo. But once it's renamed, it should be pretty trivial (I think) to point packagist to the new repo & people can still use composer like they've always done.Anyone ever done this before & have advice on how we can rename the repo without too much disruption? :) cc @yguedidi @mtdowling
Yay for 5.0! :D
The text was updated successfully, but these errors were encountered: