Describe the issue Please set EOL dates in to "2018-12-01" for the following branch SLAs in PDC:
branch SLA ID 739258, SLA name "rawhide", branch ID 370671, branch name "1.10", global component "ant", branch type "module", new EOL date "2018-12-01"
branch SLA ID 739214, SLA name "rawhide", branch ID 370645, branch name "3.5", global component "maven", branch type "module", new EOL date "2018-12-01"
branch SLA ID 739215, SLA name "rawhide", branch ID 370646, branch name "201801", global component "javapackages-tools", branch type "module", new EOL date "2018-12-01"
branch SLA ID 741257, SLA name "rawhide", branch ID 371899, branch name "2.10", global component "scala", branch type "module", new EOL date "2018-12-01"
When do you need this? (YYYY/MM/DD) Earliest convenience.
When is this no longer needed or useful? (YYYY/MM/DD) N/A
If we cannot complete your request, what is the impact? Branches will still be marked as inactive in PDC. As a consequence packagers may be unable to push to these branches. Additionally, after EOL enforcement is re-enabled, module builds from these branches may no longer be working.
Please let me know if you prefer branch SLAs listed in a different form, as I will be opening a new ticket with more (~200) SLAs to be updated soon.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
This is done and I created the script to adjust eol of modules and branches to a given date.