[
https://issues.apache.org/jira/browse/COMDEV-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114346#comment-15114346
]
Sebb commented on COMDEV-182:
-----------------------------
URL: http://svn.apache.org/viewvc?rev=1726501&view=rev
Log:
COMDEV-182 Tidy up handling of data/ changes
Don't SVN move rdf file to committee-retired
Modified:
comdev/projects.apache.org/scripts/cronjobs/parsecommitteeinfo.py
> Tidy up handling of data/ changes
> ---------------------------------
>
> Key: COMDEV-182
> URL: https://issues.apache.org/jira/browse/COMDEV-182
> Project: Community Development
> Issue Type: Bug
> Components: Projects New
> Reporter: Sebb
>
> At present, projects.a.o relies on manual intervention to update the index
> files under data/
> committees.xml
> projects.xml
> The cron job currently moves RDF files from data/committees/ to
> data/committees-retired/ if it detects that a PMC has been retired.
> However it does not attempt to update the xml files, and the SVN
> projects_role is not able to commit files under data/
> This means that the workspace on people.a.o gets out of date.
> The data/ area is also updated manually.
> This makes it difficult to commit changes without running the risk of locking
> the workspace on people.a.o.
> The cronjobs should not attempt to tidy up the RDF files in this area; that
> should be left to manual intervention.
> There needs to be a separate script to tidy the data/ tree.
> The cronjobs should report any discrepancies, but not attempt to resolve them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
