You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Robert Meyer (JIRA)" <ji...@apache.org> on 2014/07/01 14:22:25 UTC

[jira] [Commented] (INFRA-7929) Adding a markdown extension for the purpose of release automation

    [ https://issues.apache.org/jira/browse/INFRA-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048804#comment-14048804 ] 

Robert Meyer commented on INFRA-7929:
-------------------------------------

Hi Jake,

I've taken a look at the path.pm file and as you say it seems to fulfill our need for tag replacement. I will investigate more how this can be used but since my question has been answered I will close this issue.

Many thanks,

Robert Meyer

> Adding a markdown extension for the purpose of release automation
> -----------------------------------------------------------------
>
>                 Key: INFRA-7929
>                 URL: https://issues.apache.org/jira/browse/INFRA-7929
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: CMS
>            Reporter: Robert Meyer
>            Assignee: Jake Farrell
>            Priority: Minor
>
> I would like to enquire about the possibility of adding a markdown extension for the purpose of helping automate the release process on the Apache FOP project. An extension was deemed the best way to accomplish this as it can be used to update the various version numbers on the site whilst supporting the web interface. Would adding an extension be possible for just the FOP project and what would be involved in doing this? The original discussion for this can be found here:
> http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/201405.mbox/%3CDUB120-W248BA988C7FB6A6CFAB671863C0%40phx.gbl%3E



--
This message was sent by Atlassian JIRA
(v6.2#6252)