Please view the page ((GetCode)) for details.
|
|
!! How do I get the latest and greatest of bitweaver? (beta release)
|
-you need access to CVS. to set up cvs and how to use it, please view:
|
+you need access to CVS. To set up CVS and how to use it, please view: |
bitweaverCVS
|
|
!! How can I get hold of packages that haven't been released yet?
|
-try accessing [/builds/packages] and see if the package is available for testing. if it's not available there, you can get it using cvs. for a list of available packages, you can check out CVSROOT and look in the modules file. with most packages, the cvs module name is _bit_<package> (e.g.: use _bit_wiki for the wiki)
|
+Try accessing [/builds/packages] and see if the package is available for testing. If it's not available there, you can get it using CVS. For a list of available packages, you can check out CVSROOT and look in the modules file. With most packages, the CVS module name is _bit_<package> (e.g.: use _bit_wiki for the wiki) |
|
!! What is happening in CVS? How stable is CVS?
|
-CSV branch R1 is considered stable and only bugfixes are going into R1. we have got a database schema as well as an api lockdown. This means that you can update using the cvs R1 branch without much concern. obviously, we're not miracle workers and we suggest you backup your file / database before upgrading (expecially after a prolonged period). for upgrade instructions, please view bitweaverUpgrade
|
+__CSV branch R1__ (versions 1.3 of Bitweaver) is stable, but not updated anymore. It's got a database schema and API lockdown. Also, there are known security problems with Bitweaver below version 2, depending on your specific packages/feature set. However, you can update using the CVS R1 branch without harming your install. Backup your files and database before. For detailed upgrade instructions, please view ((bitweaverUpgrade)). |
+ |
+__CVS branch R2__ (versions 2 of Bitweaver) is also available. While many version 2 live sites are being updated directly from CVS (mainly the ones that the developers are running), you need to do extensive testing after an upgrade. An alternative to CVS are weekly builds in [http://bitweaver.org/builds]. It's an advantage to monitor changes via IRC, if you plan on running your site off CVS in the sense of frequently updating your code to the most recent. |
+ |
+__Final releases__ (versions) are made from the code in CVS after extensive testing and debugging (unlike weekly builds). For the highest quality, this process of coding, testing, and releasing takes several months between versions of Bitweaver. See also [/articles/102|Help Wanted]. |
+ |
|
---
|
|
! Installs, Migrations and Upgrades
|
!! How do I install bitweaver?
|
-[http://sourceforge.net/project/showfiles.php?group_id=141358&release_id=336854|Download bitweaver] and unpack it in a place of your choice. Point your browser to install/install.php, and follow the on screen instructions. After installation, for security reasons we recommend that you set the permissions of your install directory so that users cannot access it.
|
+[/downloads/gallery/15488|Download bitweaver] and unpack it in a place of your choice. Point your browser to install/install.php, and follow the on screen instructions. After installation, set the permissions of your install directory so that users cannot access it. To see what the installer does, before actually installing Bitweaver, [/downloads/file/15256|watch: Bitweaver Installation (Screencast)]. |
|
!! What files should I take care of when upgrading?
|
Please view the page ((bitweaverUpgrade)) for details.
|