Mailing-List: contact commits-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Date: Wed, 8 Jul 2015 11:07:05 +0000 (UTC)
From: "Sebb (JIRA)" <jira@apache.org>
To: commits@community.apache.org
Message-ID: <JIRA.12843191.1436277300000.128790.1436353625557@Atlassian.JIRA>
In-Reply-To: <JIRA.12843191.1436277300000@Atlassian.JIRA>
References: <JIRA.12843191.1436277300000@Atlassian.JIRA>
 <JIRA.12843191.1436277300735@arcas>
Subject: [jira] [Commented] (COMDEV-143) Allow for multi-product PMCs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sebb commented on COMDEV-143:
-----------------------------

That is better discussed on the mailing list.

> 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)