<html>#2736: consider using git+https together with a branch name or kuibit install
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>trivial</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Other</td></tr>
</table>
<p>Each ET release is tied to a specific kuibit version and <span class="ap-mention" data-atlassian-id="557058:4b0c8315-696b-4d2e-92da-2da5fea9e8d4">@Gabriele Bozzola</span> allows the ET to create branches and tags in kuibit. Yet to then install kuibit the instruction in the ET use numeric version numbers <code>1.4.0</code> or so and thus a code which may not actually match up with the ET branch <code>ET_YYYY_MM</code> of any release (unless special care is taken by the release coordinator to create a release branch of the version (tag) that will be used for the release).</p>
<p>It may be interesting to consider instead to use:</p>
<div class="codehilite language-shell"><pre><span></span>pip install git+https://github.com/Sbozzolo/kuibit@ET_2023_05
</pre></div>
<p>instead. At least from the point of view of consistent ET versions. The downside of course being that this probably breaks pip’s logic to compare newer versions and may inundate kuibit’s bug tracker with version numbers that are really ET versions and not kuibit version.s</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2736/consider-using-git-https-together-with-a'>https://bitbucket.org/einsteintoolkit/tickets/issues/2736/consider-using-git-https-together-with-a</a></p>
</html>