----- Original Message -----
From: "Hannes Gredler" <[EMAIL PROTECTED]>
To: <tcpdump-workers@lists.tcpdump.org>
Cc: <tcpdump-workers@tcpdump.org>
Sent: Wednesday, July 13, 2005 4:35 AM
Subject: Re: [tcpdump-workers] print-slow.c
On Tue, Jul 12, 2005 at 11:10:38PM -0700, Loris Degioanni wrote:
| Some genius had the idea of adding a new file (print-slow.c) to the
| repository few hours before the x.9.2 release, without at least trying
| to recompile on all the platforms. Result: tcpdump 3.9.2 doesn't compile
| under Windows (even if it used to compile the night before the release).
that was me - guilty;
| We already checked in a patch, are there plans for a x.9.3 release? If
| yes, could people stop to do breaking commits before it's done?
you could help me avoiding those things by writing up a document that
describes what files you need on windows to be touched / added;
i only test on freebsd and linux;
This is surely a good idea, and we'll work on it as soon as possible. As we
have always done, we continue to offer our time to include patches for
Windows, and make sure that the releases compile and work on this platform,
too. However, our feeling is that the problem here is not "oops, I forgot to
fix/commit <somefile>, and now it doesn't build on platform XYZ". This can
happen (and it happens) to everyone. The *real* problem here is the release
process: our opinion is that, when a release should be done, there should be
an announce to the people having write access to the CVS, and *from that
moment on* and for the next 24/48 hours (at least) only the person
responsible for the release is allowed to commit anything on the release
branch, unless some big problem is found during the release testing.
We should write a document, or at least agree, on this too.
Gianluca and Loris
/hannes
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.
