3 ms·

Really interesting new features A little feature I'm missing is to have the code coverage percentage in the slack message A bigger one is the fact that the co

by allan_s 10y ago

Really interesting new features A little feature I'm missing is to have the code coverage percentage in the slack message A bigger one is the fact that the comment text area in code review is terribly slow on my very recent desktop in firefox, and unusable on my cellphone (it used to be ok one years ago) I can't wait to deploy this release (we always wait one week after each release official date, just to let one or two bugfix release).

sytse 10y ago
Thanks. It should be possible to have the code coverage in the slack message. Consider opening an issue or contributing the code. The comments text area slowness sounds bad. I've hear people complaining about slowness in Firefox before. I'm not sure how to proceed. Not a bad idea to wait a week after the official release, we expect to have at least one patch release in this timeframe.
- allan_s 10y ago
  https://gitlab.com/gitlab-org/gitlab-ce/issues/19011 https://gitlab.com/gitlab-org/gitlab-ce/issues/19011 https://gitlab.com/gitlab-org/gitlab-ce/issues/19010 https://gitlab.com/gitlab-org/gitlab-ce/issues/19010 here you are :) Yes I think for most software waiting for the .1 release is mostly safe. Thanks a lot once again for the deployement process of gitlab, just having to do apt-get update/upgrade is such a wonderful things, most of project should learn from you, as too often in companies you start to freeze at one version, because the upgrade process is too much mind taking and soon nobody remember how exactly one can upgrade it.
  - sytse 10y ago
    Thanks for creating the issues! And you're welcome for the apt-get upgrades, glad they are a good experience for you.
jakecodes 10y ago
Thanks @allan_s we are aware of the slowness of the diff tab. It is something we are actively (this very second) working on. I am not aware of the slowness of the text area. Can you create an issue to show us so we can fix it? https://gitlab.com/gitlab-org/gitlab-ce/issues/new https://gitlab.com/gitlab-org/gitlab-ce/issues/new

by allan_s 10y ago

sytse 10y ago

Thanks. It should be possible to have the code coverage in the slack message. Consider opening an issue or contributing the code. The comments text area slowness sounds bad. I've hear people complaining about slowness in Firefox before. I'm not sure how to proceed. Not a bad idea to wait a week after the official release, we expect to have at least one patch release in this timeframe.

allan_s 10y ago
https://gitlab.com/gitlab-org/gitlab-ce/issues/19011 https://gitlab.com/gitlab-org/gitlab-ce/issues/19011 https://gitlab.com/gitlab-org/gitlab-ce/issues/19010 https://gitlab.com/gitlab-org/gitlab-ce/issues/19010 here you are :) Yes I think for most software waiting for the .1 release is mostly safe. Thanks a lot once again for the deployement process of gitlab, just having to do apt-get update/upgrade is such a wonderful things, most of project should learn from you, as too often in companies you start to freeze at one version, because the upgrade process is too much mind taking and soon nobody remember how exactly one can upgrade it.
- sytse 10y ago
  Thanks for creating the issues! And you're welcome for the apt-get upgrades, glad they are a good experience for you.

jakecodes 10y ago

Thanks @allan_s we are aware of the slowness of the diff tab. It is something we are actively (this very second) working on. I am not aware of the slowness of the text area. Can you create an issue to show us so we can fix it? https://gitlab.com/gitlab-org/gitlab-ce/issues/new https://gitlab.com/gitlab-org/gitlab-ce/issues/new