On Sat, Apr 25, 2009 at 10:59 AM, Eric Auer <e.a...@jpberlin.de> wrote: > > Hi Christian, > >>> If you're waiting for further improvements to 2038 before you release >>> 2038, then you're doing this wrong. [...] I'd strongly recommend >>> making 2038 available, and putting the "few pending improvements" in >>> 2039. >> >> The problem is that Eric holds back at least three necessary patches, of > > There are also patches waiting for feedback / review / testing. Saying > you have to modify this like that is one thing, discussion is another. > > Examples: > > - handling of floppy before disk is inserted / unformatted partitions > > - initdisk CHS geometry fix and BSS init fix from RayeR > > - int 21.1c non-FAT / non-existing drive handling fix from Tom > >> seems Eric doesn't exactly want to be the kernel maintainer, you need >> someone else for that. > > Uhm you do not exactly motivate me but I can repeat the state > of things: The 2038 kernel needs mainly doc updates plus some > feedback for a few small pending patches. The lists are too > silent on that. Of course I could just push the patches and > assume they will work, but that is the non-preferred choice. > >> The mentioned patches are: > > None of those patches is necessary for the 2038 kernel but on > the other hand some of them are definitely useful, yes :-).
The problem is: how will you (Eric) know that the patches will work? How long do you intend to hold back the 2038 version before deciding it is "good enough"? In free / open source software development, the user community assumes a certain level of instability in downloading any version. The idea is that if you release often, you can make rapid, incremental improvements to the F/OSS program because users (testers) will provide frequent feedback to the developers. If you don't make frequent releases, this feedback loop is interrupted, and you lose momentum. If you post 2038 now, and remind everyone that this needs testing (just like any other F/OSS release) then you can get others to help test it and discover bugs ... which can be fixed in a 2039 release. That will probably also have bugs, but you'll address those in a 2040 release. And so on. -jh ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
