Hey,
I know type hints are more fun to discuss but anyways: In trunk
ChangeLog lists entries up till 2005 (when 5.2 was branched of, from
which 5.3 was branched from which the current trunk was branched of) In
the old trunk the file lasts until 2009-07-08 (when we switched from CVS
to svn)
Is anybody using this file? If this is thee case could somebody then
make sure it's being updated (and maybe take care of
ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An
outdated file might be confusing for users expecting content like we
have in the NEWS file there.
johannes
2010/5/28 Johannes Schlüter johannes@schlueters.de:
Hey,
I know type hints are more fun to discuss but anyways: In trunk
ChangeLog lists entries up till 2005 (when 5.2 was branched of, from
which 5.3 was branched from which the current trunk was branched of) In
the old trunk the file lasts until 2009-07-08 (when we switched from CVS
to svn)Is anybody using this file? If this is thee case could somebody then
make sure it's being updated (and maybe take care of
ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An
outdated file might be confusing for users expecting content like we
have in the NEWS file there.
+1 for dropping it, it is confusing and why do we need that aside the
NEWS file ?
johannes
2010/5/28 Johannes Schlüter johannes@schlueters.de:
Is anybody using this file? If this is thee case could somebody then
make sure it's being updated (and maybe take care of
ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An
outdated file might be confusing for users expecting content like we
have in the NEWS file there.
+1 on removing the ChangeLog and its archives, particularly since
they're taking up over a meg in a PHP 5.3 checkout, most of which is
already gzipped.
NEWS and the migration guides in the manual cover the needs of users
these days, and there's always svn log for anyone who wants more
detailed changeset information.
Adam
hi Johannes,
2010/5/28 Johannes Schlüter johannes@schlueters.de:
Is anybody using this file? If this is thee case could somebody then
make sure it's being updated (and maybe take care of
ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An
outdated file might be confusing for users expecting content like we
have in the NEWS file there.
I do, what's about only changing how it is generated to generated
changes since last release instead?
I'd to add that unless we add everything in the NEWS file, the
ChangeLog remains the only way to have a list of all changes (without
doing manually).
Cheers,
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
2010/5/28 Johannes Schlüter johannes@schlueters.de:
Is anybody using this file? If this is thee case could somebody then
make sure it's being updated (and maybe take care of
ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An
outdated file might be confusing for users expecting content like we
have in the NEWS file there.I do, what's about only changing how it is generated to generated
changes since last release instead?I'd to add that unless we add everything in the NEWS file, the
ChangeLog remains the only way to have a list of all changes (without
doing manually).
Isn't that what "svn log -v" now provides? The format is slightly
different of course, but it does provide the same info.
Although it does seem that we need to get ourselves more diciplined into
writing the commit messages according to the prefered format[1] again.
[1] http://svn.php.net/viewvc/php/php-src/trunk/README.SVN-RULES?view=annotate#l90
with kind regards,
Derick
--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
2010/5/29 Derick Rethans derick@php.net:
2010/5/28 Johannes Schlüter johannes@schlueters.de:
Is anybody using this file? If this is thee case could somebody then
make sure it's being updated (and maybe take care of
ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An
outdated file might be confusing for users expecting content like we
have in the NEWS file there.I do, what's about only changing how it is generated to generated
changes since last release instead?I'd to add that unless we add everything in the NEWS file, the
ChangeLog remains the only way to have a list of all changes (without
doing manually).Isn't that what "svn log -v" now provides? The format is slightly
different of course, but it does provide the same info.
By "without doing it manually", I meant when one fetches a release or
a snapshot.
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
Is anybody using this file? If this is thee case could somebody then
make sure it's being updated (and maybe take care of
ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An
outdated file might be confusing for users expecting content like we
have in the NEWS file there.I do, what's about only changing how it is generated to generated
changes since last release instead?I'd to add that unless we add everything in the NEWS file, the
ChangeLog remains the only way to have a list of all changes (without
doing manually).Isn't that what "svn log -v" now provides? The format is slightly
different of course, but it does provide the same info.By "without doing it manually", I meant when one fetches a release or
a snapshot.
The ChangeLog files aren't updated because no one ever ported the ChangeLog crons from CVS to SVN. It wouldn't be very difficult - in fact one of the open-source scripts already out there for the purpose would seem appropos, it just hasn't been done. They seem to be standard fare in FOSS projects, so I'm -1 for removing the functionality, but +1 for removing the useless archives from all active branches.
I wish I could volunteer to do the port, but I have too much on my plate right now :(
-- Gwynne
hi Gwynne,
On Sat, May 29, 2010 at 10:39 AM, Gwynne Raskind
gwynne@darkrainfall.org wrote:
By "without doing it manually", I meant when one fetches a release or
a snapshot.The ChangeLog files aren't updated because no one ever ported the ChangeLog crons from CVS to SVN. It wouldn't be very difficult - in fact one of the open-source scripts already out there for the purpose would seem appropos, it just hasn't been done. They seem to be standard fare in FOSS projects, so I'm -1 for removing the functionality, but +1 for removing the useless archives from all active branches.
I wish I could volunteer to do the port, but I have too much on my plate right now :(
http://arthurdejong.org/svn2cl/ should be enough?
Cheers,
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
Hey,
I'd to add that unless we add everything in the NEWS file, the
ChangeLog remains the only way to have a list of all changes (without
doing manually).
Having the file is absolutely fine with me, while I can fulfill my needs
with svn annotate and svn log. But if we ship it, it should be correct
and at least since 5.2.0 we ship a wrong (not updated) file. And that I
consider bad. So I ask somebody to either remove it or make sure it's updated
(automatically or by adding instructions to README.RELEASE_PROCESS) in
all places.
johannes
2010/5/29 Johannes Schlüter johannes@schlueters.de:
Hey,
I'd to add that unless we add everything in the NEWS file, the
ChangeLog remains the only way to have a list of all changes (without
doing manually).Having the file is absolutely fine with me, while I can fulfill my needs
with svn annotate and svn log. But if we ship it, it should be correct
and at least since 5.2.0 we ship a wrong (not updated) file. And that I
consider bad. So I ask somebody to either remove it or make sure it's updated
(automatically or by adding instructions to README.RELEASE_PROCESS) in
all places.
Maybe simply do it at release time?
Cheers,
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org