[ceph.git] / ceph / src / boost / libs / phoenix / doc / html / phoenix / maintenance / my_understanding_of_how_maintenance_works.html

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>My Understanding of how maintenance works</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../index.html" title="Chapter&#160;1.&#160;Phoenix 3.2.0">
<link rel="up" href="../maintenance.html" title="Maintenance">
<link rel="prev" href="background.html" title="Background">
<link rel="next" href="method_in_use.html" title="Method in use">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center"><a href="../../../../../../index.html">Home</a></td>
<td align="center"><a href="../../../../../../libs/libraries.htm">Libraries</a></td>
<td align="center"><a href="http://www.boost.org/users/people.html">People</a></td>
<td align="center"><a href="http://www.boost.org/users/faq.html">FAQ</a></td>
<td align="center"><a href="../../../../../../more/index.htm">More</a></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="background.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../maintenance.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="method_in_use.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="phoenix.maintenance.my_understanding_of_how_maintenance_works"></a><a class="link" href="my_understanding_of_how_maintenance_works.html" title="My Understanding of how maintenance works">My
      Understanding of how maintenance works</a>
</h3></div></div></div>
<p>
        There has been some discussion on the mailing list of how best to get patches
        available to users of libraries. This is the understanding I have been using.
        I posted this and have had no comments on it.
      </p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
            Maintainers can have write access to the particular library for which
            they have responsibility. This includes all the branches and in particular
            both develop and master.
          </li>
<li class="listitem">
            It is up to the maintainer to put patches and tests onto develop and
            see whether there are any remaining problems.
          </li>
<li class="listitem">
            It is then up to the maintainer to move the patches and tests from develop
            to master.
            <div class="itemizedlist"><ul class="itemizedlist" type="circle">
<li class="listitem">
                  This does not have to wait for a release of Boost.
                </li>
<li class="listitem">
                  It can be done any time and at some point master will then become
                  the next release.
                </li>
</ul></div>
          </li>
<li class="listitem">
            I do not think that develop is moved to master in any other way. It is
            the maintainer who will know when that is the correct action.
          </li>
</ul></div>
<p>
        If there is more than one maintainer then any of them can do this. Each will
        be able to see what has happened from the git log.
      </p>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
<td align="right"><div class="copyright-footer">Copyright &#169; 2002-2005, 2010, 2014, 2015 Joel de Guzman, Dan Marsden, Thomas
      Heller, John Fletcher<p>
        Distributed under the Boost Software License, Version 1.0. (See accompanying
        file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
      </p>
</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="background.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../maintenance.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="method_in_use.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>
Commit	Line	Data
7c673cae FG	1	<html>
	2	<head>
	3	<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
	4	<title>My Understanding of how maintenance works</title>
	5	<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
	6	<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
	7	<link rel="home" href="../../index.html" title="Chapter 1. Phoenix 3.2.0">
	8	<link rel="up" href="../maintenance.html" title="Maintenance">
	9	<link rel="prev" href="background.html" title="Background">
	10	<link rel="next" href="method_in_use.html" title="Method in use">
	11	</head>
	12	<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
	13	<table cellpadding="2" width="100%"><tr>
	14	<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
	15	<td align="center"><a href="../../../../../../index.html">Home</a></td>
	16	<td align="center"><a href="../../../../../../libs/libraries.htm">Libraries</a></td>
	17	<td align="center"><a href="http://www.boost.org/users/people.html">People</a></td>
	18	<td align="center"><a href="http://www.boost.org/users/faq.html">FAQ</a></td>
	19	<td align="center"><a href="../../../../../../more/index.htm">More</a></td>
	20	</tr></table>
	21	<hr>
	22	<div class="spirit-nav">
	23	<a accesskey="p" href="background.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../maintenance.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="method_in_use.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
	24	</div>
	25	<div class="section">
	26	<div class="titlepage"><div><div><h3 class="title">
	27	<a name="phoenix.maintenance.my_understanding_of_how_maintenance_works"></a><a class="link" href="my_understanding_of_how_maintenance_works.html" title="My Understanding of how maintenance works">My
	28	Understanding of how maintenance works</a>
	29	</h3></div></div></div>
	30	<p>
	31	There has been some discussion on the mailing list of how best to get patches
	32	available to users of libraries. This is the understanding I have been using.
	33	I posted this and have had no comments on it.
	34	</p>
	35	<div class="itemizedlist"><ul class="itemizedlist" type="disc">
	36	<li class="listitem">
	37	Maintainers can have write access to the particular library for which
	38	they have responsibility. This includes all the branches and in particular
	39	both develop and master.
	40	</li>
	41	<li class="listitem">
	42	It is up to the maintainer to put patches and tests onto develop and
	43	see whether there are any remaining problems.
	44	</li>
	45	<li class="listitem">
	46	It is then up to the maintainer to move the patches and tests from develop
	47	to master.
	48	<div class="itemizedlist"><ul class="itemizedlist" type="circle">
	49	<li class="listitem">
	50	This does not have to wait for a release of Boost.
	51	</li>
	52	<li class="listitem">
	53	It can be done any time and at some point master will then become
	54	the next release.
	55	</li>
	56	</ul></div>
	57	</li>
	58	<li class="listitem">
	59	I do not think that develop is moved to master in any other way. It is
	60	the maintainer who will know when that is the correct action.
	61	</li>
	62	</ul></div>
	63	<p>
	64	If there is more than one maintainer then any of them can do this. Each will
65	be able to see what has happened from the git log.
66	</p>
67	</div>
68	<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
69	<td align="left"></td>
70	<td align="right"><div class="copyright-footer">Copyright © 2002-2005, 2010, 2014, 2015 Joel de Guzman, Dan Marsden, Thomas
71	Heller, John Fletcher<p>
72	Distributed under the Boost Software License, Version 1.0. (See accompanying
73	file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
74	</p>
75	</div></td>
76	</tr></table>
77	<hr>
78	<div class="spirit-nav">
79	<a accesskey="p" href="background.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../maintenance.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="method_in_use.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
80	</div>
81	</body>
82	</html>