| RE: [cdt-dev] Two weeks for documentation? |
|
> If no one else intends to improve the documentation in
the 2 weeks following RC3, then don’t plan an RC4 just for me… 8-), I would like to say yes, just for
tease. But we made the proposal because, after
RC3 we were planning to go through the Debug docs and the CDT docs too. Last time, thanks to the Altera folks (Miranda),
lots of typos and obsolete actions were caught on time. But you are right, it may not be necessary
to go through the entire 2 weeks. Concurrently, this is a request to the
community to give us feedback on the docs. From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Regarding the extra 2 weeks for documentation, here is the
current status of the MBS documentation: - I have finished my updating of the end-user
documentation. Others intend to review it, so the extra 2 weeks would get
it in better shape, but I believe it is OK as-is. - I am in the process of updating the ISV
“Managed Build System Extensibility” document. This will
probably not be as fully updated as I would like by next Wed, since I’ll
be away from the internet tomorrow -> Tues. If no one else intends to improve the documentation in the 2
weeks following RC3, then don’t plan an RC4 just for me… Regards, Leo |