Re: 11.0-RELEASE Status Update

[Johan Hendriks]

Op 06/10/2016 om 22:18 schreef Glen Barber:
> As many of you are aware, 11.0-RELEASE needed to be rebuilt to address
> several issues that were discovered after the release was built. Extra
> caution is being taken in testing the rebuilt releases, so at present,
> the final release announcement is planned for Monday, October 10.
>
> Thank you for your patience in waiting for 11.0-RELEASE.
>
> Glen
> On behalf of: re@
>
Is the aws bug included in the final build? It would be nice if it is
included and not being an Eratta. I think a lot of people are going to
update there servers, and then read the announcement.
Just like they install the RELEASE even if there is no official release
post about the release.

regards,
Johan
_______________________________________________
freebsd...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"

[Alexander Shitov]

Op 06/10/2016 om 22:18 schreef Glen Barber:
> As many of you are aware, 11.0-RELEASE needed to be rebuilt to address
> several issues that were discovered after the release was built. Extra
> caution is being taken in testing the rebuilt releases, so at present,
> the final release announcement is planned for Monday, October 10.
>
> Thank you for your patience in waiting for 11.0-RELEASE.
>
> Glen > On behalf of: re@ >

Is fix for Hyper-V bug "virtual disk being detached from the bus"
(https://reviews.freebsd.org/D7693) included in final build?
PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212721

It will be big disappointment if 11.0-RELEASE will became incompatible
with Hyper-V.

---
Best Regards,
Alexander

[Cassiano Peixoto]

Looks we have some import issues to be fixed before 11-RELEASE. I have
another one that nobody cares:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257
and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212413

It's affecting ALTQ users on both FreeBSD 11 and 10.3, the system just
crash.

IMHO would be better to release a stable product instead of keep the
schedule.

[jungle Boogie]

On 6 October 2016 at 13:18, Glen Barber <g...@freebsd.org> wrote:
> the final release announcement is planned for Monday, October 10.

suggestion:
update the schedule
https://www.freebsd.org/releases/11.0R/schedule.html



--
-------
inum: 883510009027723
sip: jungle...@sip2sip.info

[Bruce A. Mah]

If memory serves me right, Cassiano Peixoto wrote:
> Looks we have some import issues to be fixed before 11-RELEASE. I have
> another one that nobody cares:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257
> and
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212413
>
> It's affecting ALTQ users on both FreeBSD 11 and 10.3, the system just
> crash.
>
> IMHO would be better to release a stable product instead of keep the
> schedule.

There's always "just one more bug". If the FreeBSD Project waited until
the code was bug-free there'd be no releases at all.

It's the Release Engineering team's job to make the call on which bugs
are worth holding up a release for and which aren't, when workarounds
are acceptable and when they need to try to pursuade a developer to
diagnose and implement a real fix, etc. They need to use their
judgement about a number of factors such as severity, number of users
impacted, availability of developers, and so on. The schedule is also a
factor, but it's never just for the sake of adhering to the schedule.

Bruce
(Ex-RE team member)

[Marcelo Gondim]

Em 06/10/2016 17:18, Glen Barber escreveu:
> As many of you are aware, 11.0-RELEASE needed to be rebuilt to address
> several issues that were discovered after the release was built. Extra
> caution is being taken in testing the rebuilt releases, so at present,
> the final release announcement is planned for Monday, October 10.
>
> Thank you for your patience in waiting for 11.0-RELEASE.
>
> Glen
> On behalf of: re@
>

Great job Glen. The important to a sysadmin is an increasingly stable
system. When he is ready, it will be ready.

Thanks! :)