Release and Commit policy

Jump to bottom Edit New page

cybunk edited this page Apr 9, 2013 · 6 revisions

Release policy

Commit policy

List the modifications resume in VERSIONS.md in Next version section
start your line with ADD if you add a feature or FIX if you fix a feature

Version number

When a lot of modifications have been made, and their are stable, we make a new version. For that we follow thoses steps :

List the modifications resume in VERSIONS.md
Tag the commit : git tag -a v0.0(n+1) -m 'visusal sedimentation version 0.0(n+1)'
Commit the lib : git commit -m "v0.0(n+1): my message"

Deployment check list

Verify files or folder you don't want to publish are in .gitignore
TEST on local, all /exemples/* for retro compatibility
Minify the lib : build/ant
Commit the lib : git commit -m "v0.0(n+1): my message"
TEST the website :
Log in the visualsedimentation.org Web Server
Go on the visualsedimentation.org/dev/VisualSedimentation/ directory
And pull the last version : git pull
TEST online if everything work
DEPLOY the website :
Copy the files from visualsedimentation.org/dev/VisualSedimentation/ to visualsedimentation.org/