|
»
»
lwIP 1.3.2?
|
View:
New views
11 Messages
—
Rating Filter:
Alert me
|
 |
lwIP 1.3.2?
by Kieran Mansley
::
Rate this Message:
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 lwip-devel@... http://lists.nongnu.org/mailman/listinfo/lwip-devel |
|
|
Re: lwIP 1.3.2?
by Yann Suisini
::
Rate this Message:
As a future user , It's seems a good idea to first focus on remaining bugs :)
But what are the main changes in lwip 1.4.0 you're talking about ? Yann.
|
|
|
Re: lwIP 1.3.2?
by Kieran Mansley
::
Rate this Message:
On Fri, 2009-10-02 at 02:19 -0700, Yann Suisini wrote:
> As a future user , It's seems a good idea to first focus on remaining bugs :) > But what are the main changes in lwip 1.4.0 you're talking about ? The bugs will get fixed whichever route we take, but the advantage of the 1.3.2 would be that there would be a release with the fixes in, which makes it a little easier for users to get them. If we didn't make 1.3.2 they could still get the fixes, but they'd have to use CVS and risk getting a potentially unstable version due to other changes. The list of things that are planned for 1.4.0 is documented on savannah. Look at the bugs, tasks, patches, and see which are tagged for that release. Kieran _______________________________________________ lwip-devel mailing list lwip-devel@... http://lists.nongnu.org/mailman/listinfo/lwip-devel |
|
|
Re: lwIP 1.3.2?
by Simon Goldschmidt
::
Rate this Message:
> 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. I'd rather have a 1.3.2 fixing the bugs: I don't have much time for implementing new features right now, anyway... Simon -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser _______________________________________________ lwip-devel mailing list lwip-devel@... http://lists.nongnu.org/mailman/listinfo/lwip-devel |
|
|
|
|
|
Re: lwIP 1.3.2?
by Simon Goldschmidt
::
Rate this Message:
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 > lwip-devel@... > http://lists.nongnu.org/mailman/listinfo/lwip-devel > > _______________________________________________ lwip-devel mailing list lwip-devel@... http://lists.nongnu.org/mailman/listinfo/lwip-devel |
|
|
Re: lwIP 1.3.2?
by Alain Mouette
::
Rate this Message:
Hi,
I am a big fan of 1.3.2 :) from my point of view, lwip is one of the best of it's kind, and it would be very nice to have a *very stable* version out. IMHO it will probably help a lot the future of lwip, specially as it can come to be viewed as one of the most stable ... So my vote is for a very good 1.3.2, even if it takes a little while more. Cheers, Alain goldsimon@... escreveu: > 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 >> lwip-devel@... >> http://lists.nongnu.org/mailman/listinfo/lwip-devel >> >> > > > > _______________________________________________ > lwip-devel mailing list > lwip-devel@... > http://lists.nongnu.org/mailman/listinfo/lwip-devel > > _______________________________________________ lwip-devel mailing list lwip-devel@... http://lists.nongnu.org/mailman/listinfo/lwip-devel |
|
|
Re: lwIP 1.3.2?
by Kieran Mansley
::
Rate this Message:
On Mon, 2009-10-19 at 15:33 -0200, Alain Mouette wrote:
> Hi, > > I am a big fan of 1.3.2 :) > > from my point of view, lwip is one of the best of it's kind, and it > would be very nice to have a *very stable* version out. > > IMHO it will probably help a lot the future of lwip, specially as it can > come to be viewed as one of the most stable ... > > So my vote is for a very good 1.3.2, even if it takes a little while more. I'm also keen on it being stable, so I want to restrict the changes from 1.3.1 to be small, well-understood and low-risk bug fixes. If we start making more extensive changes then we'll introduce new bugs. I therefore hope to make an initial release in the next couple of weeks, once I'm happy that we've got all the issues we need fixed. Kieran _______________________________________________ lwip-devel mailing list lwip-devel@... http://lists.nongnu.org/mailman/listinfo/lwip-devel |
|
|
Re: lwIP 1.3.2?
by Simon Goldschmidt
::
Rate this Message:
Kieran Mansley wrote:
> I'm also keen on it being stable, so I want to restrict the changes from > 1.3.1 to be small, well-understood and low-risk bug fixes. If we start > making more extensive changes then we'll introduce new bugs. I > therefore hope to make an initial release in the next couple of weeks, > once I'm happy that we've got all the issues we need fixed. Of course I understand that, but I'm also keen on working on the rest of the stack. Therefore, I'd be happy if we could get a release candidate for broader testing out soon. Also, I think adding bug #26251 (RST process in TIME_WAIT TCP state) to 1.3.2 wouldn't hurt since I do regard this as low-risk. And as there is only one open bug left, I'd be happy to help you out wherever I can to speed up releasing 1.3.2. Simon _______________________________________________ lwip-devel mailing list lwip-devel@... http://lists.nongnu.org/mailman/listinfo/lwip-devel |
|
|
Re: lwIP 1.3.2?
by Alain Mouette
::
Rate this Message:
I am bringin this from another thread, as this seem to be the correct one...
goldsimon@... escreveu: > What's the current timeplan on 1.3.2? As there are only few real bugs > open (that aren't feature requests), in my opinion we have two choices: > either > a) we get 1.3.2 out really fast now (bug #27445 is nearly solved, isn't > it?) or > b) we could decide to do a real bug-fix release in which we try to fix > all known bugs (which could take another month, of course). I strongly vote for b) We really need a very goot version that every body will come to relly upon. I have been follwing the many bugfix threads and I am impressed by the depth of the bugs being fixed. This kind of stuff is essencial and will live forever... > Although I favoured a), I'm now tempted to vote for b), since it could > really be a while until 1.4.0 will be released, and it looks like that > one will have rather many new features, which makes it potentially > unstable again. Therefore, a "superstable" release before 1.4.0 (be it > 1.3.2 or 1.3.3) would be a good idea. It's really indifferent for me if it is called 1.3.2 or 1.3.3, that is the only one that matters. I got the feeleing that 1.3.1 is "risky" so I haven't moved (call me chicken...) I just feel that a super-stable version will be a much better platform to start working on new stuff :) Alain _______________________________________________ lwip-devel mailing list lwip-devel@... http://lists.nongnu.org/mailman/listinfo/lwip-devel |
|
|
Re: lwIP 1.3.2?
by Simon Goldschmidt
::
Rate this Message:
Alain Mouette wrote:
> We really need a very goot version that every body will come to relly > upon. I have been follwing the many bugfix threads and I am impressed by > the depth of the bugs being fixed. Thanks to three or four really skillful users that supplied us with detailed bug reports! > This kind of stuff is essencial and > will live forever... > > > Although I favoured a), I'm now tempted to vote for b), since it could > > really be a while until 1.4.0 will be released, and it looks like that > > one will have rather many new features, which makes it potentially > > unstable again. Therefore, a "superstable" release before 1.4.0 (be it > > 1.3.2 or 1.3.3) would be a good idea. > > It's really indifferent for me if it is called 1.3.2 or 1.3.3, that is > the only one that matters. I got the feeleing that 1.3.1 is "risky" so I > haven't moved (call me chicken...) > fixed from 1.3.0 to 1.3.1. The problem is that we also added new code, which has turned out to contain some bugs, too. One could argue if these bugs are more severe than the ones fixed in 1.3.1... As to the names (1.3.2, 1.3.3, ...) the problem is that once 1.3.2 is out, there's not feature freeze on CVS HEAD and I'll start implementing new features as I need them. This means that the code is might get more unstable again (like always when adding new code). However, with such a small project as lwIP, we can't afford to maintain branches (i.e. merge bug fixes found in 1.4.0 back to 1.3.2 and thus releasing 1.3.3)! Anyway, the bugs that are open now and not targeted for 1.3.2 aren't really severe, i.e. I wouldn't be scared to ship my own products with 1.3.2. I think 1.3.2 will be the best lwIP ever ;-) Simon _______________________________________________ lwip-devel mailing list lwip-devel@... http://lists.nongnu.org/mailman/listinfo/lwip-devel |
| Free embeddable forum powered by Nabble | Forum Help |
