erd-stockmanagement.rst

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
3.4.1 release
3.4.1 release
Since we don't have the previously saved builds anymore, I'm creating branches for past releases. I added a simple Jenkinsfile which has two main stages - build and ERD generation. The links in doc...

Since we don't have the previously saved builds anymore, I'm creating branches for past releases. I added a simple Jenkinsfile which has two main stages - build and ERD generation.
The links in docs now point to the last successful builds on release branches, so that we wouldn't have to update links if we decided to rebuild our API docs later on. Does this make sense?
I also wonder if it's alright to modify versions on readthedocs.com to use branches instead of tags, but then the label would change (from v3.3.0 to rel-3.3.0). Otherwise, we would have to modify tags in each repo. What do you think?

OLMIS-4963: Bring back lost ERD and static docs for past releases
OLMIS-4963: Bring back lost ERD and static docs for past releases
LGTM

LGTM

OLMIS-4840, fix UI doc links
OLMIS-4840, fix UI doc links