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

Update check_packages to flag required package versions (Trac #565) #697

Closed
smk78 opened this issue Mar 30, 2019 · 5 comments · Fixed by #1482 or #1487
Closed

Update check_packages to flag required package versions (Trac #565) #697

smk78 opened this issue Mar 30, 2019 · 5 comments · Fixed by #1482 or #1487
Assignees
Labels
Critical High priority Enhancement Feature requests and/or general improvements Infrastructure GitHub, project structure, community etc

Comments

@smk78
Copy link
Contributor

smk78 commented Mar 30, 2019

check_packages could be made to flag when the installed packages (eg, bumps) do not meet the minimum version number necessary for a successful build.

Migrated from http://trac.sasview.org/ticket/565

{
    "status": "accepted",
    "changetime": "2019-03-23T14:18:31",
    "_ts": "2019-03-23 14:18:31.048786+00:00",
    "description": "check_packages could be made to flag when the installed packages (eg, bumps) do not meet the minimum version number necessary for a successful build.",
    "reporter": "smk78",
    "cc": "",
    "resolution": "",
    "workpackage": "Support Infrastructure",
    "time": "2016-04-26T15:24:42",
    "component": "SasView",
    "summary": "Update check_packages to flag required package versions",
    "priority": "critical",
    "keywords": "",
    "milestone": "Admin Tasks",
    "owner": "tim",
    "type": "enhancement"
}
@smk78 smk78 added this to the Admin Tasks milestone Mar 30, 2019
@smk78 smk78 added Critical High priority Enhancement Feature requests and/or general improvements Incomplete Migration and removed Incomplete Migration labels Mar 30, 2019
@ajj
Copy link
Member

ajj commented Mar 30, 2019

Trac update at 2016/08/16 13:47:20: ajj changed milestone from "SasView 4.0.0" to "SasView Next Release +1"

@sasview-bot
Copy link

Trac update at 2017/10/25 16:04:23:

  • tim changed owner from "" to "tim"
  • tim changed status from "new" to "accepted"

@butlerpd
Copy link
Member

Trac update at 2019/02/26 14:30:58:

  • butler changed milestone from "SasView Next Release +1" to "Admin Tasks"
  • butler changed workpackage from "SasView Admin" to "Support Infrastructure"

@butlerpd
Copy link
Member

Trac update at 2019/03/23 14:18:31: butler changed priority from "major" to "critical"

@krzywon krzywon added the Slicers Concerns slicer functionality label Mar 18, 2020
@krzywon krzywon self-assigned this Mar 18, 2020
@krzywon krzywon added Infrastructure GitHub, project structure, community etc and removed Slicers Concerns slicer functionality labels Mar 18, 2020
@timsnow
Copy link
Contributor

timsnow commented Mar 19, 2020

So, whilst the idea being floated yesterday is a good one, how do we think we can go about picking the right YAML file to interrogate?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Critical High priority Enhancement Feature requests and/or general improvements Infrastructure GitHub, project structure, community etc
Projects
None yet
6 participants