Bug#727085: Now we don't depend on the weird libevent patch

[Paul Tarjan <pt@fb.com>]

Thanks so much for speaking up Faidon. Francesco, I honestly thought you
were speaking officially and we would be rejected. When you didn't reply
to my email asking "What should I do?" I didn't know what to think...

I won't stir the pot with any more legal discussion. That isn't my field
and I'm just parroting what our legal department tells me anyways. I've
articulated our position before, so I'll just wait until the legal issue
is actually blocking our adoption. Ok?

Since my last email, I put a bunch of effort into my packaging script. Now
they are signed correctly, there is a main skeleton and then overrides for
each version, and it updates the version files for me. Feel free to make
pull requests or use this as a basis:
https://github.com/hhvm/packaging/tree/master/hhvm/deb

Internally at FB we release a new version of HHVM every 2 weeks. We cut
the branch on Monday and then do lots of rigorous testing and ship it 10
days later on Thursday morning. I'd like to exactly mirror the internal
releases since they are well tested instead of just arbitrarily cutting
trunk. Many people voiced opinions that every 2 weeks was too fast for
major open source releases so we agreed on mirroring every 4 releases (8
weeks). How does that sound? It is easy to make it faster or slower by 2
week increments if anyone has opinions.


Lastly, Laszlo, we should talk about how I can help with packaging. I
currently make a new branch for major versions and tags for each point
release on our github repo. Do you want me to email you when I do this or
can you subscribe to github easily? Or should I setup a mailing list and
always email that when I push? I'll probably still have to keep packaging
it for other distros since you're only going to do debian, right? Or is
there an easy way for you to also do it in other debian-based distros
(ubuntu, mint). Can you also do yum based distros or do you know what I
should do for inclusion there?

Paul