On Wednesday 08 June 2005 16:39, Joseph Jezak wrote: > > Agreed, the PPC team is very good at arbitrarily marking things stable > > whenever they feel like it, and often times before the maintainer does. > > This is not usually our policy. However, because we moved GCC-3.4 to > stable before many arches, there were a number of packages that needed > to be marked stable for PPC in order for the stable version to even > compile. What should we have done in this case then? > If memory serves this is where amd64 had issues, we stabilised GCC 3.4 first I believe as it works much better than GCC 3.3, and so many apps needed patching/unstable versions. Some maintainers were not happy about this. Didn't happen to me as I became a dev after there were some issues raised, and I have always try to contact the maintainer to discuss it first in the rare circumstances where it is needed.
It would probably be helpful to have a ChangeLog entry saying stabilised ppc to fix GCC 3.4 compile problem or words to that effect, but I would expect that most apps have been fixed by us for our stable tree. I did think it had been decided that the maintainer should at least be contacted before stabilising before him/her. -- Gentoo Linux Developer Scientific Applications | AMD64 | KDE | net-proxy
pgpPBJHZzBGYT.pgp
Description: PGP signature
