W3C home > Mailing lists > Public > spec-prod@w3.org > July to September 2012

biblio.js update best practice?

From: <Frederick.Hirsch@nokia.com>
Date: Mon, 24 Sep 2012 17:22:23 +0000
To: <spec-prod@w3.org>
CC: <Frederick.Hirsch@nokia.com>
Message-ID: <1CB2E0B458B211478C85E11A404A2B270178E83D@008-AM1MPN1-033.mgdnok.nokia.com>
What is the best way to test a change to biblio.js before pulling it into the main build?

Is there a way to create a local build that you can link to from your document to test out any bibliography changes or additions?

I'm not quite sure how to do this as currently my documents link to the latest W3C build, and even linking to the github build will mean that the edits have already been shared with others...

I could craft a test document/Javascript to pull in biblio.js and generate a full bibliography for testing - has anyone already done this?

thanks

regards, Frederick

Frederick Hirsch
Nokia
Received on Monday, 24 September 2012 17:22:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 24 September 2012 17:22:52 GMT