Reference: http://php.net/manual/en/migration54.new-features.php
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 6 2015
Dec 3 2015
Yup, Python 3 is totally fine.
That should be easy done with the github api. No problem to do it in python3 ?
Merge commit without rebase.
Dec 2 2015
Merge without rebase.
Plugins we use:
@Kaliiixx wants to work on PHP 7.
Dec 1 2015
I wonder if that shouldn't go to nasqueron/php-cli.
Another test done: this diff has been created with an image built with this change, the → from the commit were correctly printed and I were able to write an é.
Automatic publication first success at 2015-11-20T00:44:29.539880
according https://hub.docker.com/r/nasqueron/arcanist/builds/
$ docker run --rm nasqueron/nginx-php-fpm php -i [...] bz2
$ docker run --rm nasqueron/php-cli php -i [...] bz2
I'm investigating this, we've worked on a nasqueron/etherpad (rDETHER) instance, which looks good.
I've edited the Dockerfile and rebuilding the two images, PHP is compiling.
Per http://php.net/manual/en/bzip2.installation.php the setting is --witb-bz2 and not --enable-bz2.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.