[PATCH] gweb: adding changeset branch information using <category> tag into RSS/Atom feeds (issue2530)

[Matt Mackall]

On Thu, 2011-03-03 at 09:19 +0200, Alexey Sergeev wrote:
> Hello Benoit,
> 
> Mercurial 1.8 is released. Could you add changes into next release?!

No, that's not how it works. It's too late for anything to go into 1.8
by definition. See here for the difference between major and minor
releases:

http://mercurial.selenic.com/wiki/TimeBasedReleasePlan

The next release will be a bugfix-only minor release (1.8.1) off the
"stable" branch on April 1, the work on the "default" branch where all
the new features go will be released as 1.9 on July 1. 


Now you actually did most of what you needed to do to get it into 1.8,
and I dropped the ball (sorry). The patch is still sitting in my queue.
I have it marked "fix" because it didn't pass the test suite. I planned
to fix it myself but apparently forgot about it.

I've just run the test suite again and it fails the following tests:

Failed test-hgweb-no-request-uri.t: output changed
Failed test-hgweb-commands.t: output changed
Failed test-hgweb-no-path-info.t: output changed
Failed test-hgwebdir.t: output changed

The last one fails with a bunch of exceptions.

Here's how you can help this process:

- make sure your patches pass the test suite (as per
http://mercurial.selenic.com/wiki/ContributingChanges) and resubmit

- watch the default branch for your patch, and complain if it doesn't
show up a couple days after I queue things


-- 
Mathematics is the supreme nostalgia of our time.