Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
Open Science Portal
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Open Data
Open Science Portal
Commits
6e42d427
Commit
6e42d427
authored
4 years ago
by
Tamas Gal
Browse files
Options
Downloads
Patches
Plain Diff
Update software development
parent
f4d04fcb
Branches
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#14718
passed
4 years ago
Stage: test
Stage: deploy
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
pages/Softwaredevelopment.md
+21
-1
21 additions, 1 deletion
pages/Softwaredevelopment.md
with
21 additions
and
1 deletion
pages/Softwaredevelopment.md
+
21
−
1
View file @
6e42d427
...
...
@@ -45,7 +45,27 @@ Optional but highly recommended CI jobs to automate are:
## Development Process
*TODO*
The main development branch is the
`master`
branch on Git and is meant to refer
to the latest stable version of the software. New features, experimental
implementations and bug fixing is done on separate branches and eventually
merged back to
`master`
after a code review and approvals of at least two
additional developers. The CI makes sure that the software is working as
expected and also indicates when the code coverage -- the fraction of untested
parts of the software -- is decreased upon a merge.
A separate job in the pipeline is set up to check the coding style automatically
and ensures a common style among the whole project.
To keep track of important additions, changes, bug fixes and deprecations, a
`CHANGELOG`
is available and updated accordingly. This files serves as an
overview for the users to keep track of the development process without spending
too much time to browse through closed issues and merge requests.
The versioning follow the Semantic Versioning 2.0.0 (https://semver.org)
conventions which indicates possible complications in up- or downgrading. The
version number consists of three parts in form of
`MAJOR.MINOR.PATCH`
, where
`MAJOR`
is increased on incompatible API changes,
`MINOR`
when new functionality
is added in a backwards compatible manner and
`PATCH`
for anything else, like
bug fixes or cosmetics etc.
## Python Project Template
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment