Re: Requirements for Documentation System
| From: | Stefan Neufeind | Date: | Mon, 12 Apr 2004 22:48:54 +0000 |
| Subject: | Re: Requirements for Documentation System | ||
| References: | 1 | Groups: | php.pear.doc |
| Request: | Send a blank email to pear-doc+get-3289@lists.php.net to get a copy of this message | ||
On 13 Apr 2004 at 0:36, Cipriano Groenendal wrote:
> > >>>>> 5. Fast turnaround between edits and displayed results.
> > Agreed. Let us say we are talking about a trusted team, as per the
> > above paragraph describing the PEAR-DEV problem. Are we OK for
> > "instantly" under that assumption?
> With a
roll-back in place, this would be a Good Thing(TM) yes.
Since rollback and mailing to the lists etc. is already present in
the current solution, shouldn't we maybe stick to CVS on the backend?
Working with revision-tags etc. always seemed quite helpful. Imho we
might bring an easy interface for instant editing of file etc., but
the changes might be commited back to a CVS to handle the archive and
mailings for us?
Oh, in that discussion I see a small problem: Instant updating versus
versioning. Imho instant updating while editing should be restricted
to a "Preview"-button, and clicking on "Save" should be avoided until
reasonable changes have undergone - otherwise we would end up with
multiple versions just for adding a word and then thinking it might
just be better to remove it again or something :-))
Sorry, this mail was about techniques (CVS) - but I think we should
already consider if we can use the existing backend somehow, or if it
really needs replacement.
Stefan