Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Ensure service util library will bump to stable in OSSRH

Description

In releasing the first stable release of v3, it's components should also be more stable than not. This includes the service utility library that many services consume via Maven from OSSRH.

We are currently publishing this library as a SNAPSHOT, which ends up in the snapshot repo of OSSRH. When we release 3.0, we'll be releasing this library as a stable version, and therefore it'll change repo locations.

Acceptance:

  • check that when we change away from SNAPSHOT, that the library will be published to the stable repo (i.e. answer how this works)

  • plan the stable release of the library

  • as part of the 3.0 release, the service will need to start consuming the stable version, update those services (this might be more a doc step in the rolling a release page and also asking community if we're ready to release the shared library before the big release)

Attachments

3

Confluence content

mentioned on

QAlity Plus - Test Management

Checklists

Activity

Josh Zamor 
February 28, 2017 at 1:50 AM

I'm going to move this to done. The release is in maven central and I tested by bumping reference data to use that stable release already: https://github.com/OpenLMIS/openlmis-referencedata/commit/3b37ee06d254e60cf1e3ba3680bfb72ec74d4f1d

All seems to be well and we'll bump the rest of the services as part of the release process as the rolling a release wiki calls for.

Thanks

Brandon Bowersox-Johnson 
February 28, 2017 at 12:25 AM
(edited)

Okay, this looks good so far. The one piece that does not seem to be done is the last Acceptance Criteria: "...update other services to start consuming the stable version...." That said, I see that is documented in 2.f. of the Release Wiki. So it's probably fine to Close this ticket, and we will update the other services during the release process on Wednesday.

UPDATE: Josh, I'm assigning this back to you. If you want to do any more of the follow-up (or checking if Maven Central has published it), that's cool, otherwise you can move this ticket along and we'll of course need to make sure it's all set as part of rolling the release.

Brandon Bowersox-Johnson 
February 27, 2017 at 11:59 PM

Josh Zamor 
February 27, 2017 at 11:55 PM

Moving to review. We're still waiting for Maven central propagation to complete. When it does it should show up here: https://search.maven.org/#search%7Cga%7C1%7Corg.openlmis

I think we may move this ticket through before propagation completes.

Josh Zamor 
February 27, 2017 at 11:50 PM

: thanks. I ended up taking your advise and creating a new version.

Done:

  • new key generated, uploaded to Jenkins and an S3 bucket was created to store it for future reference

  • public key published to keystore

  • project url, scm url, developer info added to artifact uploaded

  • 3.0.0 of library released to maven central

  • tips and tricks for maven wiki page published: https://openlmis.atlassian.net/wiki/x/ZK6nBg

  • rolling a release page updated

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Sprint

Fix versions

Priority

Time Assistant

Created February 16, 2017 at 5:14 AM
Updated February 28, 2017 at 1:50 AM
Resolved February 28, 2017 at 1:50 AM