Documentation should be in its own project and not be a component of TRUNK. So, a documentation sprint can live in its own project, with its greenhoppers, issues etc.
TRUNK (although a mis-represented name, should have been CORE), I feel is for the source code issues for OpenMRS core and shouldn't be mixed with documentation-related stuff, unless javadoc or maven site --- Regards, Saptarshi PURKAYASTHA My Tech Blog: http://sunnytalkstech.blogspot.com You Live by CHOICE, Not by CHANCE On 22 September 2011 17:08, Ben Wolfe <[email protected]> wrote: > In a recent OpenMRS > University<https://wiki.openmrs.org/display/RES/OpenMRS+University>call > Darius started setting up OpenMRS from scratch as a developer. There > were issues with the latest eclipse and links, dialogs, etc. > > Can I get someone to step up and own updating the page for the latest > Eclipse for us this time? > https://wiki.openmrs.org/display/docs/Step+by+Step+Installation+for+Developers > > I don't want this to be an Eclipse vs everything else flamewar. Yes, we > all know you love your IDEs, but for the time being most of us are using > eclipse. If you want your IDE on there, feel free to add a section below > the Eclipse one. > > In other news, I don't know where something like this would go as a ticket. > TRUNK with a component of Documentation? > > Ben > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
