Drop PHP5.3
Hywan opened this issue · comments
Hello :-),
As discussed on the ML, at Apex and on IRC, we are going to drop PHP5.3 in favor of PHP5.4 for the lowest required PHP version. This issue will report new elements and discussions.
/cc @hoaproject/hoackers
@Hywan we're still using some php 5.3 instances on a very old server. We plan to upgrade by the end of october.
@shouze Ok, excellent. It gives us enough times to upgrade everything.
👍
Can we go faster and targeting end of September?
@Hywan nope ™
Sorry we have a planning to respect. Other users are waiting on tags and the dropping of PHP5.3 will start the tagging. Is it critical for you?
ping @hoaproject/hoackers again :-).
My proposal:
- add tags (for finalized libraries) with master compatibility number (MCN) at
1
, - update
composer.json
files, - drop PHP5.3,
- add tags (for the same libraries) with MCN at
2
as expected with our new release process.
Also, we should:
- add an “Install” section in all existing
README.md
, - update the
Source.html
page, - complete the
Source.html
page with the release process explained.
Thoughts?
👍
+1
👍
👍
Ok for me :)
2014-09-15 15:14 GMT+02:00 Renaud LITTOLFF notifications@github.com:
[image: 👍]
—
Reply to this email directly or view it on GitHub
#41 (comment).
Gérard Ernaelsten
Ernaelsten@gmail.com
Afin de contribuer au respect de l'environnement, merci de n'imprimer ce
courriel qu'en cas de nécessité.
For libraries that are not finalized yet, I propose to use the MCN (master compatibility number) 0, something like: 0.14.09.16 for today.
Thoughts?
@Hywan oh yes, will be clear for everyone I guess.
👍
add tags (for finalized libraries) with master compatibility number (MCN) at 1
drop PHP5.3,
add tags (for the same libraries) with MCN at 2
👍
Doing so will not create much work for users stuck on 5.3 (IMHO): they'll only have to change the way they lock their deps.
👍
Tomorrow, I am going to drop PHP5.3 (so, MCN++) and updating README.md
.
So, in this order:
- apply #42,
- new tag on Core.git (
2.14.09.17
), - update all
README.md
along withcomposer.json
of libraries, - new tags for all the libraries.
And we will be good :-). After that, I will merge several pending PRs and the train will go on.
Good night!
Example in the following listed PR.
Yesterday, I have failed while tagging the first release. Everything is ok now, but I have to fix these first ones. Also, I have to add branch-alias as we discussed with @stephpy on IRC for developers (not end-users).
@Hywan everything is still not OK but we're closer than ever!
All first tags are fixed (my todo: http://paste.hoa-project.net:80/24da05ab62d1c155208d88651fcb8984de2971bf, temporary link).
https://gist.github.com/stephpy/d0ca578c6ac75871956b
branch-alias
everywhere \o/