History of ReleaseOne
Version 23 | Current version | |
---|---|---|
The main goals of
Database:
Blogs: - Add check boxes for pings to major directories like Technocrati, and weblogs.com - Add Atom API support - Be able to promote blog enteries to the front page. Newsletter: - Newsletter\'s content should be database driven. - Integrate PHPList? Tiki Cloud: - Create tiki cloud similar to Drupals to keep track of all the different TP sites. - Could keep track of stats of different sites. - Related to Database issue above about sharing info between sites in same DB? Testing: - Implement phpUnit for testing of core and packages - Relies on all coding to be in classes, possibly a nice-to-have for Clyde Enhancements: - implement FeaturePackages and/or PackageVisionBtodoroff - consider implementing phpGACL - browser specific css import - implement IconThemes
- remove kernel dependencies of packages - auto-generate Admin panel/Menus/Feature list - centralisation of pagination (<div class="pagination"> occurs about 115 times (bonnie 29-04-2004)) - this is underway and is now function_pagination - some sort of systematic and consise menu standard Optimizations: - Trim down TikiLib as much as possible by moving relevant functions into package classes - Update or Remove QuickTags so data base access is not required for every page load to draw tool bar - Move all third party code such as AdoDB, Smarty, PEAR, etc - to sit under utils/ - this will ensure code separation and modularity. | Goals and AccomplishmentsThe main goals of ReleaseOne were to make the full transition to our modular architecture. Initially ReleaseOne shipped with the following Packages:
In process of development:
This means initially ReleaseOne does not support everything from the ReleaseZero codebase. An upgrade script is available that will migrate data from ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and bitweaver and TikiWiki 1.8 and ReleaseZero to ReleaseOne. DownloadsZipped distributions are available from sourceforge.ReleaseOne CVSThe best way to get the code is via CVS. All the lead developers run live sites off CVS and you should too. It can be considered very stable. To do this:General Access: Note this method users a mirrored CVS and has a 24+ code delay with the :ext: method indicated below.
Developer Access: If you are an active member of the project use:
Key Architectual Improvements
Key Blog Improvements
Key Wiki Improvements
New Packages
Thanks |