I have reordered some projects in the Issue Tracker, in particular those
related to "eProjects". We previously had:
eProjects
|- Single Sign-on
|- Translations stats
|- Web
|- Wiki
These projects were clearly an overkill because the usage was very low
and the project owners did not use it at all. That is, we had 1 project
and 4 subprojects that were being totally ignored.
On the other hand there was an uncovered need: the ability to report
issues against {code,builds,live.builds,liveqa.builds}.openbravo.com.
It would be nice to be able to report any problems to the issue tracker,
so that the admins get notified and they take actions in an ordered way.
As a consequence I've created a subproject inside "Tools" called
"Infrastructure". And it has one category per every service:
Tools
|- Infrastructure
|- Categories:
- code.openbravo.com
- issues.openbravo.com
- planet.openbravo.com
- builds.openbravo.com
- live.builds.openbravo.com
- liveqa.builds.openbravo.com
- www.openbravo.com
- (...)
>From now on, should you have any problems with those servers, please
report an issue in the "Infrastructure" subproject.
Regards,
Juan Pablo
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Openbravo-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-development
