On Jul 16, 6:19 am, Dan <[EMAIL PROTECTED]> wrote:
> I'm starting the project in two weeks, hopefully, it will be merge then.
Don't worry about it being merged with trunk. From what I understand
changes from trunk are merged into newforms-admin branch on a weekly
basis (that is, if they are follo
I'm starting the project in two weeks, hopefully, it will be merge then.
I cross my fingers.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@goo
According to:
http://code.djangoproject.com/wiki/VersionOneRoadmap#must-have-features
newforms-admin is a high priority.
If you haven't already, take a look at:
http://code.djangoproject.com/wiki/NewformsAdminBranch
http://code.djangoproject.com/wiki/NewformsHOWTO
They're both *really* helpful,
I assumed that trunk would be moving in the newforms-admin direction,
so I've switched already. I would rather do it now than have to
backport stuff later...
Thanks!
Jon Brisibn
http://jbrisbin.com
On Jul 15, 2008, at 3:50 PM, Dan wrote:
> Should I start with the nfa branch or with trunk a
Should I start with the nfa branch or with trunk and update the code when it
is merged? Is there risks of breakage in nfa? Other issues?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to
On Jul 15, 3:30 pm, Jason <[EMAIL PROTECTED]> wrote:
> ...and it is: if I were to switch my current django project over to
> newforms-admin branch, would it break all of the old admin pages?
Yes.
> Or
> is there legacy support built in?
It isn't. But the following snippet might help create q
...and it is: if I were to switch my current django project over to
newforms-admin branch, would it break all of the old admin pages? Or
is there legacy support built in?
Thanks mucho in advance!
--~--~-~--~~~---~--~~
You received this message because you are sub
7 matches
Mail list logo
