RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042016-04-07T15:38:27ZRhodeCode - issues
Redmine RhodeCode CE/EE - Task #3454 (Feedback): [ce/ee] visually differentiate the two editionshttps://issues.rhodecode.com/issues/34542016-04-07T15:38:27ZOliver Strobeloliver@rhodecode.com
<p>Currently we are only changing the footer to include Community vs. Enterprise differentiation.</p>
<p>Purpose: It should be possible to tell the difference in edition quickly when switching between CE/EE tabs.</p>
<p>Potential solutions:<br>
1) Add the edition name into the header after the logo on the top left<br>
2) Change the colour of the header between editions, eg.<br>
CE = dark grey<br>
EE = black</p>
<p>Thoughts?</p>
RhodeCode CE/EE - Task #3377 (New): extra fields types extensionshttps://issues.rhodecode.com/issues/33772016-03-24T15:23:40ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>I really like redmine extra fields concept. We should copy this to our extra fields. The extensions should be that types have a logic behind it.</p>
<p>for example:</p>
<ul>
<li>autocomplete-user-type -> input autocomplete field for users</li>
<li>select type -> select values from a list</li>
</ul>
RhodeCode CE/EE - Task #3376 (New): Repo action pluginshttps://issues.rhodecode.com/issues/33762016-03-24T15:21:34ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Rcextensions concept is broken. It's really hard to add new extensions, and manage them.</p>
<ul>
<li>we need a concept of UI plugins we could add quickly.</li>
<li>this should be based on similar rcextensions mechanics</li>
<li>the code should be a part fo Enterprise Codebase</li>
<li>we should use extra fields to define some extra parameters</li>
<li>plugins should enable extra fields, and read data from them</li>
</ul>
<p>First good idea is to have default-reviewers plugin.</p>
RhodeCode CE/EE - Task #3362 (New): auth-plugins, indicate visually that plugin is turned on but ...https://issues.rhodecode.com/issues/33622016-03-22T19:03:57ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Based on customer feedback it's confusing that you have to twice enable a plugin, first from the list, then check the enabled checbox and save. We need to fix this either visually or conceptually.</p>
RhodeCode Tools - Task #3333 (New): Create rhodecode-tools backup command for backup of RhodeCode...https://issues.rhodecode.com/issues/33332016-03-17T12:43:52ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We should create a backup command that allows to backup instances.</p>
<ul>
<li>needs to be atomic for repositories so we don't catch a push in progress operation</li>
<li>needs to identify all required files to backup including configs, extra hooks, gists, databases etc</li>
</ul>
RhodeCode CE/EE - Task #3261 (New): mousetrap.js bump to latest 1.5.X versionhttps://issues.rhodecode.com/issues/32612016-03-11T16:21:59ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Bump musetrap js to latest version release.</p>
RhodeCode CE/EE - Task #3260 (New): api: expose get_repo_node methodhttps://issues.rhodecode.com/issues/32602016-03-11T13:34:53ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We have get_repo_nodes method while we really need get_repo_node to fetch a single file from repository.</p>
RhodeCode CE/EE - Task #3239 (Resolved): Catch all route for repo page or repo group page is alwa...https://issues.rhodecode.com/issues/32392016-03-04T10:32:22ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>THere's two routes in the match chain that catch repositories and groups landing page</p>
<pre><code> _connect_with_slash(
rmap, 'repo_group_home', '/{group_name}',
controller='home', action='index_repo_group',
conditions={'function': check_group},
requirements=URL_NAME_REQUIREMENTS)
</code></pre>
<p>and</p>
<pre><code> _connect_with_slash(
rmap, 'summary_home', '/{repo_name}',
controller='summary', action='index',
conditions={'function': check_repo},
requirements=URL_NAME_REQUIREMENTS)
</code></pre>
<p>There are defined at the beginning of the routes. Those routes execute check_repo and check_repo_group.<br>
What it means that if you visit any other page inside a repo or group you have the check_repo or check_group executed twice.</p>
<p>Example:</p>
<p>You go to <a href="https://code.rhodecode.com/https://code.rhodecode.com/rhodecode-momentum/pull-request" class="external">https://code.rhodecode.com/https://code.rhodecode.com/rhodecode-momentum/pull-request</a>, currently it matches both checks, eg.</p>
<ul>
<li>code checks if <code>rhodecode-momentum/pull-request</code> is a repository group (since /{group_name} match)</li>
<li>code checks if <code>rhodecode-momentum/pull-request</code> is a repository (since /{repo_name} match)</li>
<li>code checks if <code>rhodecode-momentum</code> is a repo (since /{repo_name}/pull-request}, only this matches since the route matches patterns, and repo check is valid.</li>
</ul>
<p>Imho we should move the eager matching patterns at the end, so we reduce the group/repo checks to the very end. This should speed up most of the pages since those checks will be skipped</p>
Documentation - Task #3093 (New): [API] - update hg/git update pr API. Auto updates PR on pushhttps://issues.rhodecode.com/issues/30932016-01-21T15:30:21ZBrian Butlerbrian@rhodecode.comDocumentation - Task #3092 (New): [RCE, ini] - doc available settings + check tender with Gemalto...https://issues.rhodecode.com/issues/30922016-01-21T15:10:51ZBrian Butlerbrian@rhodecode.comRhodeCode CE/EE - Task #2944 (New): Bump gunicorn to 19.4 versionhttps://issues.rhodecode.com/issues/29442015-11-23T10:48:09ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Fixes some gevent related issues and other small bugs</p>
RhodeCode CE/EE - Task #2844 (New): Update Bcrypt to a maintained versionhttps://issues.rhodecode.com/issues/28442015-10-27T12:12:46ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We use py-bcrypt-0.4 which is unmaintained.</p>
<p>We should switch to <a href="https://pypi.python.org/pypi/bcrypt/3.1.1" class="external">https://pypi.python.org/pypi/bcrypt/3.1.1</a> which should be fully compatible.</p>
RhodeCode CE/EE - Task #2744 (Resolved): Deprecating Internet Explorerhttps://issues.rhodecode.com/issues/27442015-09-29T16:05:04ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Thought about it a little bit, here's my proposal on ie deprecation:</p>
<p>RhodeCode 3.7 would be the last IE8 tested release.<br>
RhodeCode 3.7+ we stop testing on IE8</p>
<p>RhodeCode 3.8 would be the last supporting IE9<br>
RhodeCode 3.8+ we would stop testing on IE9</p>
<p>TBD: do we simply stop testing, on clean up IE specific hacks ?</p>
<p>As of 3.7+ and 3.8+ we need a dedicated page about not supported browser to display to users that use older browsers. Why ? We have twice issue that users did use ie11, but they had IE7/8 rendering engine enabled. We should be explicit about detecting older IE and listing what we actually support</p>
Documentation - Task #737 (New): What is an extra field and how do you add it?https://issues.rhodecode.com/issues/7372015-01-14T13:57:54ZLisa Quatmannlisa@rhodecode.com
<p>Ok, I know the answer to the first part but regular users may not. If you don't have any extra fields, then when you go to the page where you would edit them, you get a message which says "Extra fields are disabled". However, it has no information on how to enable them if one is able to do that.</p>
Documentation - Task #682 (New): Error Msg guidehttps://issues.rhodecode.com/issues/6822015-01-12T08:56:24ZBrian Butlerbrian@rhodecode.com
<p>We should have a guide that describes the messages, and the actions to take for each one</p>