<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Heya all,<br>
<br>
Borun here, almost complete outsider on this project, so correct me
if I make any wrong assumptions.<br>
<br>
I guess the build tags are made by the continuous integration
infrastructure and that no significant maintenance is required to
keep the mechanism that creates them there in place. Thus, if the
tags are a burden to some (because there are so many of them) but
useful to others, why not simply have two public repositories, one
with the build tags and another without? (I'd keep the 'main', i.e.
development repository clear of the build tags and have the
continuous build process sync (fetch) the commits over to a 'build'
repository (a clone of 'main') where it also tags the commits it
builds, instead of tagging them on the on the 'main' repository as
it seems to do today.)<br>
<br>
That way, the 'conversion tool' comes practically for free, has a
web interface already familiar to those involved <b>and</b> is
machine readable.<br>
<br>
Tags of wider interest (e.g. to mark versions that are official
releases) would probably still be made on the 'main' repo and then
fetched to the 'build' repo.<br>
<br>
Cheers,<br>
B.<br>
</body>
</html>