[development] Requiring node revisions

[Larry Garfield]

On Thursday 07 June 2007, David Strauss wrote:

> > Furthermore, the most important "visual artifact" of node revisions is
> > not the "create new revision" checkbox, but the fieldset/textarea for
> > the log message that is always expanded (fixed in D6).  I argue that it
> > is mainly the textarea that is confusing and that feels like
> > clutter/overkill -- especially because the checkbox and the log message
> > are not logically grouped. The proposed change sounds somewhat
> > counter-productive because the log message textarea would become more
> > prominent (while the checkbox goes away).  Not sure if we win or loose
> > ...
>
> Then maybe we should move toward having a revisions cleanup system that,
> by default, deletes all old revisions. It would still be a big code
> simplification. If the system is set to keep no old revisions,
> node.module can simply delete old revisions after saving the new one.

I believe I said that ~20 messages ago. :-)  

If we're going to have an "always on" revision system, then it really does 
need to include a self-cleaning mechanism by default as well.  Otherwise you 
have a system that takes more effort to maintain, or else never lets you 
delete anything.  Let's not be Google. 

-- 
Larry Garfield			AIM: LOLG42
larry at garfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of 
exclusive property, it is the action of the thinking power called an idea, 
which an individual may exclusively possess as long as he keeps it to 
himself; but the moment it is divulged, it forces itself into the possession 
of every one, and the receiver cannot dispossess himself of it."  -- Thomas 
Jefferson