The web app now presents error pages for edits again, validates objects
for being consistent before saving them (not just the web app), we have
batch editing working, and misc. cosmetic improvements (uppercase in a
few areas). Subprofiles should work better. Lots of random things.
I think it's mostly usable, though there are a few forms that should
still end up on the error pages, rather than showing the Django debug
pages, but not too many.
I also suspect the "check_if_valid" code needs a bit of enhancement, and
we need to pound on things pretty hard to see what breaks.
Anyway, please test away, and why you are doing so, make a note of
anything that just looks broken/unfinished when compared with the old
webapp.
I know of a few such items -- the way the DIVs dump text below the
navigation half of the time is certaintly one of these.
I'd also try to break the interface editor, or any of the editors, and
see what works/doesn't ...
The CLI could probably use equivalent bashing, I know --in-place doesn't
currently work, there are probably a few other options that don't work
since the refactoring.
It would be best if testing could be done against an old copy of the
cobbler objects (like your production copy), but obviously don't run
devel against production -- it may very well clobber your configs. But
making sure the data is preserved across the upgrade here is pretty
important, so feeding it old data would be useful.
I'm going to be doing more testing myself of course in the next week,
but the idea now is to get what we have back to "Cobbler 1.6.5 feature
equivalence" state, running off the new codebase, before adding anything
new.
Thanks!
--Michael