More Frequent Delivery process

As previously discussed an implication of moving to more frequent Delivery is multiple effectiveTimes in each release - is this an issue? (TIG allows for it already, but we’ve never done it before)
Liam to confirm if he got a response from his team.

Previous Notes:

Mikael Nyström asked if we would move to multiple releases per day (as if so the Date field would need to become a DateTime field) - Andrew Atkinson confirmed that this was extremely unlikely (even in the long term), as the current plan is a phased approach, starting at monthly releases and working down through weekly to daily releases in the long run. The efficiency gains are outweighed by the overheads once you move to multiple releases per day, and so this is unlikely to ever be a realistic option.
Corey Smith asked if the 6 monthly releases would stay on January 31st and July 31st - Andrew Atkinson confirmed that they would for the foreseeable future, but that we will ensure that the Release versioning will be flexible enough to cope if we were to move the dates at some point in the future... (so the version would link to whatever date range existed between the new 6 monthly release dates, allowing people to effectively trace back the changes between the 6 monthly releases)
Eric Robertson confirmed that he could see no issues with multiple effective times, but will ask his vendors.

Previous actions:
Liam Coughlan to talk to a broader audience on 23rd Feb 2016 - will feedback then.
Eric Robertson to talk to vendors and confirm no issues with multiple effective times.