Re: [cross-project-issues-dev] Provider and feature names

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [cross-project-issues-dev] Provider and feature names

From: Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
Date: Tue, 18 Nov 2014 07:53:23 +0100
Delivered-to: cross-project-issues-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cross-project-issues-dev>
List-help: <mailto:cross-project-issues-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=unsubscribe>

Tom,

> Am 17.11.2014 um 22:26 schrieb Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>:
> I disagree with you on that. I think it has value that the project name
> is in the feature name and the reason it simple: Better grouping on the
> p2-Update-UI!


Those points seems valid … but isn’t it insane how we constrain ourselves to drive a decision because of some broken UI? I actually prefer more descriptive feature names and stopped repeating the project name in features.

-Gunnar


-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx

Follow-Ups:
- Re: [cross-project-issues-dev] Provider and feature names
  - From: Tom Schindl

References:
- [cross-project-issues-dev] Provider and feature names
  - From: Wayne Beaton
- Re: [cross-project-issues-dev] Provider and feature names
  - From: Tom Schindl

Prev by Date: Re: [cross-project-issues-dev] https repository could not be resolved in Hudson HIPP job
Next by Date: Re: [cross-project-issues-dev] Provider and feature names
Previous by thread: Re: [cross-project-issues-dev] Provider and feature names
Next by thread: Re: [cross-project-issues-dev] Provider and feature names
Index(es):
- Date
- Thread

Breadcrumbs