Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Updated documentation for v3.7.0

    • binary
    ./releases/UI-Performance-3.7.png
    • -0
    • +236
    ./releases/openlmis-ref-distro-v3.7.0.rst
Added link to 3.7 release notes.

Completed the 3.7 release notes.

    • binary
    ./releases/UI-Performance-3.7.png
    • -0
    • +236
    ./releases/openlmis-ref-distro-v3.7.0.rst
Prepared ref-distro for the next release

  1. … 1 more file in changeset.
Updated documentation for v3.7.0

  1. … 1 more file in changeset.
Added info about upgrading Stock Management service from 4.0.1

    • -0
    • +4
    ./releases/openlmis-ref-distro-v3.6.0.rst
Prepared repository for next release

  1. … 1 more file in changeset.
Update documentation to v3.6 versions

To 3.6 versions of documentation, and 3.6 versions of build artifacts.

  1. … 1 more file in changeset.
Are there other location types that we may need to consider? If so, would we want this description to be more general?

Are there other location types that we may need to consider? If so, would we want this description to be more general?

OLMIS-5584, typos and suggestions from doc review

Geographic

Geographic

Is it likely that an ERP system might be the source of truth for this kind of data, rather than OLMIS? I am thinking of a country that wants to use OpenLMIS primarily for the requisition process bu...

Is it likely that an ERP system might be the source of truth for this kind of data, rather than OLMIS? I am thinking of a country that wants to use OpenLMIS primarily for the requisition process but leverage an existing ERP system for inventory-related processes.

Would OpenLMIS be the source of truth for cce or would a monitoring system like NexLeaf?

Would OpenLMIS be the source of truth for cce or would a monitoring system like NexLeaf?

Is bearer tokens the only method that we want to support?

Is bearer tokens the only method that we want to support?

Also, if you add something about smart endpoints/dump pipes, including some detail about what that means in practice would be helpful as well.

Also, if you add something about smart endpoints/dump pipes, including some detail about what that means in practice would be helpful as well.

Updated Test Coverage

Added details of testing, bugs, and bug triage link to Test Coverage.

    • -3
    • +1
    ./releases/openlmis-ref-distro-v3.6.0.rst
Completed the majority of the 3.6 release notes.

    • binary
    ./releases/UI-Performance-3.6.png
    • -48
    • +28
    ./releases/openlmis-ref-distro-v3.6.0.rst
I would prefer to lowercase device, so it doesn't get confused with FHIR's Device.

I would prefer to lowercase device, so it doesn't get confused with FHIR's Device.

a part

a part

comes from

comes from

Datetimes

Datetimes

Would you be able to add something in here about smart endpoints and dumb pipes? I think it would be helpful.

Would you be able to add something in here about smart endpoints and dumb pipes? I think it would be helpful.

OLMIS-5584, change toc depth to 2
OLMIS-5584, change toc depth to 2
OLMIS-5584, change toc depth to 2

OLMIS-5584, add interop doc section.

    • -0
    • +180
    ./architecture/interop.md
Added in-progress v3.6 release notes.

    • -0
    • +263
    ./releases/openlmis-ref-distro-v3.6.0.rst
fix link

I'm bad at rst