Yes, I think tagging with a date is a good idea, as I can see once a RC is created the tag fails in subsequent RC. I am not sure about the procedure to change this tag naming convention but +1 for this from me.
On 11/12/13 4:20 pm, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote: >On a side note: Can we set a tag of "RC-<date>" on creating release >candidates? this in combination with a branch will be helpful in >chasing changes like I just did. > >Or should I start a new [DISCUSS] thread on this? >Or just change the wiki and burden the release managers with it >without telling? (no seriousness intended) > >thanks, >Daan > >On Wed, Dec 11, 2013 at 11:47 AM, Daan Hoogland <daan.hoogl...@gmail.com> >wrote: >> I can confirm that the folowing fixes the problem >> >> [root@mccdxen1 bin]# pwd >> /opt/cloud/bin >> [root@mccdxen1 bin]# ln -s /opt/xensource/bin/vhd-util . >> >> I don't think we should let this to the people doing a migration from >> one version to another so >> >> -1 (binding) to this rc >> >> I want to set this link in code (on addHost??) so again you will hear >> more on this from me >> >> regards, >> Daan >> >> On Wed, Dec 11, 2013 at 10:38 AM, Daan Hoogland >><daan.hoogl...@gmail.com> wrote: >>> On Wed, Dec 11, 2013 at 5:24 AM, David Nalley <da...@gnsa.us> wrote: >>>> Why, for a bug fix release would we do something like change the >>>> expected location of vhd-util on a XS host? >>> >>> Or more specifically; What bug does this fix? >>> >>> And why is it not copied to the hypervisors as part of the zone >>> configuration/addHost procudure?
