[ros-bugs] [Bug 861] Integrate services from svn.reactos.com

[ReactOS.Bugzilla at www.reactos.org]

http://www.reactos.org/bugzilla/show_bug.cgi?id=861


Colin Finck <mail at colinfinck.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mail at colinfinck.de

amine48rz <amine48rz at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

ThePhysicist <timo.kreuzer at web.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |timo.kreuzer at web.de

amine48rz <amine48rz at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW

pcds90net <pcds90net at yahoo.co.jp> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pcds90net at yahoo.co.jp




--- Comment #8 from Colin Finck <mail at colinfinck.de>  2007-10-06 21:11:32 CET ---
Maybe we can close this bug:

- A web interface for downloading revision ISO's has been added to the Website
(Link "Trunk Builds")

- This interface also contains a link to the ViewVC repository browser on
svn.reactos.org.

- An API-Status page doesn't exist at the moment.
This would require that we first define how such an API-Status page should
work.

Shall all API functions be marked with @implemented and @unimplemented or
similar?
Steven already mentioned that many API functions can't just be marked this way.
The only safe way to check them would be writing several tests for each
function, so different aspects of the functions are tested. And for creating an
API-Status page, all these tests must have a similar output...
I think this API Status stuff should be discussed in another bug ticket and not
just be treated as a Website component.


--- Comment #9 from ThePhysicist <timo.kreuzer at web.de>  2007-10-08 12:29:50 CET ---
I have include a functionality to create a html apistatus in the test framework
I wote. We only need hundreds of tests that test at least if the function
returns an unimplemented error code ;-)


--- Comment #10 from Dr. Fred <maarten.paul at bosma.de>  2007-10-21 14:41:42 CET ---
When I wrote this bug report I was referring to the API status xml which rbuild
generates and which was on the svn server by that time.


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.