Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

addition of release process #267

Closed
wants to merge 1 commit into from
Closed

addition of release process #267

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
.vscode
.idea
.pdf
2 changes: 1 addition & 1 deletion BDNS_Governance_model.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

# Building Device and Asset Naming Standards initiative

Status: *release 1.1.0*
Status: *work in progress 1.2.1*

## Governance model

Expand Down
31 changes: 31 additions & 0 deletions BDNS_Release_process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Building Device and Asset Naming Standards release process

Status: *work in progress 1.2.1*

## Work in progress

While working on abbreviations and specification files between
releases, each text `.md` file will be tagged manually at the top,
just below the document title, with the following status line:

Status: *work in progress #.#.#*

The "work in progress" status will signal the fact that the files are
not part of a release and under development.

## Release

At the time of the release, each text `.md` file will be tagged
manually at the top, just between the document title, with the
following status line:

Status: *release #.#.#*

Once the release status line has been updated in all the `.md` files
the repository is ready for a GitHub release, that can be done
following the standard [GitHub release procedure](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository).

If new pull requests are merged after a tagged release, the first
developer creating a pull request will ensure to revert the "release"
status to "work in progress" status in all the `.md` files.

3 changes: 2 additions & 1 deletion BDNS_Scoping_guidelines_and_principles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@

# Building Device and Asset Naming Standards initiative

Status: *release 1.1.0*
Status: *work in progress 1.2.1*

## Scoping guidelines and principles

# Context and background
Expand Down
2 changes: 1 addition & 1 deletion BDNS_Specification_naming_syntax.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Building Device and Asset Naming Standards initiative

Status: *release 1.1.0*
Status: *work in progress 1.2.1*

# Specification for naming syntax

Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Building Device and Asset Naming Standards initiative

Status: *release 1.1.0*
Status: *work in progress 1.2.1*

This repository holds resources for an initiative to improve interoperability in building management, by focusing on standardising naming of building devices and assets.

Expand Down
Loading