Hi,
It is a few days after the initial announcement, and received some
blessings already for the effort. Cherokee is not dead, and got the code
to prove it :-)
On Thu, 7 Jun 2012, Stefan de Konink wrote:
> 1) The biggest issue in the "stable" branch is the fact that SSL and POST
> support is problematic due to recent Google 'inventions'. With some support
> of Google in the past (and some workarounds by myself) it is possible to get
> a working Cherokee "stable" anyhow.
Bug 1284 is fixed. Yes, a one-liner, but one that probably makes more
sense than my previously attempt. Take a look, apply the patch, and you
will see it works. Sadly Google decided that Chrome 20 will disable
False-Start again. The bright side is: we finally have it working!
<http://code.google.com/p/cherokee/issues/detail?id=1284>
In the past few days I have closed many tickets, if you feel this was too
fast or incorrect, please let us know. I would also ask you if you do
have a reproducable bug: try to see if you can make a QA-test out of it.
There are almost 300 examples (yes, we have almost 300 QA-tests!) to get
inspiration from.
Things I would like to address before our next update;
1) The community section of cherokee-project.org is down for ages. We need
to address that.
2) I'm pretty happy that git is a distributed versioning system, but I
would love to apply all the fixes that have been made in the previous few
days to our stable branch. Which means I would have to be in the git team.
3) Lets have a great start of the summer and set the next release date of
the stable branch to 21st of june. That means we have less than two weeks
to take care of a proper release candidate, and should ask people to make
packages for their distribution of choice. In true Cherokee style this
release will have a songname: you might be able to guess what the song
would be :-)
Stefan
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
It is a few days after the initial announcement, and received some
blessings already for the effort. Cherokee is not dead, and got the code
to prove it :-)
On Thu, 7 Jun 2012, Stefan de Konink wrote:
> 1) The biggest issue in the "stable" branch is the fact that SSL and POST
> support is problematic due to recent Google 'inventions'. With some support
> of Google in the past (and some workarounds by myself) it is possible to get
> a working Cherokee "stable" anyhow.
Bug 1284 is fixed. Yes, a one-liner, but one that probably makes more
sense than my previously attempt. Take a look, apply the patch, and you
will see it works. Sadly Google decided that Chrome 20 will disable
False-Start again. The bright side is: we finally have it working!
<http://code.google.com/p/cherokee/issues/detail?id=1284>
In the past few days I have closed many tickets, if you feel this was too
fast or incorrect, please let us know. I would also ask you if you do
have a reproducable bug: try to see if you can make a QA-test out of it.
There are almost 300 examples (yes, we have almost 300 QA-tests!) to get
inspiration from.
Things I would like to address before our next update;
1) The community section of cherokee-project.org is down for ages. We need
to address that.
2) I'm pretty happy that git is a distributed versioning system, but I
would love to apply all the fixes that have been made in the previous few
days to our stable branch. Which means I would have to be in the git team.
3) Lets have a great start of the summer and set the next release date of
the stable branch to 21st of june. That means we have less than two weeks
to take care of a proper release candidate, and should ask people to make
packages for their distribution of choice. In true Cherokee style this
release will have a songname: you might be able to guess what the song
would be :-)
Stefan
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev