Release Management - Revision history

Michael: /* Testing */

2014-04-24T07:26:15Z

Testing

← Older revision		Revision as of 09:26, 24 April 2014
Line 73:		Line 73:
	Testing is done in a clean test environment and '''not''' in a developer environment.		Testing is done in a clean test environment and '''not''' in a developer environment.
	This means: all changes have to be committed to the git repository first and checked out from there in the test environment for proper testing.		This means: all changes have to be committed to the git repository first and checked out from there in the test environment for proper testing.

			* tests can be run on different levels
			** framework-level (symfony/php unit tests)
			** API-level:
			*** JSON Schema compliance
			*** client-test via [http://frisbyjs.com/ frisby.js]

	== Bug-Reporting/-Workflow ==		== Bug-Reporting/-Workflow ==

Michael: /* Committing */

2014-04-24T06:53:33Z

Committing

← Older revision		Revision as of 08:53, 24 April 2014
Line 57:		Line 57:
	See the [[Modularisation]] page for further details.		See the [[Modularisation]] page for further details.

	== Committing ==		== Committing / Git Workflow ==
			We follow the Git branching model according to: http://nvie.com/posts/a-successful-git-branching-model/

	Each change-set in the git repository (and thus each commit) ideally contains only one concise and consistent change.		Each change-set in the git repository (and thus each commit) ideally contains only one concise and consistent change.
	The commit-message precisely describes the change. If the change is in respond to a bug-report or feature-request, the number of the bug-report or feature-request is included.		The commit-message precisely describes the change. If the change is in respond to a bug-report or feature-request, the number of the bug-report or feature-request is included.

Michael: /* Committing */

2014-04-23T12:38:15Z

Committing

← Older revision		Revision as of 14:38, 23 April 2014
Line 60:		Line 60:
	Each change-set in the git repository (and thus each commit) ideally contains only one concise and consistent change.		Each change-set in the git repository (and thus each commit) ideally contains only one concise and consistent change.
	The commit-message precisely describes the change. If the change is in respond to a bug-report or feature-request, the number of the bug-report or feature-request is included.		The commit-message precisely describes the change. If the change is in respond to a bug-report or feature-request, the number of the bug-report or feature-request is included.

			== Scrum Labels ==
			* '''Not Started''': not yet assigned to or accepted by any member.
			* '''Assigned''': being assigned to or accepted by a member.
			* '''In Progress''': being implemented.
			* '''To Verify''': implementation done and now it is time for testing/verifying.
			* '''Done''': ticket is verified.

	== Testing ==		== Testing ==

Michael: /* Source Code Organization */

2014-04-18T08:35:40Z

Source Code Organization

← Older revision		Revision as of 10:35, 18 April 2014
Line 47:		Line 47:
	* https://github.com/stoney-cloud/stoney-core/web (Ajax based web interface)		* https://github.com/stoney-cloud/stoney-core/web (Ajax based web interface)

	Then we have the [[:Category:Self-Service Modules\|Self-Service ~~Module~~]] with [[:Category:stoney backup\|stoney backup]] as an example. This Self-Service Module provides an on-line backup service for desktops, servers and virtual machines.		Then we have the [[:Category:Self-Service Modules\|Self-Service Modules]] with [[:Category:stoney backup\|stoney backup]] as an example. This Self-Service Module provides an on-line backup service for desktops, servers and virtual machines.
	* https://github.com/stoney-cloud/stoney-backup		* https://github.com/stoney-cloud/stoney-backup
	* https://github.com/stoney-cloud/stoney-backup/api (REST '''a'''pplication '''p'''rogramming '''i'''nterface)		* https://github.com/stoney-cloud/stoney-backup/api (REST '''a'''pplication '''p'''rogramming '''i'''nterface)

Michael: /* Source Code Organization */

2014-04-18T08:35:28Z

Source Code Organization

← Older revision		Revision as of 10:35, 18 April 2014
Line 41:		Line 41:
	* https://github.com/stoney-cloud/stoney-gentoo-portage		* https://github.com/stoney-cloud/stoney-gentoo-portage

	The [[:Category:stoney core\|stoney core]]~~: Main framework~~ responsible for shared functionality		The main framework called [[:Category:stoney core\|stoney core]], which is responsible for shared functionality (like user management, rights and roles).
	* https://github.com/stoney-cloud/stoney-core		* https://github.com/stoney-cloud/stoney-core
	* https://github.com/stoney-cloud/stoney-core/api (REST API)		* https://github.com/stoney-cloud/stoney-core/api (REST API)

Michael: /* Source Code Organization */

2014-04-18T08:31:55Z

Source Code Organization

← Older revision		Revision as of 10:31, 18 April 2014
Line 35:		Line 35:
	= Development =		= Development =
	== Source Code Organization ==		== Source Code Organization ==
	~~We have the~~ stoney cloud related ~~repositories like installer, node~~-~~integration~~, ~~... These we keep as is (for~~ the ~~moment)~~.		All stoney cloud related source code is located on GitHub under https://github.com/stoney-cloud. To avoid clashes with over projects, every repository has the default prefix '''stoney-'''.

	~~The web interface consists a bunch of modules~~. ~~Each module has a separate GitHub git repository containing the following sub~~-~~structure~~:		Some operating system related examples:
			* https://github.com/stoney-cloud/stoney-gentoo-overlay
			* https://github.com/stoney-cloud/stoney-gentoo-portage

	~~GitHub~~:		The [[:Category:stoney core\|stoney core]]: Main framework responsible for shared functionality
	* Form follows function: ~~we choose the~~ functionality ~~name (so we are backwards compatible)~~		* https://github.com/stoney-cloud/stoney-core
	* ~~Modules are collected in one repository (create a skeleton module as an example)~~:		* https://github.com/stoney-cloud/stoney-core/api (REST API)
	** Data (~~LDAP~~)		* https://github.com/stoney-cloud/stoney-core/cli (Command Line Interface)
	** API (~~PHP)~~		* https://github.com/stoney-cloud/stoney-core/web (Ajax based web interface)
	** Web Interface ~~(PHP, uses API~~)
	** Provisioning (Perl, .~~..)~~
	** Tests (~~GUI, Unit-Tests, ...~~)

	~~See~~ the [[~~Modularisation~~]] ~~page~~ for ~~details~~.		Then we have the [[:Category:Self-Service Modules\|Self-Service Module]] with [[:Category:stoney backup\|stoney backup]] as an example. This Self-Service Module provides an on-line backup service for desktops, servers and virtual machines.
			* https://github.com/stoney-cloud/stoney-backup
			* https://github.com/stoney-cloud/stoney-backup/api (REST '''a'''pplication '''p'''rogramming '''i'''nterface)
			* https://github.com/stoney-cloud/stoney-backup/cli ('''c'''ommand '''l'''ine '''i'''nterface)
			* https://github.com/stoney-cloud/stoney-backup/helpers (helper scripts and programmes)
			* https://github.com/stoney-cloud/stoney-backup/provisioning (scripts and programmes to provision services)
			* https://github.com/stoney-cloud/stoney-backup/web (Ajax based web interface)

	~~All stoney cloud related source code is located on GitHub under https://github.com/stoney-cloud. To avoid clashes with over projects, every repository has~~ the ~~default prefix '''stoney-'''~~.		See the [[Modularisation]] page for further details.

	== Committing ==		== Committing ==

Michael: /* Source Code Organization */

2014-04-18T08:15:29Z

Source Code Organization

← Older revision		Revision as of 10:15, 18 April 2014
Line 50:		Line 50:
	See the [[Modularisation]] page for details.		See the [[Modularisation]] page for details.

	All stoney cloud related source code is located under https://github.com/stoney-cloud		All stoney cloud related source code is located on GitHub under https://github.com/stoney-cloud. To avoid clashes with over projects, every repository has the default prefix '''stoney-'''.

	== Committing ==		== Committing ==

Michael: /* Source Code Organization */

2014-04-18T08:13:02Z

Source Code Organization

← Older revision		Revision as of 10:13, 18 April 2014
Line 49:		Line 49:

	See the [[Modularisation]] page for details.		See the [[Modularisation]] page for details.

			All stoney cloud related source code is located under https://github.com/stoney-cloud

	== Committing ==		== Committing ==

Michael: /* Development Procedure */

2013-10-18T08:34:44Z

Development Procedure

← Older revision		Revision as of 10:34, 18 October 2013
Line 30:		Line 30:
	* Features are scheduled on the individual module [[:Category:Roadmap\|roadmap]] pages for implementation in specific future stable versions and are implemented (and tested) in development versions.		* Features are scheduled on the individual module [[:Category:Roadmap\|roadmap]] pages for implementation in specific future stable versions and are implemented (and tested) in development versions.
	* A new major version will be released, when all features and goals specified for this version are implemented and tested.		* A new major version will be released, when all features and goals specified for this version are implemented and tested.

			TBD: Describe stable and unstable in more detail

	= Development =		= Development =

Michael: /* Versioning */

2013-10-16T12:15:43Z

Versioning

← Older revision		Revision as of 14:15, 16 October 2013
Line 17:		Line 17:
	* New features are added to unstable/development versions only.		* New features are added to unstable/development versions only.
	* We have separate version numbers for the separate components (installer, online-backup, ldap-schemas, ...).		* We have separate version numbers for the separate components (installer, online-backup, ldap-schemas, ...).

			We start with '''0.1.0''' for development and '''0.2.0''' for first stable release.

	= Development Procedure =		= Development Procedure =