Changes between Version 19 and Version 20 of DjangoBranches


Ignore:
Timestamp:
09/05/08 19:47:59 (7 years ago)
Author:
simon
Comment:

No active branches at this time

Legend:

Unmodified
Added
Removed
Modified
  • DjangoBranches

    v19 v20  
    99== Active Branches ==
    1010
    11 === Database layer ===
    12  * [wiki:SchemaEvolution]: This is a new feature, under development as a project for the 2006 Summer of Code.
    13  * [wiki:RowLevelPermissions]: Currently Django's permission system only works at the level of an entire model -- e.g., user "Bob" has access to add flatpages and edit users. This Summer of Code project will extend the permission system to be much more fine-grained, so permissions will be able to be assigned per object instead of per model (so, for example, user "Bob" could be given permission to edit only flatpage number 24 and user number 12, instead of all flatpages and all users).
    14  * Generic relations: a "generic foreign key" feature is currently under development, but not yet completed. There is no support for it yet in the admin application, and it is probably unwise to attempt to use it in a production application.
    15 
    16 === Other ===
    17  * [wiki:GenericAuthorization]: A more flexible authorization system for Django. The new system should allow for ACL's, role-based systems, and Django's current model-level permissions.
    18  * [wiki:FullHistory]: A "full content history" implementation with compare, revert, etc. A SoC 2006 project.
    19  * [wiki:TextIndexingAbstractionLayer]: An abstraction layer for full-text indexing and search engines such as Lucene, Xapian, and Hyper Estraier. Also known as Merquery, this Summer of Code project will most likely be placed in contrib.search.
     11There are no active branches at this time.
    2012
    2113== Creating New Branches ==
Back to Top