+ 1 as well. We should have a coding sprint and do a feature freeze and just focus on java docs for a while.
But its more important to get docs for API's, we probably want to start there first. Suresh On Jun 21, 2012, at 7:02 PM, Saminda Wijeratne wrote: > +1 > > Saminda > > On Thu, Jun 21, 2012 at 5:03 PM, Heshan Suriyaarachchi < > [email protected]> wrote: > >> Hi Devs, >> >> On a side note, I noticed that we did not have that much of documentation >> done on the code. Therefore, the generated JavaDoc does not look complete. >> So, it'll be good if we have a hackathon and fix this up. >> >> On Thu, Jun 21, 2012 at 4:58 PM, Heshan Suriyaarachchi < >> [email protected]> wrote: >> >>> Hi Saminda, >>> >>> On Thu, Jun 21, 2012 at 4:09 PM, Saminda Wijeratne <[email protected] >>> wrote: >>> >>>> In Airavata site [1] we can have a releases/docs/0.4 location to host >> the >>>> java-docs which we can expose through the website. We can keep adding >> new >>>> release docs without removing older ones... However it would be great if >>>> we >>>> can do this via buildbot rather than checking in the java docs. >>>> >>> +1 >>> It sounds good. I will look at how other Apache projects are doing this. >>> >>>> >>>> Thanks, >>>> Saminda >>>> >>>> 1. >>>> >>>> >> https://svn.apache.org/repos/asf/incubator/airavata/site/trunk/content/airavata/ >>>> >>>> On Thu, Jun 21, 2012 at 3:59 PM, Heshan Suriyaarachchi < >>>> [email protected]> wrote: >>>> >>>>> Hi Devs, >>>>> >>>>> Now the Java doc generation is integrated to the build of Airavata. We >>>> need >>>>> to point to this generated java-docs, from Airavata wiki. Therefore, >> we >>>>> need to host the java docs at some place. Where should we host it? Any >>>>> suggestions? >>>>> >>>>> -- >>>>> Regards, >>>>> Heshan Suriyaarachchi >>>>> >>>>> http://heshans.blogspot.com/ >>>>> >>>> >>> >>> >>> >>> -- >>> Regards, >>> Heshan Suriyaarachchi >>> >>> http://heshans.blogspot.com/ >>> >> >> >> >> -- >> Regards, >> Heshan Suriyaarachchi >> >> http://heshans.blogspot.com/ >>
signature.asc
Description: Message signed with OpenPGP using GPGMail
