| === Ursinha-afk is now known as Ursinha | |
| === Ursinha is now known as Ursinha-afk | |
| === Ursinha-afk is now known as Ursinha | |
| === Ursinha is now known as Ursinha-afk | |
| === Ursinha-afk is now known as Ursinha | |
| [15:45] <damianr> hi there, I am new around here. Can anyone help I have a query? | |
| === Ursinha is now known as Ursinha-afk | |
| [16:41] <hggdh> damianr: if it is related to bugs -- how to set a bug status, how to collect data for the bug, etc, yes. If it is a support question, please go to #ubuntu-bugs | |
| [16:45] <damianr> when creating a patch to fix bugs is there any naming convention for patch for example 99-somebug-patch is good enough? | |
| [16:46] <damianr> hggdh: | |
| [17:58] <damianr> One more doubt, I am fixing a bug but sending propose for merge for one version i.e trusty so how does it gets merged with other versions? or do i have to send separate merge request to all? | |
| [18:05] <penguin42> damianr: Normally you'd go for fixing it in the latest dev world (utopic) and get it 'SRUd' to older verisons | |
| [18:07] <penguin42> damianr: SRU is a Stable Release Update tat happens after the fix is known and accepted in the dev world | |
| [18:08] <damianr> thanks | |
| [18:09] <damianr> so it gets propagated automatically by maintainer only I have to see to the dev branch is patched. | |
| [18:09] <penguin42> ish | |
| [18:10] <penguin42> damianr: on the bug someone has to nominate it for an SRU and explain why it's worth doing | |
| [18:11] <damianr> so only few important patches gets back propagated and fix will most likely end up in next release. | |
| [18:12] <penguin42> yep, because it's risky to backport stuff, since there's a risk it might break something else - so stuff is backported if it's important | |
| [18:12] <penguin42> have a look around the docs - there's a page on SRUs somewhere | |
| [18:12] <penguin42> (back later) | |
| [18:13] <damianr> thanks penguin42 | |