On Tue, Jun 24, 2014 at 4:34 AM, Jaroslav Reznik <jreznik@xxxxxxxxxx> wrote:
Greetings!
Fedora 21 Changes Freeze is currently scheduled to no earlier than
2014-07-08 [1] and we're getting closer to this date. Btw this is
also Fedora 21 Branch from Rawhide date.
At this point, all accepted changes should be substantially complete,
and testable. Additionally, if a change is to be enabled by default,
it must be so enabled at Change Freeze.
Change tracking bug should be set to the MODIFIED state to indicate
it achieved completeness. [2]
As Fedora 21 scope is really huge, progress at Changes Freeze
will help us to think about where we are and what we can do for
this release. This applies not only to change owners but to all
other groups - especially from WGs and teams involved in Fedora
re-design. Let us know if you're blocked, if you need any help
etc. or just to say, hey, we're ready :).
Jaroslav
[1] https://fedoraproject.org/wiki/Releases/21/Schedule
[2] http://bit.ly/f21changesfreeze
_______________________________________________
devel-announce mailing list
devel-announce@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
I'm not very familiar with the Fedora release schedule and how closely related it is with gcc, but in the odb package that I'm the maintainer for there appears to be a bug with the devirtualization that is claimed to be on the roadmap for a fix in 4.9.1 ( http://www.codesynthesis.com/pipermail/odb-users/2014-May/001851.html ). I currently have a workaround in odb that just disables the devirtualization ( http://pkgs.fedoraproject.org/cgit/odb.git/commit/?id=5549f93543ed60a7d2027d0eb932c8cf6737edb5 ), so should I just leave it that way and then remove that when 4.9.1 is finally released for F21 or what's the right way to handle that?
Thanks,
Dave
Thanks,
Dave
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
