Opened 18 years ago
Closed 18 years ago
#4350 closed (wontfix)
Branch is out of sync (multiple-db-support)
| Reported by: | Owned by: | Jacob | |
|---|---|---|---|
| Component: | *.djangoproject.com | Version: | other branch |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Multiple Database branch is currently out of sync, maybe there could be some 'automerge' mechanism to keep branches updated if it's developer wants to.
The branch itself is so out of sync that it's merge will keep somebody busy for a while ;)
Keeping branches in-sync would allow people to test them without leaving the bleeding-edge stuff on trunk/ which seems to be the main reason there's so lack of testing on branches.
Also you could issue svn del <..> on the completed branches to clean up [source:django/branches] a bit.
Note:
See TracTickets
for help on using tickets.
Automatic syncing is not a good idea -- the person doing the merging should be reading the diffs and updating any necessary merges that might cause problems. Not all problems are shown as subversion conflicts.
Since the multi-db branch doesn't have an active maintainer at the moment, it won't be merged until that situation changes.