acmeattic-devel team mailing list archive

[Aditya Manthramurthy <aditya.mmy@xxxxxxxxx>]

On Wednesday 14 July 2010 04:17 AM, Karthik Swaminathan Nagaraj wrote:
> I don't know if this was read, now its a blueprint proposal.
> It includes most of the details that we discussed. I also put in all 
> Info that inspired me from Mercurial. It also discusses Binary diffs 
> which would be handled using a diff library written in C for performance.
>
> Karthik
I think we should keep this as an overall blueprint for the design of 
how storage and revisioning will be built. There are a few more things 
we need to define:

  1. How will renamed files be handled? Will they be considered as
     versions of the older named file? Or will it be a new file?
  2. What is the interval of time between a new revision will be backed
     up on the server?
  3. How configurable should the interval be? Per-file, hourly, daily, etc.

We should probably break it up into smaller blueprints, one for storage, 
one for revisions, one for concurrency issues, etc, when we start 
targeting these features against release milestones.

If we keep this as an overall design blueprint, then it will keep 
getting changed as we move from one release to another. It will be 
better if we write blueprints with more limited scope so that they can 
be easily targeted for release milestones.

--
Aditya.