User story #1906
closed
Added by Matthieu CERDA about 13 years ago.
Updated about 6 years ago.
Description
We should create a PT update script, following these three incremental updates :
- A first brutal version, which replaces the overwrites the whole existing library with the new PTs
- A second version which does the same thing but for each PT independantly
- A final version which takes advantage of facilities like debconf to have a consistent and simple user experience
- Target version changed from 18 to 2.4.0~alpha1
- Priority changed from 3 to 2
- Target version changed from 2.4.0~alpha1 to 2.4.0~alpha2
- Target version changed from 2.4.0~alpha2 to 2.4.0~alpha3
- Target version changed from 2.4.0~alpha3 to 2.4.0~alpha4
- Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5
- Target version changed from 2.4.0~alpha5 to 2.4.0~alpha6
- Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7
- Target version changed from 2.4.0~alpha7 to 2.4.0~beta1
I think this task will be too long to be included in 2.4.0~alpha7.
And why this task hasn't be assigned to ?
- Target version changed from 2.4.0~beta1 to Ideas (not version specific)
- Project changed from Rudder to 34
- Category deleted (
11)
- Project changed from 34 to Rudder
- Category set to Packaging
- Subject changed from PT update script to Technique update script
- Status changed from New to Rejected
Done as part of rudder agent in #13408.
- Related to User story #13408: Automatically upgrade techniques when we upgrade Rudder added
Also available in: Atom
PDF
Updated by Matthieu CERDA 
Updated by 
Updated by Jonathan CLARKE 
Updated by Nicolas PERRON 
Updated by 
Updated by