You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/04/02 09:36:58 UTC
[jira] Updated: (CONTINUUM-670) State of a project
[ http://jira.codehaus.org/browse/CONTINUUM-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-670:
-----------------------------------
Fix Version/s: (was: Future)
1.x
> State of a project
> ------------------
>
> Key: CONTINUUM-670
> URL: http://jira.codehaus.org/browse/CONTINUUM-670
> Project: Continuum
> Issue Type: New Feature
> Components: Core system
> Reporter: Reinhard Spisser
> Fix For: 1.x
>
>
> I suggest to introduce states of the projects: active, disabled and archived
> - active: continuum will check for modifications and build it
> - 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.
> - archived: the project is not show on the main project list, but on a
> "Archived Projects" tab (or something similar). These projects will
> not be build, but build history will remain.
> 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 is enabled
> again.
--
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