On 21 August 2014 17:34, Anders Roxell <[email protected]> wrote:
> On 2014-08-21 16:21, Bill Fischofer wrote: > > Please publish as it is complete and useful in its own right and > accurately > > reflects what was submitted for LNG-SC approval. Then open a bug for the > > rework. The rework you suggest is non-trivial and is non-gating here. > > Thanks. > > Does anyone else have any ideas how to handle this? > My 2 cents: I think that having the arch doc clean from the outset sounds good to me, vs having to extract the API definitions later. In this case we have started out top down and the output from that process should be the google 1st draft, then the git arch doc followed by an API definition (.h file) and then an implementation. In this case we have merged the two middle documents to some degree. I can see the benefit in splitting the .h file in that it forms a strong prototype for the first implementation of classification, at which point the one in the arch directory is deleted and everything moves forward with the two final documents, the arch doc and the real .h file. I can see a second benefit in that it makes the arch doc source a little easier to read without the problems of doxygen seeing markup for itself in the prototypes that are only in there because there is no .h file yet. > Cheers, > Anders > > > > > Bill > > > > > > On Thu, Aug 21, 2014 at 4:16 PM, Anders Roxell <[email protected] > > > > wrote: > > > > > On 2014-08-21 15:37, Bill Fischofer wrote: > > > > The argument is understood, however it's not what we did for the > crypto > > > API > > > > and the CARD for this activity has already been closed. We should > > > publish > > > > this now and then create a new CARD for the restructure as part of > the > > > > classification implementation work. These are not final docs, simply > > > "exit > > > > design phase" docs. > > > > > > That is true, Robbie started the crypto implementation for > linux-generic > > > before we had the architecture doc for it. > > > > > > This is the first time we actually does it the "correct" way. > > > Starting with the architecture doc and then, start the implementation. > > > Thats why it is more important to have the .h file to guide people. > > > > > > > > > > > > > > _______________________________________________ > lng-odp mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/lng-odp > -- *Mike Holmes* Linaro Technical Manager / Lead LNG - ODP
_______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
