Please stabilize app-shells/bash-4.0_p17-r1.
why ?
It has many new, useful features. It has been in the tree for over 30 days.
if you have no real pressing need, then it should sit in unstable for a bit longer. you could install bash-4 on a stable-only system and file bugs for any packages that need to go stable in the mean time. off the top of my head, the bash completion packages probably need to go stable.
I would also like to use some bash-4 features in some ebuilds. app-shells/bash-completion-1.0-r3 is being stabilized in bug #265504.
but again, it's going to require people actually running it on their stable-only systems for a little while before we call for stabilization. bash has a detailed history of breaking people in unexpected ways.
I think that app-shells/bash-4.0_p24 is ready for stabilization.
Please consider stabilization of app-shells/bash-4.0_p28. =app-shells/bash-4.0* has been in the tree for many months.
everything all set in stable portage and bash-completion for this ? otherwise it should be fine now
(In reply to comment #8) > everything all set in stable portage and bash-completion for this ? > > otherwise it should be fine now > bash-completion is as good as it's gonna get on my watch. (Upstream *really* needs to release a new version). Please request =app-shells/bash-completion-1.0-r5 stable with this. Thanks.
(In reply to comment #8) > everything all set in stable portage and bash-completion for this ? Stable portage is fine. We didn't have to change anything for bash-4.
Satbel on alpha (still has the issues from bug 263105 (scp completing weirdly).
+ 11 Sep 2009; Jeremy Olexa <darkside@gentoo.org> + bash-completion-1.0-r5.ebuild: + amd64 stable, bug 270008 + 11 Sep 2009; Jeremy Olexa <darkside@gentoo.org> bash-4.0_p28.ebuild: + amd64 stable, bug 270008. Passed all tests too
Stable for HPPA.
x86 stable
amd64 and x86 are already done. Removing 10.0 tags.
ppc stable
ppc64 done
sparc stable
arm stable
ia64/s390/sh stable, closing
Apparently m68k was never CC-ed.
m68k stable, closing
