It's never too late. Are you saying that MFCing this change would add 6000 packages that would otherwise not build? If that is so, we can cherry-pick, tag 3.6.1, and that is what we release. Extra packages are more beneficial than a version number ending in 0. On Nov 20, 2013 4:03 AM, "John Marino" <[email protected]> wrote:
> On 11/19/2013 06:08, Justin Sherrill wrote: > > It's been two weeks, and dports packages are built (thanks marino) and > > release notes are mostly done (thanks ftigeot) and there's no nasty bugs > > waiting that I know of, or MFCs pending... I'm not used to it being so > > quiet. > > > > Tomorrow night I'll tag 3.6.0 and start building the iso/img files. > > There's no GUI images right now because of the dports switch, but > > that's not worth holding up the release. > > Hi Justin, > I just found out this commit: > > http://gitweb.dragonflybsd.org/dragonfly.git/commit/a8e6840433fdc0aad2b0b8b58429ed1f29f848dd > > was not MFC'd. That was unfortunate. It actually caused 6000+ dports > breakage on Release 3.6 after libcheck was adjusted for master. Too > late now, I guess. > > John >
