[jira] [Commented] (COMDEV-143) Allow for multi-product PMCs

["Hervé Boutemy (JIRA)" <ji...@apache.org>]

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

Hervé Boutemy commented on COMDEV-143:
--------------------------------------

in projects new, vocabulary used is "committee+projects" = https://projects-new.apache.org/committees.html + https://projects-new.apache.org/projects.html, instead of former "TLP+project", or here "PMC+product"
we should really find a consensus on vocabulary, since that's a recurring part of the problems we have when working together and having misunderstanding on what we are talking about: a team or a software?

> Allow for multi-product PMCs
> ----------------------------
>
>                 Key: COMDEV-143
>                 URL: https://issues.apache.org/jira/browse/COMDEV-143
>             Project: Community Development
>          Issue Type: New Feature
>          Components: Reporter Tool
>            Reporter: Sebb
>
> Some PMCs release multiple independent products.
> However there is only a single release version database for each PMC.
> The current work-round is to prefix the version with the product name.
> For example Apache Commons might use versions of the form:
> LANG-1.2.0
> and
> IO-2.3
> It might be better to provide an optional field for the product name.
> [Could perhaps be made a required field for PMCs known to have multiple products?]
> As an initial implementation, it could be just prepended as per the work-round.
> The releases database format could later be changed to store the prefix separately. This would allow more sophisticated displays and statistics; easier grouping of related releases. etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)