Bug#727085: Now we don't depend on the weird libevent patch
On Mon, Dec 30, 2013 at 12:56:48AM +0100, László Böszörményi (GCS) wrote:
My opinion for releases follows. Do one if there's an important
bugfix, new feature added, etc. In short, if there's a reason.
On the other hand, there's no problem with releasing every two weeks,
it's just not common. It matches with Debian standards, meaning that
normally ten days needed for unstable -> testing migration.
Two weeks is probably too often for Debian but time-based releases in
general (rather than "important bugfix") are fairly common. I think the
original idea of accumulating multiple sprints into one "community"
release is a great path forward. The proposal for 8-week releases sounds
just fine to me.
Looking a bit further ahead, Debian will release a new stable in
something like a year from now, and will have to support whatever
happens to be in testing by November 6th, for at least the release of
next stable + one year (i.e. for about 3-4 years), without the ability
to bump into newer HHVM versions. Some upstreams tend to release some
"LTS" releases for such uses, potentially labeling one of their
incremental releases as LTS. This isn't a prerequisite, but it's good to
actually have some longer stable/security management in mind when
planning your release schedule.
Lastly, Laszlo, we should talk about how I can help with packaging.
Do you have a packager position there, at FB? :) At least ATM I've
two places to work for. At Debian I've more than a hundred packages
and twenty to do. Especially that I have to work more or less constant
from 31st 06:00 am to 2nd 04:20 pm. Will be hard, thus I'll start
again with HHVM next year.
Well, noone really forced you to ITP this :) You definitely seem to have
your hands full, there's no need for you to take on more than you're
able to handle. If you're too busy, I can just takeover this ITP, just
say so.
Now my previous package section for HHVM,
which I've named hiphop-php (to match the PHP policy of Debian, but
will re-check that):
Which section of the policy mandates that? I'd be very suprised if the
existing PHP policy covers alternative interpeters.
-- cut --
HipHop VM (HHVM) is a new open-source virtual machine designed for executing
s/a new/an/ (redundant for the description)
programs written in PHP. HHVM uses a just-in-time compilation approach to
achieve superior performance while maintaining the flexibility that PHP
developers are accustomed to. HipHop VM (and before it HPHPc) has realized
> 5x increase in throughput for Facebook compared with Zend PHP 5.2.
HipHop is most commonly run as a standalone server, replacing both Apache
and modphp.
The last two lines are incorrect considering the new FastCGI mode of
operation, which AIUI will be the only one actually offered by the
package, as the embedded standalone webserver requires patches to
libevent.
I think packaging for Debian is a good step. Then Ubuntu maintainers
will pick it up and as I know, Mint based on Ubuntu, they will have it
as well.
Ubuntu automatically syncs from Debian, there's no need for Ubuntu
maintainers to do anything. And yes, there's tons of other Debian &
Ubuntu derivatives that also regularly sync from those two.
Regards,
Faidon
Reply to: