mdc> I agree that we should be pushing toward 5.2 and testing and fixing
issues.
mdc> I'd really enjoy demoing a stable and flexible 5.2 (with UNDI
support ;)
mdc> at LinuxWorld Expo in San Francisco in August.
I agree, 5.1 seems pretty stable and we need to move forward.
mdc> Now, for 5.3, I want to propose that we consider adopting a coding
style and
mdc> doing some major code reformatting to make it easier for people to
hack.
mdc> I know from working on drivers that there is a lot of variability
in coding
mdc> style that makes it somewhat difficult to edit files. Anybody else
feel this way?
I support this also. Eric's reformatted 5.1 makes adding a driver to
the source tree dead simple compared to 5.0 but the adoption of a coding
style and reformatting/fixing the code would be great. I know some of
the inconsistencies have slowed me down in the past.
mdc> Now of course this means we have to buckle down and get 5.2 out,
but,
mdc> hey, that might even be fun. Ken's away for mdc> three weeks and if
mdc> we could test 5.1.8 and squash a few bugs, we could release in June
perhaps.
That should be doable and works nicely because I don't want to spend
much of the summer in my basement!
Tim
|