tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-07-01 00:49:33 +02:00
Code Issues Projects Releases Wiki Activity

MINOR Fixed from-source docs, added 'preview' release cycle to release-process docs

Browse Source
This commit is contained in:
Ingo Schommer 2011-05-02 08:44:09 +12:00
parent 71bc87fa1e
commit b21dbd9641
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/en/installation/from-source.md
View File

@ -149,7 +149,8 @@ Please replace `<username>` below with your github username.
cd my-silverstripe-project
git clone git@github.com:<username>/sapphire.git sapphire
git clone git@github.com:<username>/silverstripe-cms.git cms
git clone git@github.com:<username>/silverstripe-blackcandy.git themes/blackcandy
rm -rf themes
git clone git@github.com:<username>/silverstripe-blackcandy.git themes
Now you need to add the original repository as `upstream`, so you can keep your fork updated later on.

2
docs/en/misc/release-process.md
View File

@ -37,6 +37,8 @@ for stability and regression testing. Naming convention is *A.B.C-alpha* and *A.
* Major, minor and micro releases can have one or more *release candidates (RC)*, to be used by the wider community. A
release candidate signifies that the core team thinks the release is ready without further changes. The actual release
should be a identical copy of the latest RC. Naming convention is *A.B.C-rc1* (and further increments).
* Major releases may have a *preview* cycle which is a early snapshot of the codebase for developers before
going into the *alpha* cycle. Preview releases are named *A.B.C-pr1* (and further increments).
### Major releases