Skip to content

Replace Launchpad with GitHub #2345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 24, 2021
Merged

Replace Launchpad with GitHub #2345

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4f6193e
Replace Launchpad with GitHub
NickVolynkin Sep 23, 2021
fc9bafb
Update translations
NickVolynkin Sep 24, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions doc/dev_guide/developer_guidelines.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,9 @@ Developer guidelines
How to work on a bug
===========================================================

Any defect, even minor, if it changes the user-visible server behavior, needs
a bug report. Report a bug at http://github.com/tarantool/tarantool/issues.
If a defect changes user-visible server behavior, it needs a bug report,
even if it is a small defect. Report the bug at
`GitHub <https://github.com/tarantool/tarantool/issues>`__.

When reporting a bug, try to come up with a test case right away. Set the
current maintenance milestone for the bug fix, and specify the series.
Expand All @@ -20,8 +21,9 @@ ready, put the bug to 'In review' and solicit a review for the fix.

Once there is a positive code review, push the patch and set the status to 'Closed'

Patches for bugs should contain a reference to the respective Launchpad bug page or
at least bug id. Each patch should have a test, unless coming up with one is
Patches for bugs should contain a reference to the respective
`GitHub issue page <https://github.com/tarantool/tarantool/issues>`__ or
at least the issue id. Each patch should have a test, unless coming up with one is
difficult in the current framework, in which case QA should be alerted.

There are two things you need to do when your patch makes it into the master:
Expand Down
30 changes: 15 additions & 15 deletions locale/ru/LC_MESSAGES/dev_guide/developer_guidelines.po
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,13 @@ msgid "How to work on a bug"
msgstr "Как работать над дефектами"

msgid ""
"Any defect, even minor, if it changes the user-visible server behavior, "
"needs a bug report. Report a bug at "
"http://github.com/tarantool/tarantool/issues."
"If a defect changes user-visible server behavior, it needs a bug report, "
"even if it is a small defect. Report the bug at `GitHub "
"<https://github.com/tarantool/tarantool/issues>`__."
msgstr ""
"На любой дефект, даже незначительный, если он изменяет доступное "
"пользователю поведение сервера, необходимо составить отчет об ошибке. "
"Сообщите о дефекте по ссылке http://github.com/tarantool/tarantool/issues."
"На любой, даже незначительный дефект, меняющий видимое для пользователя "
"поведение сервера, необходимо составить отчет об ошибке. Сообщите о дефекте "
"`на GitHub <https://github.com/tarantool/tarantool/issues>`__."

msgid ""
"When reporting a bug, try to come up with a test case right away. Set the "
Expand All @@ -35,16 +35,16 @@ msgstr ""
"\"Closed\" (закрыт)."

msgid ""
"Patches for bugs should contain a reference to the respective Launchpad bug "
"page or at least bug id. Each patch should have a test, unless coming up "
"with one is difficult in the current framework, in which case QA should be "
"alerted."
"Patches for bugs should contain a reference to the respective `GitHub issue "
"page <https://github.com/tarantool/tarantool/issues>`__ or at least the "
"issue id. Each patch should have a test, unless coming up with one is "
"difficult in the current framework, in which case QA should be alerted."
msgstr ""
"Патчи для исправления ошибок должны содержать ссылку на соответствующую "
"страницу дефекта Launchpad или хотя бы идентификатор дефекта. Каждому патча "
"должен соответствовать отдельный тест, если только это не слишком трудно "
"сделать в текущем окружении, и в этом случае следует предупредить "
"тестировщиков."
"Патчи для исправления ошибок должны содержать ссылку на `страницу нужной "
"задачи на GitHub <https://github.com/tarantool/tarantool/issues>`__ или на "
"идентификатор задачи. Каждому патчу должен соответствовать отдельный тест. "
"Если в текущем окружении создать подходящий тест затруднительно, следует "
"предупредить тестировщиков."

msgid ""
"There are two things you need to do when your patch makes it into the "
Expand Down