Resolve tagging versions and Django versions discrepancies

[GoogleCodeExporter]

 I checked in fixes for signals and newforms into the trunk without realizing the trunk was not 
yet newforms. This is fine as the trunk will 'work' with the stub Admin classes 
for Django 1.0a. 
But now the trunk will no longer work for Django 0.96.

Due to other changes to tagging I am not sure when it last 'worked' with 0.96.
Should we find that version and tag it?
Should we actively try to get a 0.96 version working if none exists already?

At a minimum we should get the trunk working with the django trunk, including 
merging back 
newforms-admin and closing that branch.

I am looking for comments from people working with django-tagging and 
django-0.96. 
How important is this? (this means the real 0.96 with no unicode or 
autoescaping)

I do not see a reason to support django-0.97-pre (0.96 w/unicode + 
autoescaping), as there 
was no official release of that django and as such no fixed version of django 
to test against.

Original issue reported on code.google.com by doug.nap...@gmail.com on 11 Aug 2008 at 7:50

[GoogleCodeExporter]

fixing the settings on this...

Original comment by doug.nap...@gmail.com on 11 Aug 2008 at 7:51

• Changed state: Chatting
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Ok, its monday... that is the only excuse I have.

There is already a release for 0.96 and the trunk of tagging is for tracking 
the trunk of django.
There is no reason why nfa should not be merged into the trunk.
marking invalid.

Original comment by doug.nap...@gmail.com on 11 Aug 2008 at 11:41

• Changed state: Invalid
• Added labels: ****
• Removed labels: ****