You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2009/03/12 06:54:50 UTC
[jira] Created: (INFRA-1936) Dates on the staging repositories
Dates on the staging repositories
---------------------------------
Key: INFRA-1936
URL: https://issues.apache.org/jira/browse/INFRA-1936
Project: Infrastructure
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Nexus
Reporter: David Blevins
Likely not the best place for a feature request, sorry...
Would be great if I could get a human readable time stamp for a staging repo somewhere in the gui. Only way to tell one from the other is the hash on the end of the repo name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-1936) Dates on the staging repositories
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot updated INFRA-1936:
-------------------------------------
Assignee: Gavin
> Dates on the staging repositories
> ---------------------------------
>
> Key: INFRA-1936
> URL: https://issues.apache.org/jira/browse/INFRA-1936
> Project: Infrastructure
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: David Blevins
> Assignee: Gavin
>
> Likely not the best place for a feature request, sorry...
> Would be great if I could get a human readable time stamp for a staging repo somewhere in the gui. Only way to tell one from the other is the hash on the end of the repo name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-1936) Dates on the staging repositories
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-1936.
----------------------------
Resolution: Fixed
Assignee: Brian Fox
there is a date column now and the repos are sequentially numbered.
> Dates on the staging repositories
> ---------------------------------
>
> Key: INFRA-1936
> URL: https://issues.apache.org/jira/browse/INFRA-1936
> Project: Infrastructure
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: David Blevins
> Assignee: Brian Fox
>
> Likely not the best place for a feature request, sorry...
> Would be great if I could get a human readable time stamp for a staging repo somewhere in the gui. Only way to tell one from the other is the hash on the end of the repo name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-1936) Dates on the staging repositories
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot updated INFRA-1936:
-------------------------------------
Assignee: (was: Gavin)
> Dates on the staging repositories
> ---------------------------------
>
> Key: INFRA-1936
> URL: https://issues.apache.org/jira/browse/INFRA-1936
> Project: Infrastructure
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: David Blevins
>
> Likely not the best place for a feature request, sorry...
> Would be great if I could get a human readable time stamp for a staging repo somewhere in the gui. Only way to tell one from the other is the hash on the end of the repo name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.