[
https://issues.apache.org/jira/browse/INCUBATOR-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796807#comment-16796807
]
David Fisher commented on INCUBATOR-199:
----------------------------------------
An example on the guide page is needed.
Here is what I've seen done in podlings.xml and in the clutch process.
On name changes the old resource attributes have been copied to the
alternateResouces attribute. (There are other cases of alternates.) If there
are multiple then this is a list. (I need to fix clutch2 for
bval/beanvalidation case)
There are other exceptions in what is happening with projects/${resources}.xml
status files.
BTW - The other spot to indicate name changes is in the news section. This is
already parsed by the clutch analysis for new committers.
Let's track this in this issue which is close enough.
> Extend podlings.xml to include old names and TLP parent
> -------------------------------------------------------
>
> Key: INCUBATOR-199
> URL: https://issues.apache.org/jira/browse/INCUBATOR-199
> Project: Incubator
> Issue Type: New Feature
> Reporter: Sebb
> Priority: Major
>
> Podling names change fairly often.
> It would be useful to be able to list old names in the podlings file.
> At present this info is only in the free-form text.
> Also where a podling graduates as a project of a PMC, it would be useful to
> be able to document the PMC. At present this would have to be extracted from
> the url field (or the text)
> AFAIK additional attributes do not cause problems for existing parsing
> routines. However the DTD will have to be extended to allow for the new
> entries.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
