Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: Metsrw version needs to be bumped to 0.2.3 prior to release #208

Closed
jrwdunham opened this issue Sep 25, 2018 · 4 comments
Closed
Labels
OCUL: AM-Dataverse OCUL: AM-Dataverse
Milestone

Comments

@jrwdunham
Copy link


For Artefactual use:
Please make sure these steps are taken before moving this issue from Review to Verified in Waffle:

  • All PRs related to this issue are properly linked 馃憤
  • All PRs related to this issue have been merged 馃憤
  • Test plan for this issue has been implemented and passed 馃憤
  • Release documentation (e.g. release notes, wiki documentation, etc) regarding this issue has been written 馃憤
@jrwdunham jrwdunham self-assigned this Sep 25, 2018
@jrwdunham jrwdunham added the OCUL: AM-Dataverse OCUL: AM-Dataverse label Sep 25, 2018
@jrwdunham jrwdunham added Status: refining The issue needs additional details to ensure that requirements are clear. Status: ready The issue is sufficiently described/scoped to be picked up by a developer. Status: in progress Issue that is currently being worked on. and removed Status: refining The issue needs additional details to ensure that requirements are clear. Status: ready The issue is sufficiently described/scoped to be picked up by a developer. labels Sep 25, 2018
@sevein sevein added Status: review The issue's code has been merged and is ready for testing/review. and removed Status: in progress Issue that is currently being worked on. labels Sep 26, 2018
@sromkey sromkey added this to the 1.8.0 milestone Sep 26, 2018
@ablwr
Copy link
Contributor

ablwr commented Oct 3, 2018

This needs to be bumped in Archivematica dependencies as well. So should this be moved back to "in progress"? I don't see a separate issue for doing that.

@ross-spencer
Copy link
Contributor

@ablwr
Copy link
Contributor

ablwr commented Oct 3, 2018

Oh it's a dependency is the dashboard too, should it change there? https://github.com/artefactual/archivematica/blob/stable/1.7.x/src/dashboard/src/requirements/base.txt#L20

@ross-spencer
Copy link
Contributor

@ablwr In short, it could be, but I'm not sure it needs to be bumped at present. Entirely a preference based decision I think.

The update was for a Microservice in the MCP Client so testing can remain focused on that. The Dashboard could be bumped if there were a perceived benefit.

@ablwr ablwr added Status: verified and removed Status: review The issue's code has been merged and is ready for testing/review. labels Oct 4, 2018
@sromkey sromkey closed this as completed Nov 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCUL: AM-Dataverse OCUL: AM-Dataverse
Projects
None yet
Development

No branches or pull requests

5 participants