On Thu, 11 Mar 2010, Paul Wouters wrote: > > That might be harsh for some soname updates. Six months is a long time > to wait on new functionality after upstream released it. Even for users > running only full Fedora releases. Though I see various phrasing around > this that would allow exceptions, which is good. > > Example: SHA256 support added to bind 9.6.2 less then a week ago (from > 9.6.1). Bind 9.6.x is in F-12, and arpa. will be signed with SHA256 in > 4 days. This leaves quite the window until F-13 is released (where users > are on bind-9.7.x that contains SHA25 already). In this case, F-12 should > really upgrade from 9.6.1 to 9.6.2. And it will be impossible for users running the non-sha256 bind to communicate with the sha256 supporting arpa? I guess I don't understand what do the users of the existing bind LOSE? Is ARPA expecting everyone to upgrade to a sha256 supporting bind immediately? There's no migration window? -sv -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
