continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (CONTINUUM-670) State of a project - ability to disable projects
Date Wed, 22 Apr 2009 16:14:44 GMT

     [ http://jira.codehaus.org/browse/CONTINUUM-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed CONTINUUM-670.
----------------------------------

      Assignee: Brett Porter
    Resolution: Won't Fix

archiving sounds good. I think disabling is better done through the removal of permissions
and schedule

> State of a project - ability to disable projects
> ------------------------------------------------
>
>                 Key: CONTINUUM-670
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-670
>             Project: Continuum
>          Issue Type: New Feature
>          Components: Core system
>            Reporter: Reinhard Spisser
>            Assignee: Brett Porter
>
> I suggest to introduce states of the projects: active, disabled and archived
> - disabled: the project remains on the same "project list" as the
> active project (the continuum homepage), but the project links are
> greyed out. Continuum will not check for modifications. Projects can
> be enabled again to become active.
> With this states, someone could write a program that disables a
> project if no commits were done in the last x weeks and archives a
> project if no commits were done in the last x months. Also, if a
> commit is done in a disabled project then the project could be enabled
> again.
> (This issue was split into two - see CONTINUUM-2099 for the ability to archive a project.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message