You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FrameworkIssues and pull requests related to components in the FrameworkStaleThis label is automatically applied to issues that are automatically closed by the stale bot
I am writing this ticket straggling again to remember and identify an algorithm appropriate for creating a testing workspace.
I think, creating a category of Testing algorithm and gathering these algorithms together in Mantid documentation for further references would greatly simplify such job in a future.
The text was updated successfully, but these errors were encountered:
@abuts (2014-11-13T13:41:31):
Though I thought the commit above will fix it, I've find out how it all was implemented in Mantid realized that a classification can be a most debated topic which nobody would agree.
Leaving for the assigner to decide if this ticket is feasible& reasonable.
@NickDraper (2014-12-08T10:25:38):
Moved to the backlog at the code freeze of R3.3
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.
To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.
stalebot
added
the
Stale
This label is automatically applied to issues that are automatically closed by the stale bot
label
Feb 24, 2021
FrameworkIssues and pull requests related to components in the FrameworkStaleThis label is automatically applied to issues that are automatically closed by the stale bot
This issue was originally TRAC 10551
I am writing this ticket straggling again to remember and identify an algorithm appropriate for creating a testing workspace.
I think, creating a category of Testing algorithm and gathering these algorithms together in Mantid documentation for further references would greatly simplify such job in a future.
The text was updated successfully, but these errors were encountered: