Why is this Self-Contained Change and not a System Wide Change? It seems, at least to me, that it should be System Wide Change, according to https://fedoraproject.org/wiki/Changes/Policy#Complex_system_wide_changes .
On Fri, Jan 25, 2019 at 3:45 PM Ben Cotton <bcot...@redhat.com> wrote: > https://fedoraproject.org/wiki/Changes/Bash_5.0 > > == Summary == > > Upgrade bash to 5.0 release. This release fixes several outstanding > bugs in bash-4.4 and introduces several > new features. The most significant bug fixes are an overhaul of how > nameref variables resolve and a number of potential out-of-bounds memory > errors discovered via fuzzing. > > == Owner == > * Name: [[User:svashisht| Siteshwar Vashisht]] > > * Email: svashi...@redhat.com > * Release notes owner: > > == Detailed Description == > > There are a number of changes to the > expansion of $@ and $* in various contexts where word splitting is not > performed to conform to a Posix standard interpretation, and additional > changes to resolve corner cases for Posix conformance. > > The most notable new features are several new shell variables: BASH_ARGV0, > EPOCHSECONDS, and EPOCHREALTIME. The `history` builtin can remove ranges of > history entries and understands negative arguments as offsets from the end > of the history list. There is an option to allow local variables to inherit > the value of a variable with the same name at a preceding scope. There is > a new shell option that, when enabled, causes the shell to attempt to > expand associative array subscripts only once (this is an issue when they > are used in arithmetic expressions). The `globasciiranges' shell option > is now enabled by default; it can be set to off by default at configuration > time. > > There are a few incompatible changes between bash-4.4 and bash-5.0. The > changes to how nameref variables are resolved means that some uses of > namerefs will behave differently, though upstream has tried to minimize the > compatibility issues. > > == Benefit to Fedora == > > Bash is the default shell in Fedora and it will benefit from new > features and performance improvements of the latest release. > > == Scope == > * Proposal owners: Upgrade bash to 5.0 > * Other developers: N/A (not a System Wide Change) > * Release engineering: [https://pagure.io/releng/issues #Releng issue > number] (a check of an impact with Release Engineering is needed) > ** List of deliverables]: N/A (not a System Wide Change) > * Policies and guidelines: N/A (not a System Wide Change) > * Trademark approval: N/A (not needed for this Change) > > == Upgrade/compatibility impact == > Code related to resolving namerefs was changed, so some scripts may > break. But impact should be minimum as this release is largely > backward compatible. > > == Dependencies == > N/A (not a System Wide Change) > > > > == Documentation == > N/A (not a System Wide Change) > > == Release Notes == > https://lists.gnu.org/archive/html/bug-bash/2019-01/msg00063.html > > > > -- > Ben Cotton > Fedora Program Manager > TZ=America/Indiana/Indianapolis > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Best regards / S pozdravem, FrantiĊĦek Zatloukal Quality Engineer Red Hat
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
