Kieran Mansley wrote: > Something that's been in the back of my mind recently is that we should > work on a guide to updating ports from 1.3.2 to 1.4.0 at the same time > as we make the changes to the source. Trying to write this guide just > before 1.4.0 is released will be much harder. So far, as Simon has been > careful to keep the example ports in contrib up to date, the commit logs > there form a rough indication of what needs doing. > > I've been wondering how we can do this without making it becoming a > chore or getting in the way of development.
I've been thinking about this myself recently. The problem is that if I write something now, changes are high I have to change it again before releaseing 1.4.0. We could create a file "UPGRADING" or something like that along with the CHANGELOG file and with each commit, make short notes if something changes regarding the ports or netif drivers. When releasing, we can then reorganize the section from CVS HEAD (since last release, much as in CHANGELOG) to better summarize it. This wouldn't bee too much of an effort during development and would both allow upgrading from the last release to CVS HEAD as well as upgrading from an older release to the current release by making the changes each release requires (of course, that would be in the future since < 1.3.2 wouldn't be in that file...). Simon -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser _______________________________________________ lwip-users mailing list lwip-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/lwip-users