versioningReleasing.md

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
OLMIS-4801: Added information about keeping release builds forever

Agree, we just need some info in contribution guide or smth to inform about auto saving release builds

Agree, we just need some info in contribution guide or smth to inform about auto saving release builds

let's also add the SNAPSHOT check

let's also add the SNAPSHOT check

Why not have both checks? We shouldn't be releasing on branches other than master or rel-. It also does not make sense to keep a failed build, I think it's better to keep it in push image stage

Why not have both checks? We shouldn't be releasing on branches other than master or rel-. It also does not make sense to keep a failed build, I think it's better to keep it in push image stage

if files were added after 3.3 we don't need extra changelog entries

if files were added after 3.3 we don't need extra changelog entries

I'm not sure about that change, what if we are going to public docker image on every successful build on master? I believe that check for SNAPSHOT is enough, what if we are going to release from ma...

I'm not sure about that change, what if we are going to public docker image on every successful build on master? I believe that check for SNAPSHOT is enough, what if we are going to release from master branch? It is just saving a build so if we are going to support saving it from branches other than release once I think it is OK.

You are right, moved.

You are right, moved.

The Jenkinsfiles were just added in this release and we didn't include any other updates in the changelog. What do you think Mateusz Kwiatkowski Łukasz Lewczyński?

The Jenkinsfiles were just added in this release and we didn't include any other updates in the changelog. What do you think Mateusz Kwiatkowski Łukasz Lewczyński?

We should also check if it's a release branch. Maybe it would be enough move the code to 'Push image' stage?

We should also check if it's a release branch. Maybe it would be enough move the code to 'Push image' stage?

Jakub Kondrat Do we need changelog or update in the contribution documentation?

Jakub Kondrat Do we need changelog or update in the contribution documentation?

OLMIS-4801: Updated Jenkinsfile to set keepLog flag as true when releasing
OLMIS-4801: Updated Jenkinsfile to set keepLog flag as true when releasing
LGTM

LGTM

OLMIS-4840, fix UI doc links
OLMIS-4840, fix UI doc links
OLMIS-4840, fix broken service api and erd doc links

Caused by moving build jobs to newly named pipeline jobs.

  1. … 8 more files in changeset.
Maybe we shouldn't create a release branch for each single patch release, but for a series of patch releases? That means a patch 10.0.1, 10.0.2, 10.0.3 would all be supplied from branch 10.0.x The ...

Maybe we shouldn't create a release branch for each single patch release, but for a series of patch releases?
That means a patch 10.0.1, 10.0.2, 10.0.3 would all be supplied from branch 10.0.x
The reason I'm thinking about this is to avoid overlooking some changes. Eg. creating a branch for release 10.0.3 from master's 10.0.0 and not including patches for 0.1 and 0.2.
Just an idea to think about and consider.

I couldn't find anything that needs to be updated in Contribution guide. Did I miss something?

I couldn't find anything that needs to be updated in Contribution guide. Did I miss something?

OLMIS-4514: Update Doc with Patch Release Process
OLMIS-4514: Update Doc with Patch Release Process
OLMIS-4514: Update Doc with Patch Release Process

Update the release documentation to be more accurate

Some information is old.

Revert "Release of OpenLMIS Ref Distro v3.3"

This reverts commit 0a963ec3dbe8c227e0827f0ad8c721dc28523366.

  1. … 12 more files in changeset.
Release of OpenLMIS Ref Distro v3.3

* Update releasing instructions

Update to remove entry about updating openlmis-config, since that repo is now legacy.

* Update component versions in ref-distro

For 3.3.0 release.

* Update documentation to specific versions

For 3.3 release.

* Update ERD and API doc links

Update to build numbers instead of last successful build. Remove live versions of ERD and APIs (since they are not versioned).

  1. … 12 more files in changeset.
Update releasing instructions

Update to remove entry about updating openlmis-config, since that repo is now legacy.