Commits on Jan 3, 2012
  1. se build

    swarmingbee committed Jan 3, 2012
  2. Merge remote-tracking branch 'katello/master' into branding

    swarmingbee committed Jan 3, 2012
  3. Add package list

    bkearney committed Jan 3, 2012
  4. First cut at a katello-debug

    bkearney committed Jan 3, 2012
  5. adding reindex rake task

    jlsherrill committed Jan 3, 2012
  6. moving /distributions API into /repositories path

    Since Katello does not have any distribution model class and Pulp is not
    able to provide what repository this distribution belongs to, we would need
    to change the route to:
    So the controller code would be able to fetch repository/product and check
    On top of that, cli command distribution info now require new parameter
    lzap committed Jan 3, 2012
  7. Merge branch 'master' into templates-repo

    bbuckingham committed Jan 3, 2012
  8. 771352 - SAM does not need to use the katello-jobs

    this should be removed from the code path which the installer uses.
    lzap committed Jan 3, 2012
  9. Revert "api perms review - changesets"

    This reverts commit cc05e6e.
    Authorize filter call must be executed after other filters in some cases
    lzap committed Jan 3, 2012
Commits on Jan 2, 2012
  1. api perms review - changesets

    lzap committed Jan 2, 2012
Commits on Dec 23, 2011
  1. api perms - changesets unittests

    lzap committed Dec 23, 2011
  2. api perms - changesets

    lzap committed Dec 23, 2011
Commits on Dec 22, 2011
  1. system templates - fix packages, groups and repos to be consistent w/…

    … promotions
    This commit contains minor changes to make the elements for system templates
    packages, groups and repos (in left sliding tree) to be consistent with
    how the elements look in other sliding trees (e.g. promotions)
    bbuckingham committed Dec 22, 2011
  2. Updates to the website - new screenshots that match Katello Look and …

    …Feel as well as new fedora information.
    knowncitizen committed Dec 22, 2011
  3. 768047 - promotions - let user know if promotion fails

    Prior to this commit, if a promotion fails, the promotion page
    continually indicates 'Promoting...'.  As a result, the only way
    for the user to know that it failed was to reload the page.
    With this commit, the UI will update the status to indicate
    'Promotion failed'.  In addition, it will allow the user to resubmit
    the promotion request.
    This commit does not show details on the actual error that occured.
    Will be looking at adding more details in via a 'notice'; however,
    notices are owned by the ApplicationController and the
    promotion is handled as an async delayed job, which does not have
    access to the controller.  As a result, will have to do a bit of
    refactoring to enable that access.
    bbuckingham committed Dec 22, 2011