How about if we just go back to "maxlength" for even the SVN tutorial,
and hold off changing the tutorial until the latest available release
of Django includes support for it? I don't normally like to cover for
people who can't be bothered to read *multiple* warnings telling them
not to shoot themselves in the foot, but this is just getting
ridiculous.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
Reverting trunk documentation due to stupidity is just silly.
I say we just keep closing tickets until the next release, at which
stage we make the latest release docs the default.
Sigh...
> How about if we just go back to "maxlength" for even the SVN tutorial,
> and hold off changing the tutorial until the latest available release
> of Django includes support for it? I don't normally like to cover for
> people who can't be bothered to read *multiple* warnings telling them
> not to shoot themselves in the foot, but this is just getting
> ridiculous.
I can't say I'm wild about this idea. This has the potential to just
reverse the problem - people that are trying the SVN version are going
to try the tutorial, and start logging bugs about the tutorial being
out of date.
I think we've just about hit the limit of what we can do here, short
of cutting a release. IMHO we've reached the point where we will just
have to live with the problem until we cut the next release.
Yours,
Russ Magee %-)