1) BUGS
We have to create our own bug tracker for doxygen only..
- this meaans removing and deleting olve bugzilla buugs etc..
-- Feature Requests..
We ahve to look forward and implment..
Issues....
Most of the time its an output
https://bugzilla.gnome.org/enter_bug.cgi?product=doxygen
BUT we need to get away from that and be our won project and bugs,,
ME
- dont like sf.net.. I want a job there please.. to make them mrore dev
friendly..
- and bugzilla is not good for me filing bugs etc..
What so I expect;-)
I expect to file a bug or feature request and get a message back.. somehow
eg dupe or alike or reconginsed.. or oppsie..
So we need to make this more obvious...
Should the future of doxygen be a @bug lisst or @todo list or @wish list ?
We can help with that..
we need to explain a simple markup technique. .using doxyy...... ;-)
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Doxygen-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
