Feature #5683
closed
- Status changed from New to Ready For Testing
- Assignee set to Ben Hagen
- Target version set to 1.8.3
To summarize the discussion so far on the PR:
2) I think it would be safe to use the -updates version per default. But we would need to check > if there really is one for this release.
When it comes to customizing, I would want to specify the whole path or maybe even the url. For > example to use the Saucy HWE images from /ubuntu/dists/precise-updates/main/installer-i386/current/images/saucy-netboot/ to support newer hardware in Precise.
I agree. I think we want to enable specifying this kind of data on the Medium, or possibly even on the OS model. Do you want to have a go at this (we can assist if you drop into IRC), or would prefer to leave it to someone else?
- Target version changed from 1.8.3 to 1.8.2
- Target version changed from 1.8.2 to 1.8.1
- Target version changed from 1.8.1 to 1.8.0
- Target version changed from 1.8.0 to 1.7.5
- Target version changed from 1.7.5 to 1.7.4
- Target version changed from 1.7.4 to 1.7.3
I'm a +1 for the suggested changes in the PR. I'll take a look at implementing.
- Target version changed from 1.7.3 to 1.7.2
- Pull request https://github.com/theforeman/foreman/pull/1434 added
- Pull request deleted (
- Status changed from Ready For Testing to Rejected
- translation missing: en.field_release_relationship changed from auto to added
Closing as won't fix for the reasons specified in the PR, this can be done by changing the release name to precise-updates, saucy-updates, etc... on the Operating System.
Users can create an specific OS for precise and precise-updates and have the updated images without any patch.
Spam deleted by administrator.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous 
Updated by 
Updated by 
Updated by