node revisions ?
mojzis - March 21, 2009 - 18:27
| Project: | Deployment |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Jump to:
Description
I think it would be useful to work with revisions, thinking about ways :
- on the destination force a revision for each deploy (the log message would have to be automatic)
- upload the node with its revision(s) from the source server (question is whether to take only the last rev, or which ones to take ...)
It is probably more of an issue for services ? I havent seen anything revision related in their open issues.
thanks
#1
It would be a problem for both me AND Services to support revisions. Unfortunately I don't think this is going to happen in the current version. However it is a good feature, so I am marking it Postponed.
#2
Subscribing - I'd love to have support for revisions.
#3
This feature makes sense to have implemented. So right now there's no roll back functionality on the destination server after a deploy (?), but there could be on the source server though, right, at least for simple node updates?
#4
So the major problem with implementing 'revisions support' is the services module? Do you want me to see if I can figure out a work-around? It should be possible since you have to have deploy installed on both staging and production machines.
#5
I'm having a hard time seeing how revisions fit into deploy. Do people want to be able to push a specific revision? To push all revisions when a node is deployed? I'd like some thoughts on how this would work.
#6
While I personally don't see a need for it in most sites, the project I just signed on with has to meet some strict government documentation standards. Enabling revision support in deployment would simplify the process, keep it all in Drupal without any outside scripts, and make it more reliable.
By the way, as part of the project I'm on, I'd like to help you maintain the project and close out some TODOs. Could I help out as a maintainer?
-John W
#7
I still don't understand what you want deploy revision control to do. If you have four revisions on the local server, do you want them all to move to the live server when you push? If you have revisions turned on on the remote server, a revision will currently be created when the node is pushed. I guess I still don't understand what this feature should look like.