[bind10-dev] bind10 release status and rebranch (rc this week)

[Jeremy C. Reed]

There have been many fixes since the beta from a couple weeks ago, but 
mostly all for the experimental DHCP code. The revised schedule is 
currently to do a release candidate on March 27 and then the final on 
April 3.

We have many fixes and improvements that we could consider 
providing through another beta stage (but as for now I will do a rc 
instead).
http://git.bind10.isc.org/cgi-bin/cgit.cgi/bind10/log/?h=master

In addition, some of the BIND10 Kea DHCP code has some expected 
improvements happening within next two weeks.  Per past "release 
candidate" policy, we don't add new code between a release candidate and 
final release and would normally do an additional release candidate 
(like rc2).  We want to coordinate the release of these DHCP 
improvements (such as Trac #3080) for their deliverable date.

I'd like to continue as scheduled. The only non-DHCP-related code since 
the beta is the revert of entry 760 (Trac #3339) which I think is okay. 
Can someone confirm that no other non-DHCP code is expected prior to the 
release?

Since the DHCP code is standalone and documented as "experimental" and 
considered "alpha" it may be fine to ship this new code even after a 
beta or release candidate as part of the larger BIND10 release. If 
anyone has a strong argument about diverging from the our release 
candidate to final policy in the relation to this, please let me know.

Please let me know if you expect any DNS or non-DHCP specific commits to 
be included in the upcoming release.

I plan to rebranch instead of cherry-picking all the new DHCP fixes and 
the revert of beta entry 760 (Trac #3339). I plan to do this my 
Wednesday morning.

After this rc1, if all goes well, I'd like the Kea developers to let me 
know what upcoming commits to cherry-pick into the release branch by the 
end of April 1 for next week's release.

  Jeremy C. Reed
  ISC