Commit 22b04808 authored by Javier Velázquez's avatar Javier Velázquez
Browse files

Update README

parent 0975ffba

README.md

+14 −0
Original line number Diff line number Diff line
@@ -25,6 +25,7 @@ The Network Slice Controller (NSC) is a component defined by the IETF to orchest 
   - [Ixia Configuration](#ixia-configuration)  

   - [WebUI](#webui-1)  

9. [Usage](#usage)  

10. [Available Branches and Releases](#available-branches-and-releases)



---
@@ -175,3 +176,16 @@ To use the NSC, just build the image an run it in a container following these st 


    Send slice requests via **API** (/nsc) or **WebUI** (/webui)



## Available branches and releases



[![Latest Release](https://labs.etsi.org/rep/tfs/nsc/-/badges/release.svg)](https://labs.etsi.org/rep/tfs/nsc/-/releases)



- The branch `main` ([![pipeline status](https://labs.etsi.org/rep/tfs/nsc/badges/main/pipeline.svg)](https://labs.etsi.org/rep/tfs/nsc/-/commits/main) [![coverage report](https://labs.etsi.org/rep/tfs/nsc/badges/main/coverage.svg)](https://labs.etsi.org/rep/tfs/nsc/-/commits/main)), points always to the latest stable version of the TeraFlowSDN Network Slice Controller (NSC).



- The branches `release/X.Y.Z`, point to the code for the different release versions indicated in the branch name.

  - Code in these branches can be considered stable, and no new features are planned.

  - In case of bugs, point releases increasing revision number (Z) might be created.



- The `develop` ([![pipeline status](https://labs.etsi.org/rep/tfs/nsc/badges/develop/pipeline.svg)](https://labs.etsi.org/rep/tfs/nsc/-/commits/develop) [![coverage report](https://labs.etsi.org/rep/tfs/nsc/badges/develop/coverage.svg)](https://labs.etsi.org/rep/tfs/nsc/-/commits/develop)) branch is the main development branch and contains the latest contributions.

  - **Use it with care! It might not be stable.**

  - The latest developments and contributions are added to this branch for testing and validation before reaching a release.