FreeLists / openbeosstorage / [openbeosstorage] Development Cycle Proposal

["Tyler Dauwalder" <tyler@xxxxxxxxxxxxx>]

Okay, here's a stupid pseudocode algorithm for my
proposal for our individual development cycles:

develop(class)
        header(OpenBeOS::class)
        unittest(R5::class)
        implementation(OpenBeOS::class)

                
Basically, when we go to start working on a given class,
we first create a brand new header based off the R5 header.  
Add dox comments for the class and all its members, and maybe 
write up an empty implementation that just returns error values.

Next, write up a relatively complete unit test for your class 
against the R5 version.  Not only will this give us a way to test 
our own implementations as we go, it will make sure we've used 
all or nearly all of the class' features to some degree. Plus, as
Simon mentioned, being able to test against the R5 versions
will help verify we're doing things right.

Finally, write our own implementation of the class.  We'll add
kernel=5Finterface functions as we go, as we need them. 


There's no reason we each have to follow this plan precisely 
and to the letter. If there's a little overlap of between writing 
the header and working on the unittest or implementation, so
be it. Whatever works. But I think it would be a good to follow 
this reasonably closely. 

Any thoughts or suggestions=3F

-Tyler