Skip to content

Commit

Permalink
ReleaseProcess: Adapted to the current working mode (#141)
Browse files Browse the repository at this point in the history
ReleaseProcess: Adapted to the current working mode

The previous process description was not up to the current working mode. Now updated.

Fixes: #140
  • Loading branch information
danielwilms authored Mar 26, 2020
1 parent 5f0c890 commit f31feeb
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 20 deletions.
31 changes: 11 additions & 20 deletions RELEASE_PROCESS.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@

**(C) 2016 Jaguar Land Rover**<br>

All files and artifacts in this repository are licensed under the
Expand All @@ -8,33 +7,25 @@ provisions of the license provided by the LICENSE file in this repository.
This document describes the process for creating a new version of the
signal specification.

The process, driven by the GENIVI Remote Vehicle Interaction Expert
Group (RVI EG), is aimed at being lightweight and carried out in public, giving both
GENIVI members and non-members a say in the creation of a new version.
The process, driven by GENIVI with significant input from the W3C Automotive WG, is aimed at being lightweight and carried
out in public, giving both GENIVI members and non-members a say in the
creation of a new version.

![Release Process](pics/vss_release_process.png)

In git, the ```develop``` branch is used as an integration branch
In git, the ```master``` branch is used as an integration branch
accepting pull requests with new and modified vpsec files from
contributors.

Pull requests are reviewed in the public genivi
list ```genivi-projects@lists.genivi.org```. Once the review process
has concluded, the RVI EG decides if the pull request is to be
accepted or not.

A new signal specification release is created by an RVI weekly meeting decision
where at least 50% of the present vote for a new release.
Pull requests [PR] are **always** initiated from a **fork** and not through
a feature branch in the main repository. PRs are reviewed, discussed and merged
through the public github repository.
A PR is merged earliest after one week to give a fair chance of reviewing.

Each release is incrementally numbered, starting with 1.

A release is tagged in git with the tag

ver_[n]
v[n]

where [n] is the release number.







Binary file added pics/vss_release_process.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit f31feeb

Please sign in to comment.