Hi all,
What's the current timeplan on releasing 1.3.2? From the list of bugs
targeted to 1.3.2, there is only one remaining and I'd like to work on
some non-1.3.2 bugs/patches/tasks that would fit into our next
lwIP-containing product.
However, I'd also be happy to include some other (mainly TCP-related)
bugs into 1.3.2, as 1.4.0 might take a while... These would be:
- bug #26251: RST process in TIME_WAIT TCP state
- bug #26672: close connection when receive window = 0
- bug #26062: FIN_WAIT_2 state following tcp_close should timeout
eventually
and maybe also bug #25882: TCP hangs on MSS > pcb->snd_wnd
Working on these will of course delay 1.3.2 a little, but I think that
would be worth it, especially as 1.4.0 shall include new features and
will presumably change the API (a little at least). Also, most of these
bugs aren't big code changes but rather bugs that need discussion on how
to solve them.
Simon
Kieran Mansley wrote:
There have been a few quite serious bugs reported since 1.3.1 was
released, I guess because a lot of people only moved and tested it after
it was officially out. I'm mindful that 1.4.0 may take some time as we
have some significant changes, and I expect that this may result in lots
of users opting to track CVS rather than use a released version in the
meantime. It might therefore be worthwhile to make another bug-fix
release in the next month or so (1.3.2) so that users can pick up these
fixes without tracking CVS.
Does anyone have any strong objections to this? It would mean delaying
any major new features (although I'm not aware of any that are currently
being worked on) for a few weeks and concentrating on getting the bugs
that have shown up recently committed.
Thanks
Kieran
_______________________________________________
lwip-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel
_______________________________________________
lwip-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel