Merge lp:~mabkenar/ubuntu-system-settings/typo-fix into lp:ubuntu-system-settings
| Status: | Merged |
|---|---|
| Approved by: | Jonas G. Drange on 2017-01-10 |
| Approved revision: | 1753 |
| Merged at revision: | 1759 |
| Proposed branch: | lp:~mabkenar/ubuntu-system-settings/typo-fix |
| Merge into: | lp:ubuntu-system-settings |
| Diff against target: |
12 lines (+1/-1) 1 file modified
plugins/wifi/OtherNetwork.qml (+1/-1) |
| To merge this branch: | bzr merge lp:~mabkenar/ubuntu-system-settings/typo-fix |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Jonas G. Drange (community) | 2017-01-10 | Approve on 2017-01-10 | |
|
Review via email:
|
|||
Commit Message
typo fix in wifi settings
Description of the Change
Using certificates is recommend as it increases security. (recommend -> recommended)
| Masoud Abkenar (mabkenar) wrote : | # |
You're welcome :) This is just for me to figure out how the process works before I send my real patch that I've been working on.
It seems I still don't understand the process though. Why isn't this already merged after your approval? (Below this page it says "Unmerged revisions" and also in trunk the file hasn't changed.) How should it be merged? Am I expected to do something?
| Jonas G. Drange (jonas-drange) wrote : | # |
> You're welcome :) This is just for me to figure out how the process works
> before I send my real patch that I've been working on.
Excellent, awesome that you want to contribute.
> It seems I still don't understand the process though. Why isn't this already
> merged after your approval? (Below this page it says "Unmerged revisions" and
> also in trunk the file hasn't changed.)
Correct. Code is very rarely pushed to trunk/master by a person. Before that happens, quality assurance must take place. After the merge proposal (MP) has been reviewed, the merging process is handed off to the bileto tool. You can find your MP here: https:/
> How should it be merged?
It is merged by some robot after the following has happened:
0. The code is built in a silo (ppa).
1. Lander testing and approval (me in this case, jgdx)
2. Automated signoff. This is where automated tests are run for every project that depends (in some way) on Ubuntu System Settings. Unity8 is one of these and has a large test suite.
3. QA signoff. QA has tested the test plan and signed off.
4. Code is merged to trunk, code is built and copied to the final destination (archive and/or ppa).
> Am I expected to do something?
Not really, but contributions can be made to anyone of these steps if you please.
Thanks again.
| Masoud Abkenar (mabkenar) wrote : | # |
Thanks for your detailed explanation, I really appreciate it.
I guess this commit will break translations, since it changes the source string that other locales are translating against. But I don't know how can I fix this problem. If you know where to start, please let me know, and I would be glad to start working on it.
| Jonas G. Drange (jonas-drange) wrote : | # |
On 11 January 2017 at 15:03, Masoud Abkenar <email address hidden> wrote:
> I guess this commit will break translations, since it changes the source
> string that other locales are translating against.
>
Said robot will automatically generate the .pot file for this project, so
you don't have to worry about that. The translation itself can be done in
the "translation" tab.


Thanks, Masoud!