Openbravo Issue Tracking System - Tools
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0005676ToolsOtherspublic2008-10-27 15:452008-10-27 18:55
Reporterplujan 
Assigned Topnuding 
PrioritynormalSeverityminorReproducibilityN/A
StatusnewResolutionopen 
PlatformOS5OS Version
Merge Request Status
Review Assigned To
OBNetwork customer
Summary0005676: All projects should have a short code to easy identification
DescriptionCurrently, there are no naming standards for projects deliverables. For better understanding, it will be helpful to have a standard Long Name (let's say 50 chars long) and a short name (may be 10 or 15 chars length).
The short name should be used for SVN branch naming, and also as a prefix of wiki related pages, as well as for any documentation of the project, at least when still in development.
For example, bugs starting with [UUID] are those found while developing the Universal Unique IDentifiers. Once merged to trunk, no prefix will be required, and also a prefix usage will be discouraged since functional implications are not limited to a particular project.
In order to avoid naming misunderstandings, short names should be unique across versions. A new UUID project on 2.60 should not use the UUID tag.
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-10-27 15:45plujanNew Issue
2008-10-27 15:45plujanAssigned To => cromero
2008-10-27 15:45plujansf_bug_id0 => 2200951
2008-10-27 15:45plujanRegression testing => No
2008-10-27 15:45plujanAssigned Tocromero => pjuvara
2008-10-27 18:54pjuvaraAssigned Topjuvara => pnuding
2008-10-27 18:55pjuvaraProjectOpenbravo ERP => Tools

There are no notes attached to this issue.