lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-devel] 1.3.0 code freeze imminent


From: address@hidden
Subject: Re: [lwip-devel] 1.3.0 code freeze imminent
Date: Fri, 28 Dec 2007 12:36:09 +0100
User-agent: Thunderbird 2.0.0.9 (Windows/20071031)

I pretty much agree with Frédéric. #7525 is nearly done, we had a consensus on #7490 (so no need to wait), bug #21846 and patch #6348 are pretty much ready to check in also.

Other than that, I'm fine with freezing.

Simon

Frédéric BERNON schrieb:
Some tasks I think we can integrate :

 #7525 Implement TCP listen backlog (just some details to fix)
#7490 Add return value to sys_mbox_post (I think we got a consensus, I will try to produce a patch for it) #6683 Document lwIPs thread safety requirements (just close it now, since most thread safety requirements are in http://lwip.scribblewiki.com/LwIP_and_multithreading, and, as jifl said "otherwise they would be open forever because they can always be improved") #1549 lwIP function documentation (http://www.nongnu.org/lwip/ needs last updates, but they are minors, else, to my point of view, we can close it, and open a task for specific modules to document - PPP & IPv6 as Simon suggested). http://lwip.scribblewiki.com (I will update http://lwip.scribblewiki.com/LwIP_version_1.3.0_release_notes when we will reach the freeze step )

Some bugs to integrate:

#21846 LwIP doesn't appear to perform any IP Source Address Filtering (just need some other comments about the patch file)
and your records on tcp bugs

Perhaps this patch :
#6348 Broadcast ARP packets in autoip (seems good, but I would like to got Dominik Spies comments)



----- Original Message ----- From: "Kieran Mansley" <address@hidden>
To: <address@hidden>
Sent: Thursday, December 27, 2007 4:49 PM
Subject: [lwip-devel] 1.3.0 code freeze imminent


I plan to check in the persist timer changes in the next day or two if
there are no comments on the patches I've put forward, and after that
the tree will be in full code freeze for the 1.3.0 release.

I hope that this will be quickly followed by a release candidate being
published, extensive testing, no bugs to fix, and so a full release a
couple of weeks later.

As a result you should:
- let me know if there are any code changes not yet committed that you
want to get into 1.3.0
- start updating any ports that we want to officially support for
1.3.0
- get ready to test the release candidate as widely as possible.

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







reply via email to

[Prev in Thread] Current Thread [Next in Thread]