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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable nightly standalone packages to install mslice nightly versions #38674

Draft
wants to merge 1 commit into
base: release-next
Choose a base branch
from

Conversation

thomashampson
Copy link
Contributor

@thomashampson thomashampson commented Jan 22, 2025

Description of work

Summary of work

Fixes #38628

Further detail of work

To test:

On each OS:

  1. Download and install the standalone package from this build
  2. Open the application
  3. Enter the following in the Python console, it should return '2.10.1.dev25+uncommitted':
import mslice
mslice.__version

This does not require release notes because this is attempting to reproduce the old behaviour when we used the SHA to keep mslice up to date


Reviewer

Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.

Code Review

  • Is the code of an acceptable quality?
  • Does the code conform to the coding standards?
  • Are the unit tests small and test the class in isolation?
  • If there is GUI work does it follow the GUI standards?
  • If there are changes in the release notes then do they describe the changes appropriately?
  • Do the release notes conform to the release notes guide?

Functional Tests

  • Do changes function as described? Add comments below that describe the tests performed?
  • Do the changes handle unexpected situations, e.g. bad input?
  • Has the relevant (user and developer) documentation been added/updated?

Does everything look good? Mark the review as Approve. A member of @mantidproject/gatekeepers will take care of it.

Gatekeeper

If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.

@thomashampson thomashampson added the Bug Issues and pull requests that are regressions or would be considered a bug by users (e.g. crashing) label Jan 22, 2025
@sf1919 sf1919 added this to the Release 6.12 milestone Jan 23, 2025
@thomashampson thomashampson force-pushed the 38628_fix_mslice_nightly_version_bug branch from 69791f1 to 35b79cf Compare January 23, 2025 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues and pull requests that are regressions or would be considered a bug by users (e.g. crashing)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ensure released Mantid version uses a specific released MSlice version
2 participants