[
https://issues.apache.org/jira/browse/INCUBATOR-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798258#comment-16798258
]
Dave Fisher commented on INCUBATOR-199:
---------------------------------------
As I rebuilt the project page to use git and jbake's groovy template it is
clear that the answer to this is documentation.
# Document how to change names of podlings while they are in incubation
# Document how to properly add the resolutions for these cases:
** Graduation to TLP with the same name
** Graduation to TLP with a new name
** Graduation as a subproject in an existing TLP
** Retirement where the project has a new or old home
** Retirement
I think we should have a page that is only about podlings.xml and another page
that is only about projects/(podling).xml. It should have specific use cases.
> 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
