[DOCS-752] Document switch from spidermonkey to v8 scripting engine Created: 14/Nov/12  Updated: 12/Jan/13  Resolved: 30/Nov/12

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-2.2
Fix Version/s: mongodb-2.4

Type: Task Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-981 Document JavaScript interface changes... Closed
Participants:
Days since reply: 11 years, 11 weeks, 2 days ago

 Description   

Need to update the docs to reflect the change to v8. We now need a major overhaul of the docs for SpiderMonkey, V8, Windows building, and C++ driver building.

This might be a sub-ticket for overall refactor of: http://www.mongodb.org/display/DOCS/Building



 Comments   
Comment by Daniel Pasette (Inactive) [ 04/Dec/12 ]

the reason i barked is because what was covered in the release notes is quite different (build instructions) than primary user facing v8-ness. As long as it's not lost, you can manage the workflow as you like.

Comment by Sam Kleinman (Inactive) [ 03/Dec/12 ]

We (I) closed all tickets 2.4 features that we documented in the release
notes. We'll go back through the release notes after branching and
integrate documentation of this feature into the manual content, but
that's a separate body of work, and the release notes themselves capture
all the work that we need to do on that project.

Does it make sense for you all to leave these tickets open for longer?


Sam Kleinman (@tychoish)
Lead Technical Writer
10gen (the MongoDB Company)
samk@10gen.com

Comment by Daniel Pasette (Inactive) [ 30/Nov/12 ]

how is this closed?

Generated at Thu Feb 08 07:39:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.