Changes with nginx 0.8.27 17 Nov
2009
*) Bugfix: regular expressions did not work in nginx/Windows; the
bug
had appeared in 0.8.25.
When a patch comes out for the current version, does the .tar.gz at
nginx.net get patched as well, or do i have to apply the patch to the
file?
Hello,
i rebuilded the nginx rpms in suse’s buildservice. you can get them
here: /repositories/server:/http - openSUSE Download
major change for 0.8.x: file-aio enabled for distributions which got a
kernel newer then 2.6.22 (opensuse11.0, SLE11 etc)
Regards
Juergen
On Wed, Nov 18, 2009 at 11:29, Igor S. [email protected] wrote:
What a patch do you mean ?
Any patch that comes out for any given current version. Let’s say
someone finds a bug for 0.8.27 and you release a patch. If the next
day i download the 0.8.27 tarball from nginx.net, will it be patched?
On Tue, Nov 17, 2009 at 07:41:43PM +0000, Nuno Magalhães wrote:
When a patch comes out for the current version, does the .tar.gz at
nginx.net get patched as well, or do i have to apply the patch to the
file?
What a patch do you mean ?
On Wed, Nov 18, 2009 at 12:05:01PM +0000, Nuno Magalhães wrote:
On Wed, Nov 18, 2009 at 11:29, Igor S. [email protected] wrote:
What a patch do you mean ?
Any patch that comes out for any given current version. Let’s say
someone finds a bug for 0.8.27 and you release a patch. If the next
day i download the 0.8.27 tarball from nginx.net, will it be patched?
No. The released tarballs are never changed. If there is a critical bug
in a release, I just release next verison.
Marcus C. wrote:
(in 0.7.44)
- the changes made in ngx_http_finalize_request() (in 0.8.19) (which
broke some modules which relied on using the NGX_DONE return value) or
the inclusion of this older version of the file (in 0.8.22)I believe it would help developers save time identifying areas that need
changing for newer versions of Nginx, and would allow them to more
quickly adopt useful new features that they might not be aware of.
I’m having similar problems.
It would be nice if Igor could maintain and publish a developer
changelog.
On Thu, Nov 19, 2009 at 2:43 AM, Valery K.
[email protected] wrote:
I’m having similar problems.
Me too 
It would be nice if Igor could maintain and publish a developer changelog.
Yeah, that’ll be great
Thanks!
-agentzh
Agreed absolutely. And the nginx-dev mailing list will be not out of
place.
I’d prefer to see a git repository or something similar, but this works
too.
2009/11/19 Peter A Leonov [email protected]
Something like Lighthouse (lighthouseapp.com) might be good for bug
and feature request tracking as well. It’s free for open source
projects.
On Thu, Nov 19, 2009 at 7:05 PM, Mathew D.
Yes, I agree.
Hi,
Would it be possible to add a ‘developer changelog’ to the standard
changelog for newly-released versions of Nginx? I’m thinking mostly of
features of Nginx that might be used by module developers (or core
hackers), that either added new features or could break existing
modules.
Two examples I can think of include :
- the addition of ngx_http_complex_value_t (and associated functions)
(in 0.7.44) - the changes made in ngx_http_finalize_request() (in 0.8.19) (which
broke some modules which relied on using the NGX_DONE return value) or
the inclusion of this older version of the file (in 0.8.22)
I believe it would help developers save time identifying areas that need
changing for newer versions of Nginx, and would allow them to more
quickly adopt useful new features that they might not be aware of.
Thanks,
Marcus.