Gnome 2.28.1 full steam

My CIA profile went from about one commit every 17.35 housr to one every 16.56. The difference does not seem big but the calculation is diluted on about 6 years due to a KDE dev sharing the same nick. This amounts to 158 commits tonight.

~arch is now at about 85% of completeness for Gnome 2.28.1, a few commits are missing due extra complexity (hey it still took my 3 hours to do that). Beware that this release still has a few rough edges, especially policykit migration buts. So if you get cut, please come to bugzilla but do not expect sweet words and attention if I see comments like “dude why do you keep on breaking ~arch”. It’s ~arch, beat it.

3 thoughts on “Gnome 2.28.1 full steam”

  1. I’m not sure what do you mean by “break” but if you need some help from people make sure it’s “survivable” broken, i.e. it’s still possible to use the system and it’s getting closer to the stable stage with each “break” 😉
    Beat your local portage in other cases.

  2. Great work! I’ve been waiting for Gnome 2.28, especially since I saw the new GDM in Ubuntu 9.10. It’s a lot nicer than the old interface.

    I did see that GDM was masked (>2.26) so I unmasked it and it worked out great. It was masked due to “feature regressions”, but I don’t get it:
    1. Why did the Gnome team remove the features?
    2. Doesn’t Gentoo need to catch up anyway, we need to leave the 2.26 at some time don’t we?

    Finally, I just want to say “good work!” again =)

  3. @AzP, gdm 2.26 and 2.28 are masked because of missing xdmcp support, missing configuration panel and a few other stuff. Although given upstream reluctance to actually fix these issues we might just end up going with the flow.

    Haven’t had a chance to see how ubuntu 9.10 is doing since I haven’t seen the result of the update yet.

    About your other points:
    1. removing feature ? what, where, I’m not aware of any feature removal that is directly due to the work of the gentoo gnome team.

    2. catching up on what, we have latest stable, 2.26 which is reasonable about only 1 month and a half of 2.28. Hopefully 2.28 won’t be delayed as long as 2.26 was but I can’t promise anything since I have a busy agenda IRL.

Comments are closed.