Skip to content
Browse files

Initial new website in sphinx

  • Loading branch information...
0 parents commit 326e99958a86a3ba10e347892a19b21b1bb48255 @beberlei beberlei committed
2 .gitignore
@@ -0,0 +1,2 @@
+pages/build
+*.pyc
4 README.md
@@ -0,0 +1,4 @@
+# Doctrine-Project.org Website
+
+We built our complete website with Sphinx, which includes some sophisticated plugins that generate
+project details and hooks into Github.
130 pages/Makefile
@@ -0,0 +1,130 @@
+# Makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line.
+SPHINXOPTS =
+SPHINXBUILD = sphinx-build
+PAPER =
+BUILDDIR = build
+
+# Internal variables.
+PAPEROPT_a4 = -D latex_paper_size=a4
+PAPEROPT_letter = -D latex_paper_size=letter
+ALLSPHINXOPTS = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
+
+.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest
+
+help:
+ @echo "Please use \`make <target>' where <target> is one of"
+ @echo " html to make standalone HTML files"
+ @echo " dirhtml to make HTML files named index.html in directories"
+ @echo " singlehtml to make a single large HTML file"
+ @echo " pickle to make pickle files"
+ @echo " json to make JSON files"
+ @echo " htmlhelp to make HTML files and a HTML help project"
+ @echo " qthelp to make HTML files and a qthelp project"
+ @echo " devhelp to make HTML files and a Devhelp project"
+ @echo " epub to make an epub"
+ @echo " latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
+ @echo " latexpdf to make LaTeX files and run them through pdflatex"
+ @echo " text to make text files"
+ @echo " man to make manual pages"
+ @echo " changes to make an overview of all changed/added/deprecated items"
+ @echo " linkcheck to check all external links for integrity"
+ @echo " doctest to run all doctests embedded in the documentation (if enabled)"
+
+clean:
+ -rm -rf $(BUILDDIR)/*
+
+html:
+ $(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
+ @echo
+ @echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
+
+dirhtml:
+ $(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
+ @echo
+ @echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
+
+singlehtml:
+ $(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
+ @echo
+ @echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
+
+pickle:
+ $(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
+ @echo
+ @echo "Build finished; now you can process the pickle files."
+
+json:
+ $(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
+ @echo
+ @echo "Build finished; now you can process the JSON files."
+
+htmlhelp:
+ $(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
+ @echo
+ @echo "Build finished; now you can run HTML Help Workshop with the" \
+ ".hhp project file in $(BUILDDIR)/htmlhelp."
+
+qthelp:
+ $(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
+ @echo
+ @echo "Build finished; now you can run "qcollectiongenerator" with the" \
+ ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
+ @echo "# qcollectiongenerator $(BUILDDIR)/qthelp/Doctrine-Projectorg.qhcp"
+ @echo "To view the help file:"
+ @echo "# assistant -collectionFile $(BUILDDIR)/qthelp/Doctrine-Projectorg.qhc"
+
+devhelp:
+ $(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
+ @echo
+ @echo "Build finished."
+ @echo "To view the help file:"
+ @echo "# mkdir -p $$HOME/.local/share/devhelp/Doctrine-Projectorg"
+ @echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/Doctrine-Projectorg"
+ @echo "# devhelp"
+
+epub:
+ $(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
+ @echo
+ @echo "Build finished. The epub file is in $(BUILDDIR)/epub."
+
+latex:
+ $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+ @echo
+ @echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
+ @echo "Run \`make' in that directory to run these through (pdf)latex" \
+ "(use \`make latexpdf' here to do that automatically)."
+
+latexpdf:
+ $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+ @echo "Running LaTeX files through pdflatex..."
+ make -C $(BUILDDIR)/latex all-pdf
+ @echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
+
+text:
+ $(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
+ @echo
+ @echo "Build finished. The text files are in $(BUILDDIR)/text."
+
+man:
+ $(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
+ @echo
+ @echo "Build finished. The manual pages are in $(BUILDDIR)/man."
+
+changes:
+ $(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
+ @echo
+ @echo "The overview file is in $(BUILDDIR)/changes."
+
+linkcheck:
+ $(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
+ @echo
+ @echo "Link check complete; look for any errors in the above output " \
+ "or in $(BUILDDIR)/linkcheck/output.txt."
+
+doctest:
+ $(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
+ @echo "Testing of doctests in the sources finished, look at the " \
+ "results in $(BUILDDIR)/doctest/output.txt."
155 pages/make.bat
@@ -0,0 +1,155 @@
+@ECHO OFF
+
+REM Command file for Sphinx documentation
+
+if "%SPHINXBUILD%" == "" (
+ set SPHINXBUILD=sphinx-build
+)
+set BUILDDIR=build
+set ALLSPHINXOPTS=-d %BUILDDIR%/doctrees %SPHINXOPTS% source
+if NOT "%PAPER%" == "" (
+ set ALLSPHINXOPTS=-D latex_paper_size=%PAPER% %ALLSPHINXOPTS%
+)
+
+if "%1" == "" goto help
+
+if "%1" == "help" (
+ :help
+ echo.Please use `make ^<target^>` where ^<target^> is one of
+ echo. html to make standalone HTML files
+ echo. dirhtml to make HTML files named index.html in directories
+ echo. singlehtml to make a single large HTML file
+ echo. pickle to make pickle files
+ echo. json to make JSON files
+ echo. htmlhelp to make HTML files and a HTML help project
+ echo. qthelp to make HTML files and a qthelp project
+ echo. devhelp to make HTML files and a Devhelp project
+ echo. epub to make an epub
+ echo. latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter
+ echo. text to make text files
+ echo. man to make manual pages
+ echo. changes to make an overview over all changed/added/deprecated items
+ echo. linkcheck to check all external links for integrity
+ echo. doctest to run all doctests embedded in the documentation if enabled
+ goto end
+)
+
+if "%1" == "clean" (
+ for /d %%i in (%BUILDDIR%\*) do rmdir /q /s %%i
+ del /q /s %BUILDDIR%\*
+ goto end
+)
+
+if "%1" == "html" (
+ %SPHINXBUILD% -b html %ALLSPHINXOPTS% %BUILDDIR%/html
+ echo.
+ echo.Build finished. The HTML pages are in %BUILDDIR%/html.
+ goto end
+)
+
+if "%1" == "dirhtml" (
+ %SPHINXBUILD% -b dirhtml %ALLSPHINXOPTS% %BUILDDIR%/dirhtml
+ echo.
+ echo.Build finished. The HTML pages are in %BUILDDIR%/dirhtml.
+ goto end
+)
+
+if "%1" == "singlehtml" (
+ %SPHINXBUILD% -b singlehtml %ALLSPHINXOPTS% %BUILDDIR%/singlehtml
+ echo.
+ echo.Build finished. The HTML pages are in %BUILDDIR%/singlehtml.
+ goto end
+)
+
+if "%1" == "pickle" (
+ %SPHINXBUILD% -b pickle %ALLSPHINXOPTS% %BUILDDIR%/pickle
+ echo.
+ echo.Build finished; now you can process the pickle files.
+ goto end
+)
+
+if "%1" == "json" (
+ %SPHINXBUILD% -b json %ALLSPHINXOPTS% %BUILDDIR%/json
+ echo.
+ echo.Build finished; now you can process the JSON files.
+ goto end
+)
+
+if "%1" == "htmlhelp" (
+ %SPHINXBUILD% -b htmlhelp %ALLSPHINXOPTS% %BUILDDIR%/htmlhelp
+ echo.
+ echo.Build finished; now you can run HTML Help Workshop with the ^
+.hhp project file in %BUILDDIR%/htmlhelp.
+ goto end
+)
+
+if "%1" == "qthelp" (
+ %SPHINXBUILD% -b qthelp %ALLSPHINXOPTS% %BUILDDIR%/qthelp
+ echo.
+ echo.Build finished; now you can run "qcollectiongenerator" with the ^
+.qhcp project file in %BUILDDIR%/qthelp, like this:
+ echo.^> qcollectiongenerator %BUILDDIR%\qthelp\Doctrine-Projectorg.qhcp
+ echo.To view the help file:
+ echo.^> assistant -collectionFile %BUILDDIR%\qthelp\Doctrine-Projectorg.ghc
+ goto end
+)
+
+if "%1" == "devhelp" (
+ %SPHINXBUILD% -b devhelp %ALLSPHINXOPTS% %BUILDDIR%/devhelp
+ echo.
+ echo.Build finished.
+ goto end
+)
+
+if "%1" == "epub" (
+ %SPHINXBUILD% -b epub %ALLSPHINXOPTS% %BUILDDIR%/epub
+ echo.
+ echo.Build finished. The epub file is in %BUILDDIR%/epub.
+ goto end
+)
+
+if "%1" == "latex" (
+ %SPHINXBUILD% -b latex %ALLSPHINXOPTS% %BUILDDIR%/latex
+ echo.
+ echo.Build finished; the LaTeX files are in %BUILDDIR%/latex.
+ goto end
+)
+
+if "%1" == "text" (
+ %SPHINXBUILD% -b text %ALLSPHINXOPTS% %BUILDDIR%/text
+ echo.
+ echo.Build finished. The text files are in %BUILDDIR%/text.
+ goto end
+)
+
+if "%1" == "man" (
+ %SPHINXBUILD% -b man %ALLSPHINXOPTS% %BUILDDIR%/man
+ echo.
+ echo.Build finished. The manual pages are in %BUILDDIR%/man.
+ goto end
+)
+
+if "%1" == "changes" (
+ %SPHINXBUILD% -b changes %ALLSPHINXOPTS% %BUILDDIR%/changes
+ echo.
+ echo.The overview file is in %BUILDDIR%/changes.
+ goto end
+)
+
+if "%1" == "linkcheck" (
+ %SPHINXBUILD% -b linkcheck %ALLSPHINXOPTS% %BUILDDIR%/linkcheck
+ echo.
+ echo.Link check complete; look for any errors in the above output ^
+or in %BUILDDIR%/linkcheck/output.txt.
+ goto end
+)
+
+if "%1" == "doctest" (
+ %SPHINXBUILD% -b doctest %ALLSPHINXOPTS% %BUILDDIR%/doctest
+ echo.
+ echo.Testing of doctests in the sources finished, look at the ^
+results in %BUILDDIR%/doctest/output.txt.
+ goto end
+)
+
+:end
113 pages/source/_exts/doctrinedownloads.py
@@ -0,0 +1,113 @@
+from docutils.parsers.rst import Directive, directives
+from docutils import nodes, utils
+from string import upper
+import os;
+from yaml import load as yaml_load
+try:
+ from yaml import CLoader as Loader, CDumper as Dumper
+except ImportError:
+ from yaml import Loader, Dumper
+
+class doctrinedownloads(nodes.General, nodes.Element):
+ pass
+
+class DoctrineDownloads(Directive):
+ required_arguments = 0
+ optional_arguments = 0
+ has_content = True
+ option_spec = {
+ 'file': directives.path,
+ 'project': directives.unchanged # shortname of the project
+ }
+
+ def run(self):
+ """
+ Implements the directive
+ """
+ # Get content and options
+ file_path = self.options.get('file', None)
+ project = self.options.get('project', 'top')
+
+ if not file_path:
+ return [self._report('file_path -option missing')]
+
+ projects = yaml_load(open(self._get_directive_path(file_path)).read())
+
+ ret = []
+ for p in projects:
+ if (p == project):
+ project = projects[project]
+ node = doctrinedownloads()
+ node['project'] = project
+ ret.append(node)
+
+ return ret
+
+ def _get_directive_path(self, path):
+ """
+ Returns transformed path from the directive
+ option/content
+ """
+ source = self.state_machine.input_lines.source(
+ self.lineno - self.state_machine.input_offset - 1)
+ source_dir = os.path.dirname(os.path.abspath(source))
+ path = os.path.normpath(os.path.join(source_dir, path))
+
+ return utils.relative_path(None, path)
+
+def visit_doctrinedownloads_html(self, node):
+ self.body.append(self.starttag(node, 'div', CLASS='project'))
+
+ self.body.append('<p>%s</p>' % node['project']['description']);
+
+ self.body.append('<ul>')
+ self.body.append('<li><a href="%s">Issues</a></li>\n' % (node['project']['issues_link']) )
+ self.body.append('<li><a href="/projects/%s/current/docs/en">Documentation</a></li>\n' % (node['project']['slug']) )
+ self.body.append('<li><a href="%s">Browse Source</a></li>\n' % (node['project']['browse_source_link']) )
+ self.body.append('</ul>')
+
+ for version in node['project']['versions']:
+ self.body.append(self.starttag(node, 'div', CLASS='version'))
+ versiondata = node['project']['versions'][version];
+
+ self.body.append('<h3>Download %s (%s)</h3>' % ( version, versiondata['stability'] ))
+
+ self.body.append('<div class="releases">')
+ for release in versiondata['releases']:
+ releasedata = versiondata['releases'][release]
+
+ self.body.append('<h4>%s</h4>' % release)
+
+ self.body.append('<ul class="release">');
+ if 'package_name' in releasedata:
+ self.body.append('<li><a href="http://www.doctrine-project.org/downloads/%s">Download Archive</a></li>' % (releasedata['package_name']))
+
+ if 'svn_checkout_command' in releasedata:
+ self.body.append('<li><strong>Checkout from Subversion:</strong> <pre>%s</pre></li>' % (releasedata['svn_checkout_command']))
+
+ if 'git_checkout_command' in releasedata:
+ self.body.append('<li><strong>Checkout from Git:</strong> <pre>%s</pre></li>' % (releasedata['git_checkout_command']))
+
+ if 'pear_install_command' in releasedata:
+ self.body.append('<li><strong>Install via PEAR:</strong> <pre>%s</pre></li>' % (releasedata['pear_install_command']))
+
+ self.body.append('</ul>');
+
+ self.body.append('</div>')
+
+ raise nodes.SkipNode
+
+def depart_doctrinedownloads_html(self, node):
+ self.body.append('</div>\n')
+
+def visit_doctrinedownloads_latex(self, node):
+ pass
+
+def depart_doctrinedownloads_latex(self, node):
+ pass
+
+def setup(app):
+ app.add_node(doctrinedownloads,
+ html=(visit_doctrinedownloads_html, depart_doctrinedownloads_html),
+ latex=(visit_doctrinedownloads_latex, depart_doctrinedownloads_latex))
+ app.add_directive('doctrine-downloads', DoctrineDownloads)
85 pages/source/_exts/doctrineprojects.py
@@ -0,0 +1,85 @@
+from docutils.parsers.rst import Directive, directives
+from docutils import nodes, utils
+from string import upper
+import os;
+from yaml import load as yaml_load
+try:
+ from yaml import CLoader as Loader, CDumper as Dumper
+except ImportError:
+ from yaml import Loader, Dumper
+
+class doctrineprojects(nodes.General, nodes.Element):
+ pass
+
+class DoctrineProjects(Directive):
+ required_arguments = 0
+ optional_arguments = 0
+ has_content = True
+ option_spec = {
+ 'file': directives.path,
+ 'type': directives.unchanged # 'top' -> all toplevel projects, 'all' -> all projects
+ }
+
+ def run(self):
+ """
+ Implements the directive
+ """
+ # Get content and options
+ file_path = self.options.get('file', None)
+ type = self.options.get('type', 'top')
+
+ if not file_path:
+ return [self._report('file_path -option missing')]
+
+ projects = yaml_load(open(self._get_directive_path(file_path)).read())
+
+ ret = []
+ for project in projects:
+ project = projects[project]
+
+ if type == 'top' and project['is_primary'] == False:
+ continue
+
+ node = doctrineprojects()
+ node['project'] = project
+ ret.append(node)
+
+ return ret
+
+ def _get_directive_path(self, path):
+ """
+ Returns transformed path from the directive
+ option/content
+ """
+ source = self.state_machine.input_lines.source(
+ self.lineno - self.state_machine.input_offset - 1)
+ source_dir = os.path.dirname(os.path.abspath(source))
+ path = os.path.normpath(os.path.join(source_dir, path))
+
+ return utils.relative_path(None, path)
+
+def visit_doctrineprojects_html(self, node):
+ self.body.append('<li class="project" id="%s"><h3><a href="/projects/%s.html">%s</a></h3>\n' % (node['project']['slug'], node['project']['slug'], node['project']['title']) )
+ self.body.append('<p>%s</p>' % (node['project']['description']) )
+ self.body.append('<ul>\n')
+ self.body.append('<li><a href="%s">Issues</a></li>\n' % (node['project']['issues_link']) )
+ self.body.append('<li><a href="/projects/%s/current/docs/en">Documentation</a></li>\n' % (node['project']['slug']) )
+ self.body.append('<li><a href="/projects/%s.html">Download</a></li>\n' % (node['project']['slug']) )
+ self.body.append('<li><a href="%s">Browse Source</a></li>\n' % (node['project']['browse_source_link']) )
+ self.body.append('</ul></li>')
+ raise nodes.SkipNode
+
+def depart_doctrineprojects_html(self, node):
+ self.body.append('</div>\n')
+
+def visit_doctrineprojects_latex(self, node):
+ pass
+
+def depart_doctrineprojects_latex(self, node):
+ pass
+
+def setup(app):
+ app.add_node(doctrineprojects,
+ html=(visit_doctrineprojects_html, depart_doctrineprojects_html),
+ latex=(visit_doctrineprojects_latex, depart_doctrineprojects_latex))
+ app.add_directive('doctrine-projects', DoctrineProjects)
83 pages/source/about.rst
@@ -0,0 +1,83 @@
+About
+=====
+
+The Doctrine Project is the home of a selected set of PHP libraries primarily focused on providing persistence services and related functionality.
+
+Core Team
+---------
+
+Jonathan H. Wage Developer
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+Documentation, Project Manager, Website
+
+Jonathan is a software developer who currently lives in Nashville, TN. He joined the Doctrine project as a contributor in early 2007 and has been involved in one way or another since. Jonathan currently works full-time as a software developer at ShopOpenSky, a social commerce platform that uses the Doctrine MongoDB ODM.
+
+It all began at the age of 12 when he first got his hands on the tools to build his first website. From then on he hopped from one thing to another learning the various aspects of programming in several different languages. He enjoys working on Doctrine as it is a daily challenge and allows him to explore uncharted territories in PHP.
+
+jonwage@gmail.com
+
+Guilherme Blanco
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Developer, Documentation
+
+Guilherme Blanco was born in 09/19/1983 and lives in Brazil. He has a bachelors degree in Computer Science from the Federal University of São Carlos and works in the web development industry. He is currently employed by his company named Bisna and holds a blog at http://blog.bisna.com.
+
+He has worked with Java, .NET and the majority of server/client side languages and decided to pick PHP as his default development language. Instead of reinventing the wheel after he planned an entire ORM tool, he decided to jump on board the Doctrine project in November of 2007 and put his efforts in to help it move forward.
+
+He also enjoys watching movies and playing Age of Empires in his spare time. guilhermeblanco@hotmail.com
+
+Benjamin Eberlei
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+ORM & DBAL Team Leader, Developer
+
+Benjamin studied economics, outgrew his profession and is now a software developer based in Bonn, Germany. He has been developing PHP applications for almost ten years and currently works for the SimpleThings GmbH.
+
+As a contributor to the Zend Framework he was the lead to propose and prototype an ORM package, which was discontinued in October 2009 in favor of a full integration with the Doctrine ORM. Since then he has become a member of the core Doctrine team, working on many parts of the second generation and planing the integration between both projects.
+
+kontakt@beberlei.de
+
+Bulat Shakirzyanov
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+MongoDB ODM Developer
+
+Bulat Shakirzyanov a.k.a. avalanche123 is software alchemist at OpenSky, member of the Doctrine Project core team, holds a black belt in test-fu, Symfony2 fan and contributor, geek and talks about himself in third person. mallluhuct@gmail.com
+
+Juozas Kaziukėnas
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Developer, Evangelist
+
+Juozas "Joe" Kaziukenas is a software developer from Edinburgh, UK, originally born in Lithuania. He has joined Doctrine Core team in November, 2010 previously working on Microsoft SQL Server support in Doctrine 2. Joe can be found speaking at various PHP conferences and working on open source projects to improve interoperability and platform independence.
+
+juozas@juokaz.com
+
+Other Contributors
+------------------
+
+* Ian P. Christian (pookey), Developer, Documentation, Hosts Website.
+
+* Fabien Potencier (fabpot), Api Documentation Code.
+
+* Lukas Smith (lsmith), Developer, Documentation.
+
+* Takeshi Amano (moksahero), Japanese translation.
+
+* Giorgio Sironi (piccoloprincipe), Development, Documentation. Doctrine 2 contributor. Contributed implementation and tests for lazy-loading in Doctrine 2.
+
+* Kris Wallsmith (kris.wallsmith), Developer, Documentation.
+
+* David Abdemoulaie (hobodave), Developer, Git Guru/Manager.
+
+* Konsta Vesterinen (zYne-), Developer, Documentation, Founder. Konsta is the founder of the Doctrine project and responsible for most of the code that makes up Doctrine 1.
+
+* Roman S. Borschel (romanb), Developer, Documentation. Roman is a software developer from Berlin, Germany who originally joined the project as a user in its early stages in 2006. These days he is mainly a Scala/Java developer with the occasional bit of .NET. His strange passion for object-relational mapping, and object persistence in general culminated in the Doctrine 2 project which he led up to the 2.0 final release in the fall of 2010.
+
+* Bjarte Stien Karlsen (bjartek), Developer, Documentation.
+
+* Janne Vanhala (jepso), Developer, Documentation. Janne Vanhala contributed the initial draft and implementation of the Doctrine 2 DQL Lexer and Parser.
+
+* Phu Son Nguyen (phuson), Web Design. Phu Son Nguyen created the design of the Doctrine website.
+
26 pages/source/community.rst
@@ -0,0 +1,26 @@
+Want to contribute?
+===================
+
+Open source software development is a battle against problems. There's no better way to be part of the team than to grab a gun and dive into the trenches. You can learn how to get started contributing by reading the contribute page.
+
+Get Involved with the Community
+-------------------------------
+
+Want to get involved with the Doctrine community? This page aims to document the different ways you can get involved with the community to help with offering support or for getting support yourself.
+Mailing Lists
+
+The primary means for communication between Doctrine users and developers are the mailing lists hosted with Google Groups:
+
+ - `Doctrine User Mailing List <http://groups.google.com/group/doctrine-user>`_
+ - `Doctrine Developers Mailing List <http://groups.google.com/group/doctrine-dev>`_
+
+IRC
+---
+
+If you prefer a more intimate and instant way of communicating with other Doctrine users and developers you can use IRC. We host our channels on the Freenode network:
+
+ - `irc.freenode.net/doctrine <irc://irc.freenode.net/doctrine>`_
+ - `irc.freenode.net/doctrine-dev <irc://irc.freenode.net/doctrine>`_
+ - `irc.freenode.net/doctrine-mongodb-odm <irc://irc.freenode.net/doctrine-mongodb-odm>`_
+
+
220 pages/source/conf.py
@@ -0,0 +1,220 @@
+# -*- coding: utf-8 -*-
+#
+# Doctrine-Project.org documentation build configuration file, created by
+# sphinx-quickstart on Tue Aug 30 22:21:19 2011.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+import sys, os
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+sys.path.append(os.path.abspath('_exts'))
+
+# -- General configuration -----------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = ['sphinx.ext.intersphinx', 'doctrineprojects', 'doctrinedownloads']
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# The suffix of source filenames.
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8-sig'
+
+# The master toctree document.
+master_doc = 'index'
+
+# General information about the project.
+project = u'Doctrine-Project.org'
+copyright = u'2011, Doctrine Project Team'
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+# The short X.Y version.
+version = '1.0'
+# The full version, including alpha/beta/rc tags.
+release = '1.0'
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#language = None
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+#today_fmt = '%B %d, %Y'
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+exclude_patterns = []
+
+# The reST default role (used for this markup: `text`) to use for all documents.
+#default_role = None
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+
+# -- Options for HTML output ---------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages. See the documentation for
+# a list of builtin themes.
+html_theme = 'default'
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further. For a list of options available for each theme, see the
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+#html_theme_path = []
+
+# The name for this set of Sphinx documents. If None, it defaults to
+# "<project> v<release> documentation".
+#html_title = None
+
+# A shorter title for the navigation bar. Default is the same as html_title.
+#html_short_title = None
+
+# The name of an image file (relative to this directory) to place at the top
+# of the sidebar.
+#html_logo = None
+
+# The name of an image file (within the static path) to use as favicon of the
+# docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32
+# pixels large.
+#html_favicon = None
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['_static']
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+#html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_domain_indices = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+#html_show_sourcelink = True
+
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
+#html_show_sphinx = True
+
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
+#html_show_copyright = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it. The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# This is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = None
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'Doctrine-Projectorgdoc'
+
+
+# -- Options for LaTeX output --------------------------------------------------
+
+# The paper size ('letter' or 'a4').
+#latex_paper_size = 'letter'
+
+# The font size ('10pt', '11pt' or '12pt').
+#latex_font_size = '10pt'
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, documentclass [howto/manual]).
+latex_documents = [
+ ('index', 'Doctrine-Projectorg.tex', u'Doctrine-Project.org Documentation',
+ u'Doctrine Project Team', 'manual'),
+]
+
+# The name of an image file (relative to this directory) to place at the top of
+# the title page.
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# If true, show page references after internal links.
+#latex_show_pagerefs = False
+
+# If true, show URL addresses after external links.
+#latex_show_urls = False
+
+# Additional stuff for the LaTeX preamble.
+#latex_preamble = ''
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_domain_indices = True
+
+
+# -- Options for manual page output --------------------------------------------
+
+# One entry per manual page. List of tuples
+# (source start file, name, description, authors, manual section).
+man_pages = [
+ ('index', 'doctrine-projectorg', u'Doctrine-Project.org Documentation',
+ [u'Doctrine Project Team'], 1)
+]
+
+
+# Example configuration for intersphinx: refer to the Python standard library.
+intersphinx_mapping = {'http://docs.python.org/': None}
600 pages/source/contribute.rst
@@ -0,0 +1,600 @@
+Introduction
+============
+
+Welcome to the Doctrine Project Contributors Guide. This
+documentation aims to document how contributors and collaborators
+should work when using git, development workflow, build process,
+dependency management, etc.
+
+About
+-----
+
+The Doctrine Project is the home of a selected set of PHP libraries
+primarily focused on providing persistence services and related
+functionality. Its prize projects are a Object Relational Mapper
+and the Database Abstraction Layer it is built on top of. You can
+view a list of all
+`projects <http://www.doctrine-project.org/projects>`_ on the
+website.
+
+Contributors vs Collaborators
+-----------------------------
+
+Before continuing you need to understand the difference between a
+contributor and a collaborator.
+
+
+- Contributor: A contributor is someone from the outside not on
+ the core development team of the project that wants to contribute
+ some changes to a project.
+- Collaborator: A collaborator is someone on the core development
+ team of the project and has commit access to the main repository of
+ the project.
+
+Continue reading to learn about the workflow for both contributors
+and collaborators.
+
+Contributor Workflow
+====================
+
+Who is a contributor?
+---------------------
+
+A contributor can be anyone! It could be you. Continue reading this
+section if you wish to get involved and contribute back to a
+Doctrine project.
+
+Initial Setup
+-------------
+
+
+- Setup a `github <http://github.com>`_ account.
+- Fork the `repository <http://github.com/doctrine/doctrine2>`_ of
+ the project you want to contribute to.
+- Clone your fork locally
+
+-
+
+::
+
+ $ git clone git@github.com:username/doctrine2.git
+
+
+- Enter the doctrine2 directory and add the **doctrine** remote
+
+-
+
+::
+
+ $ cd doctrine2
+ $ git remote add doctrine git://github.com/doctrine/doctrine2.git
+
+
+- Adjust your branch to track the doctrine master remote branch,
+ by default it'll track your origin remote's master:
+
+-
+
+::
+
+ $ git config branch.master.remote doctrine
+
+Keeping your master up-to-date!
+-------------------------------
+
+Once all this is done, you'll be able to keep your local master up
+to date with the simple command:
+
+::
+
+ $ git checkout master
+ $ git pull --rebase
+
+Alternatively, you can synchronize your master from any branch with
+the full fetch/rebase syntax:
+
+::
+
+ $ git fetch doctrine
+ $ git rebase doctrine/master master
+
+Using rebase pull will do a rebase instead of a merge, which will
+keep a linear history with no unnecessary merge commits. It'll also
+rewind, apply and then reapply your commits at the HEAD.
+
+Branching Model
+---------------
+
+The following names will be used to differentiate between the
+different repositories:
+
+
+- **doctrine** - The "official" Doctrine repository
+- **origin** - Your fork of the official repository on github
+- **local** - This will be your local clone of **origin**
+
+As a **contributor** you will push your completed **local** topic
+branch to **origin**. As a **contributor** you will pull updates
+from **doctrine**. As a **collaborator** (write-access) you will
+merge branches from contributors into **doctrine**.
+
+Primary Branches
+----------------
+
+The **doctrine** repository holds the following primary branches:
+
+
+- **doctrine/master** Development towards the next release.
+- **doctrine/release-\*** Maintenance branches of existing
+ releases.
+
+These branches exist in parallel and are defined as follows:
+
+**doctrine/master** is the branch where the source code of **HEAD**
+always reflects the latest version. Each released stable version
+will be a tagged commit in a **doctrine/release-\*** branch. Each
+released unstable version will be a tagged commit in the
+**doctrine/master** branch.
+
+ **NOTE** You should never commit to your forked **origin/master**.
+ Changes to **origin/master** will never be merged into
+ **doctrine/master**. All work must be done in a **topic branch**,
+ which are explained below.
+
+
+Topic Branches
+--------------
+
+Topic branches are for contributors to develop bug fixes, new
+features, etc. so that they can be easily merged to **master**.
+They must follow a few simple rules as listed below:
+
+
+- May branch off from: **master** or a **release-\*** branch.
+- Must merge back into: **master** and any affected **release-\***
+ branch that should get the same changes, but remember that release
+ branches usually only get bug fixes, with rare exceptions.
+- Branch naming convention: anything except **master** and
+ **release-\***. If a topic is related to a JIRA issue then the
+ branch should be named after that ticket, e.g. **DDC-588**
+
+Topic branches are used to develop new features and fix reported
+issues. When starting development of a feature, the target release
+in which this feature will be incorporated may well be unknown. The
+essence of a topic branch is that it exists as long as the feature
+is in development, but will eventually be merged back into
+**master** or a **release-\*** branch (to add the new feature or
+bugfix to a next release) or discarded (in case of a disappointing
+experiment).
+
+Topic branches should exist in your **local** and **origin**
+repositories only, there is no need for them to exist in
+**doctrine**.
+
+Working on topic branches
+-------------------------
+
+First create an appropriately named branch. When starting work on a
+new topic, branch off from **doctrine/master** or a
+**doctrine/release-\*** branch:
+
+::
+
+ $ git checkout -b DDC-588 doctrine/master
+ Switched to a new branch "DDC-588"
+
+Now do some work, make some changes then commit them:
+
+::
+
+ $ git status
+ $ git commit <filespec>
+
+Next, merge or rebase your commit against **doctrine/master**. With
+your work done in a **local** topic branch, you'll want to assist
+upstream merge by rebasing your commits. You can either do this
+manually with ``fetch`` then ``rebase``, or use the
+``pull --rebase`` shortcut. You may encounter merge conflicts,
+which you should fix and then mark as fixed with ``add``, and then
+continue rebasing with ``rebase --continue``. At any stage, you can
+abort the rebase with ``rebase --abort`` unlike nasty merges which
+will leave files strewn everywhere.
+
+ **CAUTION** Please note that once you have pushed your branch
+ remotely you MUST NOT rebase!
+
+
+::
+
+ $ git fetch doctrine
+ $ git rebase doctrine/master DDC-588
+
+or (uses tracking branch shortcuts):
+
+::
+
+ $ git pull --rebase
+
+ **CAUTION** You must not rebase if you have pushed your branch to
+ **origin**.
+
+
+If you need to pull master into your branch after it has already
+been pushed remotely, simply use:
+
+::
+
+ $ git pull
+
+Push your branch to **origin**:
+
+Finished topic branches should be pushed to **origin** for a
+**collaborator** to review and pull into **doctrine** as
+appropriate:
+
+::
+
+ $ git push origin DDC-588
+ To git@github.com:hobodave/doctrine2.git
+ * [new branch] DDC-588 -> DDC-588</pre>
+
+Now you are read to send a pull request from this branch, and
+update JIRA, to let a collaborator know your branch can be merged.
+
+Topic Branch Cleanup
+--------------------
+
+Once your work has been merged by the branch maintainer, it will no
+longer be necessary to keep the local branch or remote branch, so
+you can remove them!
+
+Sync your local master:
+
+::
+
+ $ git checkout master
+ $ git pull --rebase
+
+Remove your local branch using -d to ensure that it has been merged
+by upstream. Branch -d will not delete a branch that is not an
+ancestor of your current head.
+
+From the git-branch man page:
+
+
+.. raw:: html
+
+ <pre>
+ -d
+ Delete a branch. The branch must be fully merged in HEAD.
+ -D
+ Delete a branch irrespective of its merged status.
+ </pre>
+
+Remove your local branch:
+
+::
+
+ $ git branch -d DDC-588
+
+Remove your remote branch at **origin**:
+
+::
+
+ $ git push origin :DDC-588
+
+
+The projects under the Doctrine umbrella use
+`Phing <http://phing.info/trac>`_ to automate the process for
+building our distributable PEAR packages.
+
+Collaborator Workflow
+=====================
+
+Who is a collaborator?
+----------------------
+
+Collaborators are those who have been granted write access to the
+main repository of a project. In the example of the ORM, it would
+be this `repository <http://github.com/doctrine/doctrine2>`_. This
+repository will be referred to as **doctrine** in this document.
+
+You might want want to know how a collaborator is different from a
+contributor. The **Collaborator Workflow** is used primarily for
+the following:
+
+
+- Merging **contributor** branches into **doctrine/master** and/or
+ **doctrine/release-\*** branches.
+- Creating @release-\*@ branches.
+- Tagging released versions within **master** and **release-\***
+ branches.
+
+Setup
+-----
+
+First you must Fork the
+`repository <http://github.com/doctrine/doctrine2>`_ and clone your
+fork locally:
+
+::
+
+ $ git clone git@github.com:username/doctrine2.git doctrine2-orm
+ $ cd doctrine2-orm
+
+Fetch dependencies using git submodules:
+
+::
+
+ $ git submodule init
+ $ git submodule update
+
+Now add the **doctrine** remote for collaborators:
+
+::
+
+ $ cd doctrine2
+ $ git remote add doctrine git@github.com:doctrine/doctrine2.git
+
+Adjust your branch to track the doctrine master remote branch, by
+default it'll track your origin remote's master:
+
+::
+
+ $ git config branch.master.remote doctrine
+
+Optionally, add any additional contributor/collaborator forks,
+e.g.:
+
+::
+
+ $ git remote add romanb git://github.com/romanb/doctrine2.git
+
+Branching Model
+---------------
+
+Merging topic branches
+~~~~~~~~~~~~~~~~~~~~~~
+
+
+- Topic branches **must** merge into **master** and/or any
+ affected **release-\*** branches.
+- Merging a topic branch puts it into the *next* release, that is
+ the next release created from **master** and/or the next patch
+ release created from a specific **release-\*** branch.
+
+Steps
+^^^^^
+
+Add remote repo for contributor/collaborator, if necessary (only
+needs to be done once per collaborator):
+
+::
+
+ $ git remote add hobodave git://github.com/hobodave/doctrine2.git
+
+Fetch remote:
+
+::
+
+ $ git fetch hobodave
+
+Merge topic branch into master:
+
+::
+
+ $ git checkout master
+ Switched to branch 'master'
+ $ git merge --no-ff hobodave/DDC-588
+ Updating ea1b82a..05e9557
+ (Summary of changes)
+ $ git push doctrine master
+
+The **--no-ff** flag causes the merge to always create a new commit
+object, even if the merge could be performed with a fast-forward.
+This avoids losing information about the historical existence of a
+topic branch and groups together all commits that together added
+the topic.
+
+Release branches
+~~~~~~~~~~~~~~~~
+
+
+- May branch off from: **master**
+- Must merge back into: -
+- Branch naming convention: **release-\***
+
+Release branches are created when **master** has reached the state
+of the next major or minor release. They allow for continuous bug
+fixes and patch releases of that particular release until the
+release is no longer supported.
+
+The key moment to branch off a new release branch from **master**
+is when **master** reflects the desired state of the new release.
+
+Creating a release branch
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Release branches are created from the **master** branch. When the
+state of **master** is ready for the upcoming target version we
+branch off and give the release branch a name reflecting the target
+version number. In addition the ".0" release is tagged on the new
+release branch:
+
+::
+
+ $ git checkout -b release-2.0 doctrine/master
+ Switched to a new branch "release-2.0"
+ $ git push doctrine release-2.0
+ $ git tag -a 2.0.0
+ $ git push doctrine release-2.0
+
+This new branch may exist for a while, at least until the release
+is no longer supported. During that time, bug fixes are applied in
+this branch (in addition to the **master** branch), if it is
+affected by the same bug. Adding large new features here is
+prohibited. They must be merged into **master**, and therefore,
+wait for the next major or minor release.
+
+Project Dependencies
+====================
+
+Project dependencies between Doctrine projects are handled through
+git submodules. The code of the particular Doctrine project you
+have cloned is located under **lib/Doctrine**. The source code of
+dependencies to other projects resides under **lib/vendor**. If you
+have a local clone of a Doctrine project that you use directly and
+this project has dependencies to other (Doctrine) projects, you
+must run the following commands in order for the git submodules to
+be loaded:
+
+::
+
+ $ git submodule init
+ $ git submodule update
+
+Alternatively, consider using a packaged release from the
+`Doctrine Website <http://www.doctrine-project.org>`_ that contains
+everything you need already.
+
+Bumping Versions
+----------------
+
+To bump/upgrade a dependency version you just need to follow a few
+simple steps:
+
+::
+
+ $ cd lib/vendor/doctrine-dbal
+ $ git checkout 2.0.0BETA2
+ $ cd ../../../
+ $ git commit
+ $ git push
+
+Testing Different Versions
+--------------------------
+
+Testing another version is much the same as bumping the version
+except that you must not forget to go back to the old version when
+you're done otherwise if you git ``commit -a`` you will push the
+new version you were testing. Here is an example:
+
+::
+
+ $ cd lib/vendor/doctrine-dbal
+ $ git checkout 2.0.0BETA2
+ $ cd ../../../
+
+Now you can run the tests against the DoctrineDBAL-2.0.0BETA2
+version to test that the new version of the dependency doesn't
+break anything:
+
+::
+
+ $ cd tests
+ $ phpunit Doctrine/Tests/AllTests.php
+
+Now don't forget to change back the version after testing if you
+are not going to bump it permanently and commit it:
+
+::
+
+ cd lib/vendor/doctrine-dbal
+ git checkout 2.0.0-BETA1
+
+Checking Submodule Tag
+----------------------
+
+If you want to check what tag a submodule is currently at you can
+use something like this from the submodule root directory:
+
+::
+
+ $ cd lib/vendor/doctrine-dbal
+
+To get the status of the submodule:
+
+::
+
+ $ git submodule status
+
+Then use the SHA that is shown in the following command to show the
+name of the tag:
+
+::
+
+ $ git show-ref --tags | grep SHA
+
+Phing Build Process
+===================
+
+Prerequisites
+-------------
+
+
+- You must have PEAR installed.
+- You must have `Phing <http://phing.info/trac>`_ installed. The
+ easiest way is through
+ `pear <http://phing.info/docs/guide/stable/chapters/Setup.html#Setup.PearInstall>`_.
+- You must have the
+ `d51PearPkg2Task <http://pear.domain51.com/svn/Phing_d51PearPkg2Task/trunk/src/phing/tasks/ext/d51PearPkg2Task.php>`_
+ added to the core Phing tasks.
+- Copy the **build.properties.dev** file to **build.properties**
+ and adjust any properties to your local environment, if necessary.
+
+Building
+--------
+
+Clone the Doctrine project that you want to build and from within
+the root directory of the project (where the build.xml resides) run
+one of the following commands.
+
+::
+
+ $ git clone git://github.com/doctrine/doctrine2.git doctrine2-orm
+ $ cd doctrine2-orm
+
+As mentioned previously, Doctrine uses submodules with git to make
+sure the required dependencies are present. You can initialize
+these dependencies using the following commands:
+
+::
+
+ $ git submodule init
+ $ git submodule update
+
+Basic Build
+~~~~~~~~~~~
+
+You can simply run ``phing`` and it will build the sources that are
+packaged for distribution:
+
+::
+
+ $ phing
+
+After a successful build you will find the prepared code that will
+be packaged for distribution in the **build** directory.
+
+Distributable Archives
+~~~~~~~~~~~~~~~~~~~~~~
+
+If you want to produce a distributable PEAR archive run:
+
+::
+
+ $ phing build-packages
+
+After a successful build you will find the distributable archive(s)
+in the **dist** directory.
+
+Running Tests
+~~~~~~~~~~~~~
+
+The tests will be run automatically by most other targets but you
+can also run them directly:
+
+::
+
+ $ phing test
+
19 pages/source/index.rst
@@ -0,0 +1,19 @@
+Welcome to the Doctrine Project
+===============================
+
+The Doctrine Project is the home of a selected set of PHP libraries primarily focused
+on providing persistence services and related functionality. Its prize projects are a
+Object Relational Mapper and the Database Abstraction Layer it is built on top of.
+You can read more about the projects below or view a list of all projects.
+
+* :doc:`Projects <projects>`
+* :doc:`Contribute <contribute>`
+* :doc:`About <about>`
+* :doc:`Community <community>`
+
+.. doctrine-projects::
+ :file: projects.yml
+ :type: top
+
+
+
7 pages/source/projects.rst
@@ -0,0 +1,7 @@
+Doctrine Projects
+=================
+
+.. doctrine-projects::
+ :file: projects.yml
+ :type: all
+
383 pages/source/projects.yml
@@ -0,0 +1,383 @@
+orm:
+ slug: orm
+ title: 'Object Relational Mapper'
+ short_title: ORM
+ description: 'Object relational mapper (ORM) for PHP that sits on top of a powerful database abstraction layer (DBAL). One of its key features is the option to write database queries in a proprietary object oriented SQL dialect called Doctrine Query Language (DQL), inspired by Hibernates HQL. This provides developers with a powerful alternative to SQL that maintains flexibility without requiring unnecessary code duplication.'
+ latest_version: '2.1'
+ is_primary: true
+ issues_link: 'http://www.doctrine-project.org/jira/browse/DDC'
+ browse_source_link: 'http://github.com/doctrine/doctrine2'
+ versions:
+ '1.2':
+ stability: stable
+ upgrade_file_path: source/orm1.2/UPGRADE_TO_1_2
+ releases:
+ 1.2.0:
+ package_name: Doctrine-1.2.0.tgz
+ svn_checkout_command: 'svn co http://svn.doctrine-project.org/tags/1.2.0'
+ pear_install_command: 'pear install pear.doctrine-project.org/Doctrine-1.2.0.tgz'
+ 1.2.1:
+ package_name: Doctrine-1.2.1.tgz
+ svn_checkout_command: 'svn co http://svn.doctrine-project.org/tags/1.2.1'
+ pear_install_command: 'pear install pear.doctrine-project.org/Doctrine-1.2.1.tgz'
+ 1.2.2:
+ package_name: Doctrine-1.2.2.tgz
+ svn_checkout_command: 'svn co http://svn.doctrine-project.org/tags/1.2.2'
+ pear_install_command: 'pear install pear.doctrine-project.org/Doctrine-1.2.2.tgz'
+ 1.2.3:
+ package_name: Doctrine-1.2.3.tgz
+ svn_checkout_command: 'svn co http://svn.doctrine-project.org/tags/1.2.3'
+ pear_install_command: 'pear install pear.doctrine-project.org/Doctrine-1.2.3.tgz'
+ 1.2.4:
+ package_name: Doctrine-1.2.4.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine1.git doctrine-orm<br/>$ cd doctrine-orm<br/>$ git checkout 1.2.4'
+ pear_install_command: 'pear install pear.doctrine-project.org/Doctrine-1.2.4.tgz'
+ '2.0':
+ stability: stable
+ upgrade_file_path: source/orm2.0/UPGRADE_TO_2_0
+ releases:
+ 2.0.0-ALPHA1:
+ package_name: DoctrineORM-2.0.0-ALPHA1.tgz
+ svn_checkout_command: 'svn co http://svn.doctrine-project.org/tags/2.0.0-ALPHA1'
+ 2.0.0-ALPHA2:
+ package_name: DoctrineORM-2.0.0-ALPHA2.tgz
+ svn_checkout_command: 'svn co http://svn.doctrine-project.org/tags/2.0.0-ALPHA2'
+ 2.0.0-ALPHA3:
+ package_name: DoctrineORM-2.0.0-ALPHA3.tgz
+ svn_checkout_command: 'svn co http://svn.doctrine-project.org/tags/2.0.0-ALPHA3'
+ 2.0.0-ALPHA4:
+ package_name: DoctrineORM-2.0.0-ALPHA4.tgz
+ svn_checkout_command: 'svn co http://svn.doctrine-project.org/tags/2.0.0-ALPHA4'
+ 2.0.0BETA1:
+ package_name: DoctrineORM-2.0.0-BETA1.tgz
+ svn_checkout_command: 'svn co http://svn.doctrine-project.org/tags/2.0.0-BETA1'
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.0-BETA1'
+ 2.0.0BETA2:
+ package_name: DoctrineORM-2.0.0BETA2.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.0-BETA2<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.0BETA2'
+ 2.0.0BETA3:
+ package_name: DoctrineORM-2.0.0BETA3.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.0-BETA3<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.0BETA3'
+ 2.0.0BETA4:
+ package_name: DoctrineORM-2.0.0BETA4-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.0-BETA4<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.0BETA4'
+ 2.0.0RC1:
+ package_name: DoctrineORM-2.0.0RC1-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.0RC1<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.0RC1'
+ 2.0.0RC2:
+ package_name: DoctrineORM-2.0.0RC2-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.0RC2<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.0RC2'
+ 2.0.0:
+ package_name: DoctrineORM-2.0.0-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.0<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.0'
+ 2.0.1:
+ package_name: DoctrineORM-2.0.1-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.1<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.1'
+ 2.0.2:
+ package_name: DoctrineORM-2.0.2-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.2<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.2'
+ 2.0.3:
+ package_name: DoctrineORM-2.0.3-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.3<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.3'
+ 2.0.4:
+ package_name: DoctrineORM-2.0.4-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.4<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.4'
+ 2.0.5:
+ package_name: DoctrineORM-2.0.5-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.5<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.5'
+ 2.0.6:
+ package_name: DoctrineORM-2.0.6-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.6<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.6'
+ 2.0.7:
+ package_name: DoctrineORM-2.0.7-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.0.7<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.0.7'
+ '2.1':
+ stability: beta
+ upgrade_file_path: source/orm2.0/UPGRADE_TO_2_0
+ releases:
+ 2.1.0BETA1:
+ package_name: DoctrineORM-2.1.0BETA1-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.1.0BETA1<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.1.0BETA1-beta'
+ 2.1.0RC1:
+ package_name: DoctrineORM-2.1.0RC1-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.1.0RC1<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.1.0RC1-beta'
+ 2.1.0RC2:
+ package_name: DoctrineORM-2.1.0RC2-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.1.0RC2<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.1.0RC2-beta'
+ 2.1.0RC3:
+ package_name: DoctrineORM-2.1.0RC3-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.1.0RC3<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.1.0RC3-beta'
+ 2.1.0:
+ package_name: DoctrineORM-2.1.0-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.1.0<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.1.0'
+ 2.1.1:
+ package_name: DoctrineORM-2.1.1-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/doctrine2.git doctrine2-orm<br/>$ cd doctrine2-orm<br/>$ git checkout 2.1.1<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineORM-2.1.1'
+dbal:
+ slug: dbal
+ title: 'Database Abstraction Layer'
+ short_title: DBAL
+ description: 'Powerful database abstraction layer with many features for database schema introspection, schema management and PDO abstraction.'
+ latest_version: '2.1'
+ is_primary: true
+ issues_link: 'http://www.doctrine-project.org/jira/browse/DBAL'
+ browse_source_link: 'http://github.com/doctrine/dbal'
+ versions:
+ '2.0':
+ stability: stable
+ releases:
+ 2.0.0BETA2:
+ package_name: DoctrineDBAL-2.0.0BETA2.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.0-BETA2<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.0BETA2'
+ 2.0.0BETA3:
+ package_name: DoctrineDBAL-2.0.0BETA3.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.0-BETA3<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.0BETA3'
+ 2.0.0BETA4:
+ package_name: DoctrineDBAL-2.0.0BETA4-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.0-BETA4<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.0BETA4'
+ 2.0.0RC3:
+ package_name: DoctrineDBAL-2.0.0RC3-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.0-RC3<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.0RC3'
+ 2.0.0RC4:
+ package_name: DoctrineDBAL-2.0.0RC4-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.0-RC4<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.0RC4'
+ 2.0.0RC5:
+ package_name: DoctrineDBAL-2.0.0RC5-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.0-RC5<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.0RC5'
+ 2.0.0:
+ package_name: DoctrineDBAL-2.0.0-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.0<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.0'
+ 2.0.1:
+ package_name: DoctrineDBAL-2.0.1-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.1<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.1'
+ 2.0.2:
+ package_name: DoctrineDBAL-2.0.2-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.2<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.2'
+ 2.0.3:
+ package_name: DoctrineDBAL-2.0.3-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.3<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.3'
+ 2.0.4:
+ package_name: DoctrineDBAL-2.0.4-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.4<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.4'
+ 2.0.5:
+ package_name: DoctrineDBAL-2.0.5-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.5<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.5'
+ 2.0.6:
+ package_name: DoctrineDBAL-2.0.6-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.6<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.6'
+ 2.0.7:
+ package_name: DoctrineDBAL-2.0.7-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.7<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.7'
+ 2.0.8:
+ package_name: DoctrineDBAL-2.0.8-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.0.8<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.0.8'
+ '2.1':
+ stability: stable
+ releases:
+ 2.1.0BETA1:
+ package_name: DoctrineDBAL-2.1.0BETA1-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.1.0-BETA1<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.1.0BETA1'
+ 2.1.0RC1:
+ package_name: DoctrineDBAL-2.1.0RC1-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.1.0-RC1<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.1.0RC1'
+ 2.1.0RC2:
+ package_name: DoctrineDBAL-2.1.0RC2-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.1.0-RC2<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.1.0RC2'
+ 2.1.0:
+ package_name: DoctrineDBAL-2.1.0-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.1.0<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.1.0'
+ 2.1.1:
+ package_name: DoctrineDBAL-2.1.1-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.1.1<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.1.1'
+ 2.1.2:
+ package_name: DoctrineDBAL-2.1.2-full.tar.gz
+ git_checkout_command: 'git clone git://github.com/doctrine/dbal.git doctrine2-dbal<br/>$ cd doctrine2-dbal<br/>$ git checkout 2.1.2<br />$ git submodule update --init'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineDBAL-2.1.2'
+mongodb_odm:
+ slug: mongodb_odm
+ title: 'MongoDB Object Document Mapper'
+ short_title: MongoDBODM
+ description: 'Doctrine MongoDB Object Document Mapper is built for PHP 5.3.2+ and provides transparent persistence for PHP objects.'
+ latest_version: '1.0'
+ is_primary: false
+ namespace: Doctrine\ODM\MongoDB
+ issues_link: 'http://www.doctrine-project.org/jira/browse/MODM'
+ browse_source_link: 'http://github.com/doctrine/mongodb-odm'
+ versions:
+ '1.0':
+ stability: beta
+ releases:
+ 1.0.0ALPHA1:
+ package_name: DoctrineMongoDBODM-1.0.0ALPHA1.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/mongodb-odm.git mongodb_odm<br/>$ cd mongodb_odm<br/>$ git checkout 1.0.0ALPHA1'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineMongoDBODM-1.0.0ALPHA1'
+ 1.0.0ALPHA2:
+ package_name: DoctrineMongoDBODM-1.0.0ALPHA2.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/mongodb-odm.git mongodb_odm<br/>$ cd mongodb_odm<br/>$ git checkout 1.0.0ALPHA2'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineMongoDBODM-1.0.0ALPHA2'
+ 1.0.0BETA1:
+ package_name: DoctrineMongoDBODM-1.0.0BETA1.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/mongodb-odm.git mongodb_odm<br/>$ cd mongodb_odm<br/>$ git checkout 1.0.0BETA1'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineMongoDBODM-1.0.0BETA1'
+ 1.0.0BETA2:
+ package_name: DoctrineMongoDBODM-1.0.0BETA2.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/mongodb-odm.git mongodb_odm<br/>$ cd mongodb_odm<br/>$ git checkout 1.0.0BETA2'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineMongoDBODM-1.0.0BETA2'
+ 1.0.0BETA3:
+ package_name: DoctrineMongoDBODM-1.0.0BETA3.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/mongodb-odm.git mongodb_odm<br/>$ cd mongodb_odm<br/>$ git checkout 1.0.0BETA3'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineMongoDBODM-1.0.0BETA3'
+couchdb_odm:
+ slug: couchdb_odm
+ title: 'CouchDB Object Document Mapper'
+ short_title: CouchDBODM
+ description: 'Doctrine CouchDB Object Document Mapper is built for PHP 5.3.2+ and provides transparent persistence for PHP objects.'
+ latest_version: '1.0'
+ is_primary: false
+ issues_link: 'http://www.doctrine-project.org/jira/browse/CODM'
+ browse_source_link: 'http://github.com/doctrine/couchdb-odm'
+ namespace: Doctrine\ODM\CouchdbDB
+ versions:
+ '1.0':
+ stability: alpha
+ releases:
+ 1.0.0ALPHA1:
+ package_name: CouchDBODM-1.0.0ALPHA1.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/couchdb-odm.git mongodb_odm<br/>$ cd couchdb_odm<br/>$ git checkout 1.0.0alpha1'
+ pear_install_command: 'pear install pear.doctrine-project.org/CouchDBODM-1.0.0alpha1'
+phpcr_odm:
+ slug: phpcr_odm
+ title: 'PHPCR Object Document Mapper'
+ short_title: PHPCRODM
+ description: 'Doctrine PHPCR Object Document Mapper is built for PHP 5.3.2+ and provides transparent persistence for PHP objects.'
+ latest_version: '1.0'
+ is_primary: false
+ namespace: Doctrine\ODM\PHPCR
+ issues_link: 'http://www.doctrine-project.org/jira/browse/PHPCR'
+ browse_source_link: 'http://github.com/doctrine/phpcr-odm'
+ versions:
+ '1.0':
+ stability: alpha
+ releases: []
+migrations:
+ slug: migrations
+ title: 'Migrations'
+ short_title: Migrations
+ description: 'The Doctrine Migrations offer additional functionality on top of the database abstraction layer (DBAL) for versioning your database schema and easily deploying changes to it. It is a very easy to use and powerful tool.'
+ latest_version: '2.0'
+ is_primary: false
+ issues_link: 'http://www.doctrine-project.org/jira/browse/DMIG'
+ browse_source_link: 'http://github.com/doctrine/migrations'
+ namespace: Doctrine\DBAL\Migrations
+ versions:
+ '2.0':
+ stability: alpha
+ releases: []
+common:
+ slug: common
+ title: 'Common'
+ short_title: Common
+ description: 'The Doctrine Common project is a library that provides extensions to core PHP functionality.'
+ latest_version: '2.1'
+ is_primary: false
+ issues_link: 'http://www.doctrine-project.org/jira/browse/DCOM'
+ browse_source_link: 'http://github.com/doctrine/common'
+ versions:
+ '2.0':
+ stability: stable
+ releases:
+ 2.0.0BETA2:
+ package_name: DoctrineCommon-2.0.0BETA2.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.0.0-BETA2'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.0.0BETA2'
+ 2.0.0BETA3:
+ package_name: DoctrineCommon-2.0.0BETA3.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.0.0-BETA3'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.0.0BETA3'
+ 2.0.0BETA4:
+ package_name: DoctrineCommon-2.0.0BETA4.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.0.0-BETA4'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.0.0BETA4'
+ 2.0.0RC1:
+ package_name: DoctrineCommon-2.0.0RC1.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.0.0-RC1'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.0.0RC1'
+ 2.0.0RC2:
+ package_name: DoctrineCommon-2.0.0RC2.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.0.0-RC2'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.0.0RC2'
+ 2.0.0:
+ package_name: DoctrineCommon-2.0.0-full.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.0.0'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.0.0'
+ 2.0.1:
+ package_name: DoctrineCommon-2.0.1-full.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.0.1'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.0.1'
+ 2.0.2:
+ package_name: DoctrineCommon-2.0.2-full.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.0.2'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.0.2'
+ '2.1':
+ stability: stable
+ releases:
+ 2.1.0BETA1:
+ package_name: DoctrineCommon-2.1.0BETA1-full.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.1.0-BETA1'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.1.0BETA1'
+ 2.1.0RC1:
+ package_name: DoctrineCommon-2.1.0RC1-full.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.1.0-RC1'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.1.0RC1'
+ 2.1.0RC2:
+ package_name: DoctrineCommon-2.1.0RC2-full.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.1.0-RC2'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.1.0RC2'
+ 2.1.0:
+ package_name: DoctrineCommon-2.1.0-full.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.1.0'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.1.0'
+ 2.1.1:
+ package_name: DoctrineCommon-2.1.1-full.tgz
+ git_checkout_command: 'git clone git://github.com/doctrine/common.git doctrine2-common<br/>$ cd doctrine2-common<br/>$ git checkout 2.1.1'
+ pear_install_command: 'pear install pear.doctrine-project.org/DoctrineCommon-2.1.1'
+
6 pages/source/projects/common.rst
@@ -0,0 +1,6 @@
+Common
+======
+
+.. doctrine-downloads::
+ :file: ../projects.yml
+ :project: orm
6 pages/source/projects/couchdb_odm.rst
@@ -0,0 +1,6 @@
+Migrations
+==========
+
+.. doctrine-downloads::
+ :file: ../projects.yml
+ :project: orm
6 pages/source/projects/dbal.rst
@@ -0,0 +1,6 @@
+Database Abstraction Layer
+==========================
+
+.. doctrine-downloads::
+ :file: ../projects.yml
+ :project: orm
6 pages/source/projects/migrations.rst
@@ -0,0 +1,6 @@
+Migrations
+==========
+
+.. doctrine-downloads::
+ :file: ../projects.yml
+ :project: orm
6 pages/source/projects/mongodb_odm.rst
@@ -0,0 +1,6 @@
+Migrations
+==========
+
+.. doctrine-downloads::
+ :file: ../projects.yml
+ :project: orm
6 pages/source/projects/orm.rst
@@ -0,0 +1,6 @@
+Object Relational Mapper
+========================
+
+.. doctrine-downloads::
+ :file: ../projects.yml
+ :project: orm
6 pages/source/projects/phpcr_odm.rst
@@ -0,0 +1,6 @@
+Migrations
+==========
+
+.. doctrine-downloads::
+ :file: ../projects.yml
+ :project: orm

0 comments on commit 326e999

Please sign in to comment.
Something went wrong with that request. Please try again.