Re: Attempt to get 5.3.1 release one step further
| From: | Johannes Schlüter | Date: | Tue, 29 Sep 2009 10:06:23 +0000 |
| Subject: | Re: Attempt to get 5.3.1 release one step further | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-45649@lists.php.net to get a copy of this message | ||
Hi,
On Mon, 2009-09-28 at 22:52 +0200, Pierre Joye wrote:
> As an attempt to get 5.3.1 release sooner rather than later, I would
> like to give a hand to Johannes (who is MIA ;), to get the patches
good thing :-)
> merged in 5.3.1 in a controllable manner (from a QA point of view) and
> as soon as possible. Many of you certainly contacted Johannes in one
> way or another to ask him to merge a patch. That's a good thing except
> for one part, we have no trace of these requests :)
>
> That's why I would like to get a list of these requests here:
> http://wiki.php.net/todo/php531
What I actually - while doing quite lazy computer-less vacation - tried
to find is a nice tool to
a) visualize commits that have been merged (most tools do this the other
way round only ("this commit is a merge coming from there") and
b) comment on commits that they should be reviewed deeper/should
be/won't be merged
The best I found is a stupid spreadsheet and random (custom) svn
properties and some scripting, but that's some pain, too.
As I think without such a tool it ends in a mess, anybody knows such a
tool which works on unix or linux systems?
some background: Initially I thought about doing this strictly
chronically but this won't work for fixes which should be merged but
aren't 100% complete, yet and similar cases.
Thanks,
johannes