History of ReleaseOne

{maketoc}

!Goals and Accomplishments
The main goals of ReleaseOne were to make the full transition to our modular architecture. Initially ReleaseOne shipped with the following Packages:
# Core (KernelPackage, CategoriesPackage, LibertyPackage, UsersPackage)
# BlogsPackage
# WikiPackage
# PhpBBPackage
# FisheyePackage (image galleries)
# Gallery2Package
# GatekeeperPackage (content security)
# CategoriesPackage
# HotwordsPackage
# LanguagesPackage
# MessuPackage
# NexusPackage
# PdfPackage
# QuotaPackage
# TinymcePackage
# StickiesPackage
# StatsPackage
# RssPackage
# and more! Additional packages will be added depending on community interest
and involvement

In process of development:
# ArticlesPackage
# GalaxiaPackage (workflow)

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.

!Downloads
[http://sourceforge.net/project/showfiles.php?group_id=141358|Zipped distributions are available from sourceforge].

!ReleaseOne CVS
The 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.
{code in="Bash"} cvs -d :pserver:anonymous@bitweaver.cvs.sourceforge.net:/cvsroot/bitweaver co -r R1 bitweaver{code}
__Developer Access:__ If you are an [https://sourceforge.net/project/memberlist.php?group_id=141358|active member of the project] use:
{code in="Bash"} cvs -d :ext:yourusername@bitweaver.cvs.sourceforge.net:/cvsroot/bitweaver co -r R1 bitweaver{code}

!Key Architectual Improvements
# Make all foreign keys immutable (i.e. use user_id instead of username, and page_id instead of page_name
# Introduction of the LibertyPackage base table
# Rename all column names to be lowercase_with_underscores
# Increase modularity to allow Packages to be removed entirely, or added arbitrarily
# Increase speed, and continue cleanup of code base

!!Key Blog Improvements
* Rewrote blog post images code so that it now uses the tiki_storage table instead of storing files in the db
* Fixed many bugs associated with posting, viewing, creating, and emailing blogs and blog posts.


!!Key Wiki Improvements
* Migrate to the LibertyPackage architecture (spider)
* Conversion of all foreign keys from page_name to use page_id (spider)
* Permit pages with the same name (spider)

!New Packages
* FisheyePackage
go to NewPackages

!((ReleaseOneThanks|Thanks))