Rare project developers

[Frédéric LOUI <>]

> . Maybe that makes more sense anyway?
Sure ! 

I’m opened to any suggestion that would facilitate your (also everyone's) 
work and that obviously would make sense to everyone.

I declared you as admin on:
- https://github.com/rare-freertr/RARE-web. ( <----- mkdocs sources )
- https://github.com/rare-freertr/docs.freertr.org ( <----- serialised HTML 
files, médocs output)

Please let me know if this is fine for you.

If you are not familiar to mkdocs workflows we can have a quick sync VC.

One thing I’ve in my wish list is to create a docs based of git or release 
tag. 
(Part of the doc can be generated automatically after a specific commit …)
If anyone know how to do that please get back to me.

For example in this link: you see the docs is related to a specific release: 
https://projectcalico.docs.tigera.io/about/about-calico
Version is 3.22 with tag "latest" and nightly is "main"

But maybe we can leave it for near future. Meanwhile we can create on the 
left a section called: « Release »

Please let me know your thoughts,

All the best,
Frederic

> Le 21 avr. 2022 à 16:32, Alexander Gall <> a écrit :
> 
> Hi Fréderic
> 
> I'd like to create a Release Notes file in the RARE-NIX repo for each
> release. I did this for the test releases, see
> https://bitbucket.software.geant.org/projects/RARE/repos/rare-nix/browse/release-notes
> how this could look like.
> 
> For the first release, I'm planning to simply put a reference to
> http://docs.freertr.org/, but in future releases I'd like to include
> what one would expect from the release notes, i.e. new features, bug
> fixes, etc.
> 
> Instead of adding it to the repo, we could also add the Release Notes
> to http://docs.freertr.org/. Maybe that makes more sense anyway?
> 
> -- 
> Alex