Opened 10 years ago
Last modified 6 years ago
#322 new defect
Need to streamline requiring new version of packages
Reported by: | butler | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | SasView 4.3.0 |
Component: | SasView | Keywords: | |
Cc: | Work Package: | SasView Framework Enhancements |
Description
Currently requiring a new version of, for example bumps, requires changes be made in five separate places: build_tools/* (mac builder, RPM builder and windows builder), setup.py and check_packages.py
Change History (5)
comment:1 Changed 10 years ago by butler
comment:2 Changed 10 years ago by butler
- Milestone changed from SasView 3.1 to SasView Next Release +1
Not required for release and not likely to get done before release — moving from 3.1 to release +1
comment:3 Changed 9 years ago by butler
- Milestone changed from SasView Next Release +1 to SasView 4.0.0
comment:4 Changed 9 years ago by butler
- Milestone changed from SasView 4.0.0 to SasView Next Release +1
comment:5 Changed 6 years ago by butler
- Milestone changed from SasView Next Release +1 to SasView 4.3.0
Is this fixed by the yml files?
Note: See
TracTickets for help on using
tickets.
want a configuration file that specifies all the version dependencies in one place to be used by the build systems.