[opensuse-packaging] Changelog: Reference github issues or pull requests
At http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_... there is a quite impressive list of abbreviations to link to tickets of different system; As there is a growing number of tools which come from github, it would be great to have the possibility to reference the bugs; unfortunately they don't offer system-wide IDs but project specific IDs... Is there any plan how to handle this? Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 13.06.2013 11:33, schrieb Johannes Weberhofer:
At http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_... there is a quite impressive list of abbreviations to link to tickets of different system;
As there is a growing number of tools which come from github, it would be great to have the possibility to reference the bugs; unfortunately they don't offer system-wide IDs but project specific IDs...
Is there any plan how to handle this?
Best regards, Johannes
maybe something like gh#fail2ban/fail2ban/pull/249 or gh#fail2ban/fail2ban/issues/243 ? -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Johannes Weberhofer (jweberhofer@weberhofer.at) wrote:
Am 13.06.2013 11:33, schrieb Johannes Weberhofer:
At http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_... there is a quite impressive list of abbreviations to link to tickets of different system;
As there is a growing number of tools which come from github, it would be great to have the possibility to reference the bugs; unfortunately they don't offer system-wide IDs but project specific IDs...
Is there any plan how to handle this?
Best regards, Johannes
maybe something like gh#fail2ban/fail2ban/pull/249 or gh#fail2ban/fail2ban/issues/243 ?
It would be better if it was at least partially consistent with github's own cross-referencing system, which for the above examples would be: fail2ban/fail2ban#249 fail2ban/fail2ban#243 However we would still need a prefix to identify the github namespace, so maybe something like this? gh:fail2ban/fail2ban#249 gh:fail2ban/fail2ban#243 https://help.github.com/articles/github-flavored-markdown#references -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 13.06.2013 12:46, schrieb Adam Spiers:
Johannes Weberhofer (jweberhofer@weberhofer.at) wrote:
Am 13.06.2013 11:33, schrieb Johannes Weberhofer:
At http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_... there is a quite impressive list of abbreviations to link to tickets of different system;
As there is a growing number of tools which come from github, it would be great to have the possibility to reference the bugs; unfortunately they don't offer system-wide IDs but project specific IDs...
Is there any plan how to handle this?
Best regards, Johannes
maybe something like gh#fail2ban/fail2ban/pull/249 or gh#fail2ban/fail2ban/issues/243 ?
It would be better if it was at least partially consistent with github's own cross-referencing system, which for the above examples would be:
fail2ban/fail2ban#249 fail2ban/fail2ban#243
However we would still need a prefix to identify the github namespace, so maybe something like this?
gh:fail2ban/fail2ban#249 gh:fail2ban/fail2ban#243
https://help.github.com/articles/github-flavored-markdown#references
This would be very good to have. Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 06/13/2013 12:46 PM, Adam Spiers wrote:
Johannes Weberhofer (jweberhofer@weberhofer.at) wrote:
Am 13.06.2013 11:33, schrieb Johannes Weberhofer:
At http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_... there is a quite impressive list of abbreviations to link to tickets of different system;
As there is a growing number of tools which come from github, it would be great to have the possibility to reference the bugs; unfortunately they don't offer system-wide IDs but project specific IDs...
Is there any plan how to handle this?
Best regards, Johannes
maybe something like gh#fail2ban/fail2ban/pull/249 or gh#fail2ban/fail2ban/issues/243 ?
It would be better if it was at least partially consistent with github's own cross-referencing system, which for the above examples would be:
fail2ban/fail2ban#249 fail2ban/fail2ban#243
However we would still need a prefix to identify the github namespace, so maybe something like this?
gh:fail2ban/fail2ban#249 gh:fail2ban/fail2ban#243
https://help.github.com/articles/github-flavored-markdown#references
Would github recognize these and mark them properly? In that case I suggest to go for it - meaning enhance the packaging guidelines with this new convention, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Andreas Jaeger (aj@suse.com) wrote:
On 06/13/2013 12:46 PM, Adam Spiers wrote:
Johannes Weberhofer (jweberhofer@weberhofer.at) wrote:
Am 13.06.2013 11:33, schrieb Johannes Weberhofer:
At http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_... there is a quite impressive list of abbreviations to link to tickets of different system;
As there is a growing number of tools which come from github, it would be great to have the possibility to reference the bugs; unfortunately they don't offer system-wide IDs but project specific IDs...
Is there any plan how to handle this?
Best regards, Johannes
maybe something like gh#fail2ban/fail2ban/pull/249 or gh#fail2ban/fail2ban/issues/243 ?
It would be better if it was at least partially consistent with github's own cross-referencing system, which for the above examples would be:
fail2ban/fail2ban#249 fail2ban/fail2ban#243
However we would still need a prefix to identify the github namespace, so maybe something like this?
gh:fail2ban/fail2ban#249 gh:fail2ban/fail2ban#243
https://help.github.com/articles/github-flavored-markdown#references
Would github recognize these and mark them properly?
In what context? github only hyperlinks them when the text is passed through its markdown parser, and even then, the "gh:" prefix would stop this from working. But would that even matter? I think we first need to answer the question: what are we trying to achieve here, exactly? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 13.06.2013 14:17, schrieb Adam Spiers:
Andreas Jaeger (aj@suse.com) wrote:
On 06/13/2013 12:46 PM, Adam Spiers wrote:
Johannes Weberhofer (jweberhofer@weberhofer.at) wrote:
Am 13.06.2013 11:33, schrieb Johannes Weberhofer:
At http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_... there is a quite impressive list of abbreviations to link to tickets of different system;
As there is a growing number of tools which come from github, it would be great to have the possibility to reference the bugs; unfortunately they don't offer system-wide IDs but project specific IDs...
Is there any plan how to handle this?
Best regards, Johannes
maybe something like gh#fail2ban/fail2ban/pull/249 or gh#fail2ban/fail2ban/issues/243 ?
It would be better if it was at least partially consistent with github's own cross-referencing system, which for the above examples would be:
fail2ban/fail2ban#249 fail2ban/fail2ban#243
However we would still need a prefix to identify the github namespace, so maybe something like this?
gh:fail2ban/fail2ban#249 gh:fail2ban/fail2ban#243
https://help.github.com/articles/github-flavored-markdown#references
Would github recognize these and mark them properly?
In what context? github only hyperlinks them when the text is passed through its markdown parser, and even then, the "gh:" prefix would stop this from working. But would that even matter?
I think we first need to answer the question: what are we trying to achieve here, exactly?
I think it should be documented in the wiki (I can do this) and it would be great when the OBS would offer a link to the ticket/issue when reviewing a request and it's mentioned in the changelog like it is done for bnc# tickets; I've just recognized, that the typical separator is '#' not ':', so the entry should possibly be named gh#fail2ban/fail2ban#249 Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Johannes Weberhofer (jweberhofer@weberhofer.at) wrote:
Am 13.06.2013 14:17, schrieb Adam Spiers:
Andreas Jaeger (aj@suse.com) wrote:
On 06/13/2013 12:46 PM, Adam Spiers wrote:
Johannes Weberhofer (jweberhofer@weberhofer.at) wrote:
Am 13.06.2013 11:33, schrieb Johannes Weberhofer:
At http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_... there is a quite impressive list of abbreviations to link to tickets of different system;
As there is a growing number of tools which come from github, it would be great to have the possibility to reference the bugs; unfortunately they don't offer system-wide IDs but project specific IDs...
Is there any plan how to handle this?
Best regards, Johannes
maybe something like gh#fail2ban/fail2ban/pull/249 or gh#fail2ban/fail2ban/issues/243 ?
It would be better if it was at least partially consistent with github's own cross-referencing system, which for the above examples would be:
fail2ban/fail2ban#249 fail2ban/fail2ban#243
However we would still need a prefix to identify the github namespace, so maybe something like this?
gh:fail2ban/fail2ban#249 gh:fail2ban/fail2ban#243
https://help.github.com/articles/github-flavored-markdown#references
Would github recognize these and mark them properly?
In what context? github only hyperlinks them when the text is passed through its markdown parser, and even then, the "gh:" prefix would stop this from working. But would that even matter?
I think we first need to answer the question: what are we trying to achieve here, exactly?
I think it should be documented in the wiki (I can do this) and it would be great when the OBS would offer a link to the ticket/issue when reviewing a request and it's mentioned in the changelog like it is done for bnc# tickets; I've just recognized, that the typical separator is '#' not ':', so the entry should possibly be named
gh#fail2ban/fail2ban#249
Sounds good to me! -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Adam Spiers -
Andreas Jaeger -
Johannes Weberhofer