https://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692017-04-25T06:51:46ZOpen-Source ProjectsKlever - Feature #6712: Specify Django versionhttps://forge.ispras.ru/issues/6712?journal_id=302492017-04-25T06:51:46ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul><p>Let's shed light on this at last. It will be much better if everybody will be bound to use some particular version of Django rather than rely upon a variety of them should behave properly and in the same way.</p> Klever - Feature #6712: Specify Django versionhttps://forge.ispras.ru/issues/6712?journal_id=306502017-06-22T18:37:33ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li><li><strong>Assignee</strong> deleted (<del><i>Vladimir Gratinskiy</i></del>)</li><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>High</i></li></ul><p>Eventually I consider this issue strange since similar requirements should be specified for all used libraries and tools but there aren't corresponding feature requests.</p> Klever - Feature #6712: Specify Django versionhttps://forge.ispras.ru/issues/6712?journal_id=359182019-04-02T07:10:48ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Subject</strong> changed from <i>Minimal and maximum version of Django</i> to <i>Specify Django version</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/35918/diff?detail_id=40633">diff</a>)</li><li><strong>Category</strong> changed from <i>Documentation</i> to <i>Deployment</i></li><li><strong>Status</strong> changed from <i>Rejected</i> to <i>Open</i></li><li><strong>Assignee</strong> set to <i>Evgeny Novikov</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Immediate</i></li><li><strong>Target version</strong> set to <i>3.0</i></li></ul><p>I re-opened the issue as yesterday Django 2.2 was released and at least Bridge migrations started to fail with it. Everybody, let's use Django 2.1.7 that definitely works until explicit update of supported version in Bridge.</p> Klever - Feature #6712: Specify Django versionhttps://forge.ispras.ru/issues/6712?journal_id=359202019-04-02T07:14:16ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Resolved</i></li></ul><p>I fixed this in branch <em>deploy-linux-3.14-build-base</em>.</p> Klever - Feature #6712: Specify Django versionhttps://forge.ispras.ru/issues/6712?journal_id=359232019-04-02T09:10:54ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul><p>Tests passed, so, I merged the branch to master in commmit:afaaf5f.</p>
<p><a class="user active user-mention" href="https://forge.ispras.ru/users/506">@Vladimir Gratinskiy</a>, please, update Bridge to new versions of Django in separate branches and via explicit new features at Forge.</p>