It seems as if the model of 'just hold off the new development release
until That New Feature(sm) (the next best thing after sliced bread) is
in' doesn't really work.
Like you said we opted to wait for the multi-interface capture to be
in, and even though Irene is working hard on it, it hasn't materialized
in solid form just yet.
In practice the development release becomes stale as soon as the next
branch comes out, and remain so until the next one is about to come
along.
So what to do? I say, remove the development pane with a new branch,
and restore it once we have really something new to show, like a genuine
RC.
In the mean time, development builds (at the bleeding edge) remain
available, so for the persistent ones there's always new stuff
available.
Gerald, I know this makes your release TODO list yet another item
longer, something you don't like. I am sorry about that, maybe I've got
some suggestions about that later.
Thanks,
Jaap
On Wed, 02 Nov 2011 10:07:44 -0700, Gerald Combs wrote:
Excellent question. We were holding off on making a development
release
over the summer until the multi-interface capture support settled
down.
Is there any reason to delay 1.7.0 at this point?
On 11/2/11 12:51 AM, Dirk Jagdmann wrote:
So today somebody at my company wanted to check the latest
Wireshark.
Looking at http://www.wireshark.org/download.html [1] he read the
description literally which said that the 1.6.0rc2 is the latest
development release. So he figured it might be newer than the fresh
1.6.3 release... I think we can remove that old release candidate,
or
alternatively put a daily/weekly tarball of trunk on that page. --->
Dirk Jagdmann ^ doj / cubic ----> http://cubic.org/~doj [2] ----->
http://llg.cubic.org [3]
