Buildbot has been (mostly) green for a while, and private fuzz tests
haven't turned up any problems, so I'm going to create the 0.99.6 branch
in the next couple of days. Please don't check in anything experimental
until then. :)
Gerald Combs wrote:
> It's been a while since the last release, and
It's been a while since the last release, and we've accumulated a lot of
bug fixes (some of which keep getting reported on Bugzilla). Once we
get fuzz testing up and running again (and it's green for a few
consecutive runs) I'd like to push out a new release.
__
gt;
>
>
> Must be solved first…
>
> Best regards
>
> Anders
>
>
>
>
>
>
> Från: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] För Kukosa,
> Tomas
> Skickat: den 12 april 2007 07:49
> Till: Developer support list fo
ckat: den 12 april 2007 07:49
Till: Developer support list for Wireshark
Ämne: [Wireshark-dev] Next release?
Is there any timeframe for the next release?
T.
___
Wireshark-dev mailing list
[EMAIL PROTECTED]
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Is there any timeframe for the next release?
T.
___
Wireshark-dev mailing list
[EMAIL PROTECTED]
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Gerald Combs wrote:
> Create a "/prerelease" directory in SVN, and copy the 0.99.1pre1
> revision to "/prerelease/wireshark-0.99.1pre1. (Bryant, will this
> meet your needs?)
Yes, it will. Thank you! Not to continue to nit-pick, but does
> For each prerelease, copy "/trunk-" to
> "/prerelease/wi
Jaap Keuter wrote:
> Having a develoment trunk and release branches just take more management
> around the time of the branch. Calm down on the new stuff, focus on
> bugfixes then branch and work only on the stability of the branch. Have a
> look at the Linux kernel development process, they face t
ronnie sahlberg wrote:
> Also, I would really like if bugzilla could be changed to REQUIRE an
> example capture for all "wireshark crashes" bugs that are reported.
>
That would be really helpful.
However, I don't think that bugzilla provides such a features (I would
be glad to be prove wrong,
On 7/1/06, Jaap Keuter <[EMAIL PROTECTED]> wrote:
> On Sat, 1 Jul 2006, Ulf Lamping wrote:
>
> > Kukosa, Tomas wrote:
> > > Would not it be better to make /trunk-1.0 as late as we have implemented
> all features planned for 1.0.0?
> > > Then the /trunk-1.0 would continue only with bug fixies.
> > >
On Sat, 1 Jul 2006, Ulf Lamping wrote:
> Kukosa, Tomas wrote:
> > Would not it be better to make /trunk-1.0 as late as we have implemented
> > all features planned for 1.0.0?
> > Then the /trunk-1.0 would continue only with bug fixies.
> >
> > I am affraid when we make /trunk-1.0 now we will come
Kukosa, Tomas wrote:
> Would not it be better to make /trunk-1.0 as late as we have implemented all
> features planned for 1.0.0?
> Then the /trunk-1.0 would continue only with bug fixies.
>
> I am affraid when we make /trunk-1.0 now we will come to the same conclusion
> during next release, i.
/trunk.
Od: [EMAIL PROTECTED] za uživatele Gerald Combs
Odesláno: pá 30.6.2006 21:25
Komu: wireshark-dev@wireshark.org
Předmět: [Wireshark-dev] Next release (plus SVN and roadmap changes)
We're overdue for an official Wireshark release. A couple of people
ACK
current SVN contains a lot of new nice features that may encourage
people to upgrade to wireshark and make a clean cut from ethereal.
something like the multiplatform autio playback thingytogether
with an example capture (the rtp one from the samplecaptures
repository?)
to send a signal
Gerald Combs wrote:
> Bryant Eastham wrote:
> > Not to open a complete can of worms here, but is there a reason that
a
> > more standard repository layout (trunk, tags, branches) is not being
> > used? I have been asking for a tag of 0.99.1pre1, with my appeals
> > probably being ignored because
Bryant Eastham wrote:
> Not to open a complete can of worms here, but is there a reason that a
> more standard repository layout (trunk, tags, branches) is not being
> used? I have been asking for a tag of 0.99.1pre1, with my appeals
> probably being ignored because I was asking for something that
t I shouldn't.
I'll stop now and live (happily, for the most part, I must add) with
what is given me.
Bryant Eastham
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gerald Combs
Sent: Friday, June 30, 2006 1:26 PM
To: wireshark-dev@wireshark.org
We're overdue for an official Wireshark release. A couple of people
have pointed out that the code in /trunk is in better shape than
/trunk-1.0, and that we might be better off using it for future
releases. I agree.
I'd like to make the following changes in the repository, which would
address th
17 matches
Mail list logo
