Or perhaps you have a test server which is running the same codebase
as prod?
Yes. We have a development server running 0.95 that matches our
production server.
Generally there hasn't been much different from 0.95 to trunk so I've
been keeping up to date with trunk on my workstation just to
On 12/18/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
in changeset 4208 all the code from django/forms was copied to
django/oldforms. Isn't that a little bit twisted? Now there's the
same code twice, and any future patch for forms needs to address
both trees.
Good point, Michael. I've remove
On 12/21/06, Rob Hudson <[EMAIL PROTECTED]> wrote:
Would Michael Radziej's suggestion work better for those who develop
against trunk but whose servers are running stable releases (ie: 0.95)?
That's my case and I just ran up against this issue.
If you're doing that in the expectation that ru
Would Michael Radziej's suggestion work better for those who develop
against trunk but whose servers are running stable releases (ie: 0.95)?
That's my case and I just ran up against this issue.
For now, I'm going to revert my local workstation to using 0.95.
--~--~-~--~~---
On 12/18/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> in changeset 4208 all the code from django/forms was copied to
> django/oldforms. Isn't that a little bit twisted? Now there's the
> same code twice, and any future patch for forms needs to address
> both trees.
>
But only for th
Hi,
in changeset 4208 all the code from django/forms was copied to
django/oldforms. Isn't that a little bit twisted? Now there's the
same code twice, and any future patch for forms needs to address
both trees.
This may not be a big problem for the core development of django,
but I guess ther
