GTK+-2.5.0 released. Release announcement is http://mail.gnome.org/archives/gnome-announce-list/2004-July/msg00023.html Reproducible: Always Steps to Reproduce: 1. 2. 3.
Your link says gtk+-2.4.4 is released, which is allready in portage. Gtk+-2.5 is the development version, moving towards 2.6, so we won't be including it, at least until it reaches maturity (ie close to 2.6).
Oops, I'm sorry my mistake. I know GTK+-2.5.0 is development state and unstable, but "~arch" is also unstable, isn't it? When the previous major version of GTK+ (GTK+-2.4.0, sombody thinks it's minor. but there are many many changes, I don't think it's minor) was released, it suddenly came in portage tree. It couldn't make a soft landing to migrate new version, maybe you know, because there are alot of changes from GTK+-2.2.x. So I think it's better that GTK+-2.5.x series is included in portage tree even it's unstable. Anyway, I'm looking forward to comming of GTK+-2.5.x series in portage tree. thanks.
thats because gtk-2.4 is the stable series. There were no releases of gtk-2.3 in portage. gtk-2.3 is to gtk-2.4 what gtk-2.5 is to gtk-2.6. Following the kernel/gnome style release pattern, odd versioned numbers are development releases and even version numbers are stable releases.
Yes, I know. But I want to know what the Gentoo's unstable means. In the case of Mozilla, Mozilla-1.7 is the next stable version of Mozilla-1.4, 1.5 and 1.6 are the unstable version. Why these version were included in portage? What the difference?
the main issue would be this: ~arch isn't really "unstable", its more untested. If portage were to add gtk+-2.5 into the tree under ~arch, then every new 2.4.x release would have to be marked stable without any testing at all. Plus development versions of libs will most likely cause inconsistency with the api and stable packages.
I'm going to write one more thing about Mozilla (precisely Gecko). Mozilla (Gecko) is a library for embedded browsers like Epiphany and Galeon. But Mozilla-1.5 and 1.6 and 1.7 have no ABI compatibility, of course API compatibility. It is worse than GTK+. Yes, GTK+ is also bad. But the unstable version of Mozilla goes well in portage tree, why doesn't GTK+?
stable and unstable words are used by upstream developers all the time. each maintainer has their own view of what is stable and unstable and what is suitable for the tree or not. you can even say why do we have developer kernels and gcc/glibc prereleases. the current gnome herd policy is that we stick with stable releases. when we do unstable releases, that is a bonus. currently as it stands, we don't have time to track the unstable releases. maybe in the future.
Thank you for your response. I understand now completely. I write a last words for you. The most important thing I think is the upstream developers need more feedbacks and testing for their unstable release, because feedbacks are the main reason of releasing unstable version. You, the developper of Gentoo, need testings to use ~ARCH? Don't you imagine that the upstream also need them? I think the developpers of the distribution should cooperate with the upstream, now you have been doing but more! FYI http://lists.gnu.org/archive/html/bug-grub/2004-07/msg00046.html This isn't GTK+, but I think GTK+ is the same. BTW If I am a developer of Gentoo and a resident of GNOME herd, I can add unstable GTK+ in portage tree? Of course I don't also have enough time to maintain it, but I think it can if all of the developper in GNOME herd cooperate each other. thanks.
~arch isn't for unstable/testing _packages/programs_. it's for testing _ebuilds_. if we kept up with development releases for all of the gnome libraries, we wouldn't get anywhere. The herd won't be adding this or other unstable versions (for example, gstreamer -0.7 series etc) as that's our internal policy. Thanks for your request, we'll get GTK-2.6 in as soon as it's released/mature. Thanks.
Thank you for your kindly response. I understood GNOME herd policy. Thanks. > we'll get GTK-2.6 in as soon as it's released/mature. GTK+-2.6 will not be matured, GTK+-2.4.x is not matured too, they are in highly development state, the stable release is just feature freezing. It annoys me and maybe you. :-) Please close this bug, I'll make a new entry when GTK+-2.6.0 is released.
Reopening to fix resolution.
This was applied to the tree. Thanks for reporting.
