Bug 798587 - rhc-list-stale treats new app as stale when local date fell behind
Summary: rhc-list-stale treats new app as stale when local date fell behind
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 1.x
Hardware: All
OS: All
high
high
Target Milestone: ---
: ---
Assignee: Mrunal Patel
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-29 10:39 UTC by Linqing Lu
Modified: 2013-04-30 22:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-02 21:56:41 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Linqing Lu 2012-02-29 10:39:05 UTC 
Description of problem:
because rhc-list-stale bases on latest commit date of the app repo, so it will affected by the accuracy of user's local date

Version-Release number of selected component (if applicable):
devenv_1649

How reproducible:


Steps to Reproduce:
1. set local date as 2011-1-1
2. create an app and make a commit
3. check rhc-list-stale in devenv
  
Actual results:
the newly created app is listed as stale

Expected results:
the newly created app should not be listed as stale

Additional info:
Comment 1 jizhao 2012-03-01 03:31:18 UTC 
Verified on devenv-stage_139.
Note You need to log in before you can comment on or make changes to this bug.