Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Tech words


Go to End


3 Posts   1076 Views

Avatar
Big Bang Creative

Community Member, 92 Posts

11 June 2009 at 9:10pm

Edited: 11/06/2009 9:12pm

There seems to be a lot of techy words used throughout the forums and documentation and I am sure I'm not the only one struggling to understand what each word is and what it means.

i.e.

- SVN
- Trunk
- Stable
- v2.3.2 RC2

Avatar
bummzack

Community Member, 904 Posts

11 June 2009 at 11:08pm

SVN: Subversion is a versioning software. Read here for further information: http://en.wikipedia.org/wiki/Subversion_(software)
Trunk: Usually this is the working copy when working with a version control system as subversion. Changes are made to trunk and are then "frozen" into branches when stable
Stable: A version that's considered stable :)
V2.3.2 RC2: Version 2.3.2, Release Candidate 2. You might want to look at this article, describing software development stages: http://en.wikipedia.org/wiki/Development_stage

HTH

Avatar
Willr

Forum Moderator, 5523 Posts

14 June 2009 at 10:07pm

And watch out we use Trunk / Daily Build interchangeably but when we say daily build it usually refers to the daily snapshot of trunk. Each module / component of SS has its own 'trunk' version.

On top of what banal has said - trunk is what we all work on day to day so this usually has new features, a few bug fixes (as well as a new few bugs).

A stable release is trunk (or a branch) at a point where its not going to change. Eg SS2.3.1 stable is code which isnt going to change, its been tested, a few RC (test) releases and we have declared it stable. At this time we update the site with the version / changelog and make an announcement of it. Stable = tested (in other words, stable (relatively)) and Trunk = relatively untested could be broken / work in progress.

RCs are test releases before we declare something stable. RCs are designed for the community to test, give feedback and report issues. These become a stable release after 3-4 weeks (we usually 1-3 RCs per stable release before we are happy that its stable enough)