1.11 RCs and remaining 1.10 issues

Today we released Foreman 1.11.0-RC1, so the process of 1.11 is now
fully underway. Thanks to people for their help with the build-blocking
issues I had between branching and RC1, they were all fixed in only one
week.

Over the next few weeks we can expect the tickets to pile up, and it's
important that we try and address them quickly for the following release
candidate. Each RC will be around two weeks after the last, so RC2 is
due around Weds 10th March.

To start us off, here are the current 1.11 and 1.10 regression lists.
Check the issue query URLs for the latest.

1.10 tickets

http://projects.theforeman.org/projects/foreman/issues?query_id=87

  1. foreman-debug SCL name is incorrect
    Bug #13803: Foreman-debug does not report SCL correctly - Foreman

  2. Host update API can't change unwrapped hostgroup_id
    Bug #13775: Not able to change an HG for a host using API call - Foreman

  3. "stack level too deep" during LDAP AD auth
    Bug #13608: LDAP Authentication failure: stack level too deep - Foreman

  4. undefined method persisted? during CR form rendering
    Bug #13053: undefined method `persisted?' for #<Hash:0x007f2481f21258> - Foreman

  5. VMware provisioning from template not using new disk
    Bug #12487: Provisioning with Templates causes new VM to use Template Disk - Foreman

1.11 tickets

http://projects.theforeman.org/projects/foreman/issues?query_id=81

  1. Dashboard widgets loading in the wrong order
    Bug #13352: Dashboard widget rows are loaded in reverse order - Foreman

  2. jQuery upgrade tasks
    Refactor #12935: Check js code against jQuery upgrade guide and release notes - Foreman

Thanks all.

··· -- Dominic Cleal dominic@cleal.org

I forgot to link to the schedule:

http://projects.theforeman.org/projects/foreman/wiki/Foreman_111_Schedule

I'll update this page if any build-blocking issues come up or if the
dates shift significantly.

··· On 25/02/16 12:27, Dominic Cleal wrote: > Today we released Foreman 1.11.0-RC1, so the process of 1.11 is now > fully underway. Thanks to people for their help with the build-blocking > issues I had between branching and RC1, they were all fixed in only one > week. > > Over the next few weeks we can expect the tickets to pile up, and it's > important that we try and address them quickly for the following release > candidate. Each RC will be around two weeks after the last, so RC2 is > due around Weds 10th March.


Dominic Cleal
dominic@cleal.org