On 23/06/16 17:41, Thomas Cheng wrote: > Thanks for Confirmation. In my version (latest stable 1.11.3) seems this > problem exists. > I looked at the issue your mentioned here > http://projects.theforeman.org/issues/14954, > it was last updated one month ago, and 1.11.3 was built on Jun 21, 2016 > ( two days ago), > so can I assume that a sub-minor release, say, 1.11.4/5/6 recently may > have a plan to patch it? > > a backport patch, if possible, will be great if no recent plan to merge > into master branch.
There isn't a patch to fix it yet, so I can't really comment. If it's fixed then it will probably go into a subsequent patch release too, which is more likely to be 1.12 than 1.11 currently. -- Dominic Cleal [email protected] -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
