Personal tools
You are here: Home Products Plone Roadmap #70: Simple Version Control
Document Actions

#70: Simple Version Control

Contents
  1. Motivation
  2. Proposal
  3. Implementation
by Alexander Limi last modified June 11, 2006 - 00:21
Proposed by
runyaga
Proposal type
State
rejected

Motivation

ZODB Transactions do not provide semantics or durabiltiy for
a good versioning solution. We need something people can
build Staging implementations around.

Proposal

The goal of landing versioning in Plone is provide higher level
services to the Plone CMS. These services will mostly add on
top of existing products/api - CMFStaging and ZopeVersionControl.
There have been many different versioning implementations from
PloneStaging, Occams, EnSimpleStaging, CMFEditions and many others.
Typically all of these "versioning" solutions revolve around
the concept of staging. Staging refers to the movement/processing
of a logical grouping of content in a particular state. i.e.
making a group of content "live" on the server. Staging is very
sensitive to the way the client works so its likely there will
always be many different staging implementations.

Implementation

I documents. Why is a PLIP not containerish for the assets that
support a PLIP?


For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by