1. 09 Apr, 2012 1 commit
  2. 03 Apr, 2012 2 commits
  3. 02 Apr, 2012 1 commit
    • Frederic Peters's avatar
      3.4: branch modules · ad6224df
      Frederic Peters authored
      atk, evolution-data-server, gnome-desktop, libgnomekbd, gnome-settings-daemon,
      gnome-control-center, gnome-packagekit, gnome-themes-standard, mousetweaks,
      gtkhtml, evolution, vino, yelp-tools, brasero, empathy, epiphany, gcalctool,
      gnome-contacts, gnome-system-monitor, accerciser, gdl, anjuta,
      gnome-video-effects, cheese, gnome-boxes, gnome-color-manager, gnome-games,
      ghex, orca, totem, vinagre.
      ad6224df
  4. 28 Mar, 2012 1 commit
  5. 27 Mar, 2012 1 commit
  6. 24 Mar, 2012 1 commit
  7. 23 Mar, 2012 4 commits
  8. 22 Mar, 2012 2 commits
  9. 21 Mar, 2012 1 commit
  10. 20 Mar, 2012 2 commits
  11. 17 Mar, 2012 3 commits
  12. 14 Mar, 2012 1 commit
  13. 12 Mar, 2012 1 commit
  14. 11 Mar, 2012 1 commit
  15. 09 Mar, 2012 1 commit
  16. 08 Mar, 2012 1 commit
  17. 05 Mar, 2012 1 commit
  18. 02 Mar, 2012 1 commit
  19. 01 Mar, 2012 2 commits
    • Javier Jardón's avatar
      3.4: Split module dependencies in two separete files · 94c8188c
      Javier Jardón authored
      core-deps-base for "1st level" deps
      core-deps      for "2nd and 3rd level" deps
      
      https://mail.gnome.org/archives/desktop-devel-list/2011-May/msg00428.html
      
      ** 1st level **
      
        Established, stable, system modules, they have been in
        place for a long time, with stable API and ABI, and they exist in
        sufficient versions in the distributions commonly used by GNOME
        hackers, even in older but still used versions (Fedora 13 for
        example).
      
        Examples : libxml2, libpng, dbus...
      
        Proposed guideline : mentioned as dependencies with a base version,
        not built by default by jhbuild.
      
        Rationale : we want to reduce the number of modules that need to be
        built to start developing on GNOME.
      
      ** 2nd level **
      
        Modules developed outside GNOME, with little attention to our
        schedule, but with an active development, and where we want to track
        recent code.
      
        Examples : mozilla (js-185 nowadays), poppler.
      
        Proposed guideline : built from tarballs, version bumps whenever a
        module need a new version.
      
        Rationale : we need recent code, but we do not want to arrive on a
        release days with modules failing to build because they require some
        code only available in $DVCS.
      
      ** 3rd level **
      
        Modules developed outside GNOME, with attention to our schedule
        (i.e. we can ask for a tarball and get it in two days).
      
        Examples : webkitgtk, polkit.
      
        Proposed guideline : treated like any other GNOME module, built from
        latest git.
      
        Rationale : we do not need to put extra burden on modules that are
        close to us.
      94c8188c
    • Javier Jardón's avatar
      6d6a5ec5
  20. 29 Feb, 2012 3 commits
  21. 28 Feb, 2012 1 commit
  22. 27 Feb, 2012 2 commits
  23. 25 Feb, 2012 1 commit
  24. 23 Feb, 2012 3 commits
  25. 22 Feb, 2012 1 commit
  26. 21 Feb, 2012 1 commit