Revision: 15514
Author: [email protected]
Date: Fri Jul 5 04:32:57 2013
Log: Edited wiki page Source through web user interface.
http://code.google.com/p/v8/source/detail?r=15514
Modified:
/wiki/Source.wiki
=======================================
--- /wiki/Source.wiki Fri Mar 8 01:03:18 2013
+++ /wiki/Source.wiki Fri Jul 5 04:32:57 2013
@@ -28,9 +28,14 @@
There are several different branches of V8; if you're unsure of which
version to get, you most likely want the up-to-date stable version in
`trunk/`. Here's an overview of the different branches:
* The bleeding edge, `branches/bleeding_edge/`, is where active
development takes place. If you're considering contributing to V8 this is
the branch to get.
- * Under `trunk/` is the "stable edge", which is updated a few times per
week. It is a copy of the bleeding edge that has been successfully tested.
Use this if you want to be almost up to date and don't want your code to
break whenever we accidentally forget to add a file on the bleeding edge.
+ * Under `trunk/` is the "stable edge", which is updated a few times per
week. It is a copy of the bleeding edge that has been successfully tested.
Use this if you want to be almost up to date and don't want your code to
break whenever we accidentally forget to add a file on the bleeding edge.
Some of the trunk revisions are tagged with X.Y.Z.T version labels. When we
decide which of X.Y.*.* is the "most stable", it becomes the X.Y branch in
subversion.
* If you want a well-tested version that doesn't change except for
bugfixes, use one of the versioned branches (e.g. `branches/3.16/` at the
time of this writing). Note that usually only the last two branches are
actively maintained; any older branches could have unfixed security holes.
You may want to follow the V8 version that Chrome is shipping on its stable
(or beta) channels, see [http://omahaproxy.appspot.com].
+== V8 public API compatibility ==
+
+V8 public API (basically the files under include/ directory) may change
over time. New types/methods may be added without breaking existing
functionality. When we decide that want to drop some existing
class/methods, we first mark it with
[https://code.google.com/p/chromium/codesearch#search/&q=V8_DEPRECATED&sq=package:chromium&type=cs
V8_DEPRECATED] macro which will cause compile time warnings when the
deprecated methods are called by the embedder. We keep deprecated method
for one branch and then remove it. E.g. if v8::CpuProfiler::FindCpuProfile
was plain non deprecated in 3.17 branch, marked as V8_DEPRECATED in 3.18,
it may well be removed in 3.19 branch.
+
+
== GUI and IDE Access ==
This project's Subversion repository may be accessed using many different
client programs and plug-ins. See your client's documentation for more
information.
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
