<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<br>
<div id="smartTemplate4-template">Hello!<br>
<br>
I would like to discuss which policy we want to recommend for the
versioning, branching and tagging for FUEL plugins and how it
should correlate with FUEL/MOS versions/releases.<br>
According <a
href="http://docs.mirantis.com/openstack/fuel/fuel-6.0/plugin-dev.html#metadata-yaml">Fuel
Plug-in Guide</a> we recommend to use the following standard <a
href="http://semver.org/">(</a><a class="reference external"
href="http://semver.org/" style="box-sizing: border-box; color:
rgb(211, 47, 26); text-decoration: none; font-family: 'PT Sans',
arial, sans-serif; font-size: 15px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: 22.5px; orphans: auto; text-align: justify;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Semantic Versioning 2.0.0</a><span
style="color: rgb(65, 69, 77); font-family: 'PT Sans', arial,
sans-serif; font-size: 15px; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal;
line-height: 22.5px; orphans: auto; text-align: justify;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
display: inline !important; float: none; background-color:
rgb(255, 255, 255);"></span><a href="http://semver.org/">)</a>
for the plugin versioning. IMO, it is a good idea, because in this
case we have independent development process and release cycle
from the FUEL/MOS. But very often we will need to find out which
versions of FUEL/MOS is supported by each version of plugin and
vice versa. Of course, we can checkout each version and look into
metadata.yaml which contain a list of supported releases of
FUEL/MOS, but it is not very convenient. For this purpose we can
store this list in the commit message for each tag. It is allow us
very quick and easily to get dependencies between plugin versions
and FUEL/MOS releases, usging simple command: <b>git tag -n10</b>.
It also will be very convenient for the CI process.<br>
<br>
What do you think about it?<br>
<br>
<br>
<i>Thanks and Best Regards,<br>
Andrey.</i><br>
</div>
</body>
</html>