Change Details

We should have Parsoid-specific implementations of extensions live in the extension repositories. Couple of things to keep in mind when we do this: * See if we can preserve git history of Cite development in Parsoid * Ensure we turn on / enable integrated-mode testing of parser tests (if necessary, by adding html/parsoid+integrated sections to newer files that don't already have them) * Figure out if we can preserve standalone testing mode for this extension since we often rely on this for debugging / bug fixes. * If the above is not possible, we should at least move tests in parser test file that us <ref>/<references> to integrated mode only

We should have Parsoid-specific implementations of extensions live in the extension repositories. Things to keep in mind when we do this: * See if we can preserve git history of Cite development in Parsoid * Ensure we turn on / enable integrated-mode testing of parser tests (if necessary, by adding html/parsoid+integrated sections to newer files that don't already have them) * Figure out if we can preserve standalone testing mode for this extension since we often rely on this for debugging / bug fixes. * If the above is not possible, we should at least move tests in parser test file that us <ref>/<references> to integrated mode only * By default, we will no longer be able to run rt-testing on not-yet-deployed code in the Cite repository (as we have been so far) since extension code are deployed to scandium as part of the train. @cscott has a proposal to deploy Cite separately just like Parsoid code is deployed on scandium and use class loading hacks to have Cite come from there.

We should have Parsoid-specific implementations of extensions live in the extension repositories. Couple of tThings to keep in mind when we do this: * See if we can preserve git history of Cite development in Parsoid * Ensure we turn on / enable integrated-mode testing of parser tests (if necessary, by adding html/parsoid+integrated sections to newer files that don't already have them) * Figure out if we can preserve standalone testing mode for this extension since we often rely on this for debugging / bug fixes. * If the above is not possible, we should at least move tests in parser test file that us <ref>/<references> to integrated mode only * By default, we will no longer be able to run rt-testing on not-yet-deployed code in the Cite repository (as we have been so far) since extension code are deployed to scandium as part of the train. @cscott has a proposal to deploy Cite separately just like Parsoid code is deployed on scandium and use class loading hacks to have Cite come from there.