RE: [Gpsbabel-code] RE: Proposed release in June

[Tasse, E. <Eti...@cb...>]

ET>    It's a lot of new, untested code. Is it too late to add it for =
this June?
ET>    I've attached what is done, but has not been diff-ed into the =
latest CVS

RJL> I won't close the door for new formats, but I think they'd need to =
be in
RJL> pretty strong shape within a low number of weeks to make it.
RJL>=20
RJL> Not to single you out, as I realize this is in progress, but that =
would
RJL> include:
RJL>=20
RJL> * Doc.
RJL> * Diffs against trunk.
RJL> * Testsuite entries.
RJL> * Willingness to work with others if there are problems on other =
platforms

Commendable goals.  Everytime I checkout a version from CVS I have to =
spend time doing cleanup so it builds cleanly on MSVC/Windows. =20

The code I sent out earlier is not ready for CVS but can be useful to =
someone who wants a quick'n'dirty way to handle netstumbling files, =
provided one can build a customized gpsbabel themselves. In the =
meantime, the new formats are out there and can be looked at by peers.

One thing I am unclear of is 'Doc.'  What kind of documentation is =
required? Just a one page usage sheet or are we talking about design =
specs?  Is it for maintainers or users .. or both?

RJL> I just can't continue to spend dozens of hours cleaning these =
things up,=20
RJL> so I will be raising the bar on contributions.

Commit no code before it's time.