You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "christofer.dutz@c-ware.de" <ch...@c-ware.de> on 2012/12/12 08:38:48 UTC
Suggestion to commits and Jira
Hi,
I just wanted to have a look at what Jose did to fix a bug in the Mavenizer. My usual workflow for this is to go to the Jira Issue and select the "Source" tab. In all of the Jira+SVN/GIT combinations I have seen Jira displays the commits related to that particular issue. I couldn't find a single issue in which Jira found anything.
Is this feature not turned on or did simply no one check in any code with a comment containing the Jira issue id of the related issue?
I would strongly suggest to link the code repo and Jira and to prefix commit-comments with Jira issue Id of the issue the checkin relates to (Ideally with the title of the Issue) in order to get this cool bonus functionality. If one commit addresses a bunch of issues simply mentioning them all in the commit statement, would also make that particular cheking appear on all of these issues detail-pages.
Just a suggestion :)
Chris
Re: AW: Suggestion to commits and Jira
Posted by Frédéric THOMAS <we...@hotmail.com>.
> Otherwise you would have to register for the commit list
Yes
> and keep everything in order to do searches there
and yes too :P
- Fred
-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Wednesday, December 12, 2012 8:49 AM
To: flex-dev@incubator.apache.org
Subject: AW: Suggestion to commits and Jira
Well it would be nice to be able to click on an issue and see what was done
to resolve it. Otherwise you would have to register for the commit list and
keep everything in order to do searches there, which I think is relatively
undesirable considering the current size of my pst-file. It's a feature that
comes almost for free and I think the benefits outweigh the cost by far. But
that's just my personal opinion ;-)
-----Ursprüngliche Nachricht-----
Von: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Gesendet: Mittwoch, 12. Dezember 2012 08:45
An: flex-dev@incubator.apache.org
Betreff: Re: Suggestion to commits and Jira
Hi Chris,
I don't know for that, I used to work the same but here, in the commit
mailling list, for each commit, you can see a link to viewvc with the diff
for each commit but sure, it would be nice to have the same in JIRA.
- Fred
-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Wednesday, December 12, 2012 8:38 AM
To: flex-dev@incubator.apache.org
Subject: Suggestion to commits and Jira
Hi,
I just wanted to have a look at what Jose did to fix a bug in the Mavenizer.
My usual workflow for this is to go to the Jira Issue and select the
"Source" tab. In all of the Jira+SVN/GIT combinations I have seen Jira
displays the commits related to that particular issue. I couldn't find a
single issue in which Jira found anything.
Is this feature not turned on or did simply no one check in any code with a
comment containing the Jira issue id of the related issue?
I would strongly suggest to link the code repo and Jira and to prefix
commit-comments with Jira issue Id of the issue the checkin relates to
(Ideally with the title of the Issue) in order to get this cool bonus
functionality. If one commit addresses a bunch of issues simply mentioning
them all in the commit statement, would also make that particular cheking
appear on all of these issues detail-pages.
Just a suggestion :)
Chris
Re: AW: Suggestion to commits and Jira
Posted by Frédéric THOMAS <we...@hotmail.com>.
+1
-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Wednesday, December 12, 2012 8:49 AM
To: flex-dev@incubator.apache.org
Subject: AW: Suggestion to commits and Jira
Well it would be nice to be able to click on an issue and see what was done
to resolve it. Otherwise you would have to register for the commit list and
keep everything in order to do searches there, which I think is relatively
undesirable considering the current size of my pst-file. It's a feature that
comes almost for free and I think the benefits outweigh the cost by far. But
that's just my personal opinion ;-)
-----Ursprüngliche Nachricht-----
Von: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Gesendet: Mittwoch, 12. Dezember 2012 08:45
An: flex-dev@incubator.apache.org
Betreff: Re: Suggestion to commits and Jira
Hi Chris,
I don't know for that, I used to work the same but here, in the commit
mailling list, for each commit, you can see a link to viewvc with the diff
for each commit but sure, it would be nice to have the same in JIRA.
- Fred
-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Wednesday, December 12, 2012 8:38 AM
To: flex-dev@incubator.apache.org
Subject: Suggestion to commits and Jira
Hi,
I just wanted to have a look at what Jose did to fix a bug in the Mavenizer.
My usual workflow for this is to go to the Jira Issue and select the
"Source" tab. In all of the Jira+SVN/GIT combinations I have seen Jira
displays the commits related to that particular issue. I couldn't find a
single issue in which Jira found anything.
Is this feature not turned on or did simply no one check in any code with a
comment containing the Jira issue id of the related issue?
I would strongly suggest to link the code repo and Jira and to prefix
commit-comments with Jira issue Id of the issue the checkin relates to
(Ideally with the title of the Issue) in order to get this cool bonus
functionality. If one commit addresses a bunch of issues simply mentioning
them all in the commit statement, would also make that particular cheking
appear on all of these issues detail-pages.
Just a suggestion :)
Chris
AW: Suggestion to commits and Jira
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Well it would be nice to be able to click on an issue and see what was done to resolve it. Otherwise you would have to register for the commit list and keep everything in order to do searches there, which I think is relatively undesirable considering the current size of my pst-file. It's a feature that comes almost for free and I think the benefits outweigh the cost by far. But that's just my personal opinion ;-)
-----Ursprüngliche Nachricht-----
Von: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Gesendet: Mittwoch, 12. Dezember 2012 08:45
An: flex-dev@incubator.apache.org
Betreff: Re: Suggestion to commits and Jira
Hi Chris,
I don't know for that, I used to work the same but here, in the commit mailling list, for each commit, you can see a link to viewvc with the diff for each commit but sure, it would be nice to have the same in JIRA.
- Fred
-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Wednesday, December 12, 2012 8:38 AM
To: flex-dev@incubator.apache.org
Subject: Suggestion to commits and Jira
Hi,
I just wanted to have a look at what Jose did to fix a bug in the Mavenizer.
My usual workflow for this is to go to the Jira Issue and select the "Source" tab. In all of the Jira+SVN/GIT combinations I have seen Jira displays the commits related to that particular issue. I couldn't find a single issue in which Jira found anything.
Is this feature not turned on or did simply no one check in any code with a comment containing the Jira issue id of the related issue?
I would strongly suggest to link the code repo and Jira and to prefix commit-comments with Jira issue Id of the issue the checkin relates to (Ideally with the title of the Issue) in order to get this cool bonus functionality. If one commit addresses a bunch of issues simply mentioning them all in the commit statement, would also make that particular cheking appear on all of these issues detail-pages.
Just a suggestion :)
Chris
Re: Suggestion to commits and Jira
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Chris,
I don't know for that, I used to work the same but here, in the commit
mailling list, for each commit, you can see a link to viewvc with the diff
for each commit but sure, it would be nice to have the same in JIRA.
- Fred
-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Wednesday, December 12, 2012 8:38 AM
To: flex-dev@incubator.apache.org
Subject: Suggestion to commits and Jira
Hi,
I just wanted to have a look at what Jose did to fix a bug in the Mavenizer.
My usual workflow for this is to go to the Jira Issue and select the
"Source" tab. In all of the Jira+SVN/GIT combinations I have seen Jira
displays the commits related to that particular issue. I couldn't find a
single issue in which Jira found anything.
Is this feature not turned on or did simply no one check in any code with a
comment containing the Jira issue id of the related issue?
I would strongly suggest to link the code repo and Jira and to prefix
commit-comments with Jira issue Id of the issue the checkin relates to
(Ideally with the title of the Issue) in order to get this cool bonus
functionality. If one commit addresses a bunch of issues simply mentioning
them all in the commit statement, would also make that particular cheking
appear on all of these issues detail-pages.
Just a suggestion :)
Chris
AW: Suggestion to commits and Jira
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Ok ... so it seems that the "Source"-Tab functionality is broken as well as only few Committers add the Issue numbers ... good to know ;-)
-----Ursprüngliche Nachricht-----
Von: Jose Barragan [mailto:jose.barragan@codeoscopic.com]
Gesendet: Mittwoch, 12. Dezember 2012 09:28
An: flex-dev@incubator.apache.org
Betreff: Re: Suggestion to commits and Jira
In fact, I'm always include the ticket number and url reference in commit description :)
--
Jose Barragan
Software Architect Chief
Codeoscopic Madrid
C/. Infanta Mercedes, 92.
Planta 5. 505.
28020 Madrid.
Tel.: +34 912 94 80 80
On Dec 12, 2012, at 9:26 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de> wrote:
> That's why I was suggesting to sort of make it part of the
> "apache-flex-way" to simply add those few chars to the commit messages
> :-)
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]
> Gesendet: Mittwoch, 12. Dezember 2012 09:09
> An: flex-dev@incubator.apache.org
> Betreff: Re: Suggestion to commits and Jira
>
> Hi,
>
> On Wed, Dec 12, 2012 at 8:38 AM, christofer.dutz@c-ware.de <ch...@c-ware.de> wrote:
>> ...My usual workflow for this is to go to the Jira Issue and select
>> the "Source" tab. In all of the
>> Jira+SVN/GIT combinations I have seen Jira displays the commits related to that particular issue...
>
> Stanbol seems to have the same issue, I've added a mention of Flex at
> https://issues.apache.org/jira/browse/INFRA-5635
>
> Note that this (obviously) only works if people include FLEX- references in the commit log messages, which doesn't seem to happen often here.
>
> -Bertrand
Re: Suggestion to commits and Jira
Posted by Frédéric THOMAS <we...@hotmail.com>.
> OK, so can someone explicitly put the steps and an example in this email
> and
on the wiki?
It's not better to do it as soon as the feature won't be broken anymore ?
- Fred
-----Message d'origine-----
From: Alex Harui
Sent: Wednesday, December 12, 2012 5:30 PM
To: flex-dev@incubator.apache.org
Subject: Re: Suggestion to commits and Jira
OK, so can someone explicitly put the steps and an example in this email and
on the wiki?
On 12/12/12 2:15 AM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
> Hi Bertrand,
>
> That is so that you have not watched in the correct branch :P
>
> http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fflex%2Futi
> lities%2Ftrunk
>
> --
> Jose Barragan
> Software Architect Chief
> Codeoscopic Madrid
> C/. Infanta Mercedes, 92.
> Planta 5. 505.
> 28020 Madrid.
> Tel.: +34 912 94 80 80
>
> On Dec 12, 2012, at 9:41 AM, Bertrand Delacretaz <bd...@apache.org>
> wrote:
>
>> On Wed, Dec 12, 2012 at 9:27 AM, Jose Barragan
>> <jo...@codeoscopic.com> wrote:
>>> In fact, I'm always include the ticket number and url reference in
>>> commit
>>> description :)
>>
>> Cool! I was just looking at
>> http://svnsearch.org/svnsearch/repos/ASF/search?start-index=140&path=%2Fincub
>> ator%2Fflex
>> and didn't see lots of that.
>>
>> -Bertrand
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Suggestion to commits and Jira
Posted by Alex Harui <ah...@adobe.com>.
OK, so can someone explicitly put the steps and an example in this email and
on the wiki?
On 12/12/12 2:15 AM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
> Hi Bertrand,
>
> That is so that you have not watched in the correct branch :P
>
> http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fflex%2Futi
> lities%2Ftrunk
>
> --
> Jose Barragan
> Software Architect Chief
> Codeoscopic Madrid
> C/. Infanta Mercedes, 92.
> Planta 5. 505.
> 28020 Madrid.
> Tel.: +34 912 94 80 80
>
> On Dec 12, 2012, at 9:41 AM, Bertrand Delacretaz <bd...@apache.org>
> wrote:
>
>> On Wed, Dec 12, 2012 at 9:27 AM, Jose Barragan
>> <jo...@codeoscopic.com> wrote:
>>> In fact, I'm always include the ticket number and url reference in commit
>>> description :)
>>
>> Cool! I was just looking at
>> http://svnsearch.org/svnsearch/repos/ASF/search?start-index=140&path=%2Fincub
>> ator%2Fflex
>> and didn't see lots of that.
>>
>> -Bertrand
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Suggestion to commits and Jira
Posted by Jose Barragan <jo...@codeoscopic.com>.
Hi Bertrand,
That is so that you have not watched in the correct branch :P
http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fflex%2Futilities%2Ftrunk
--
Jose Barragan
Software Architect Chief
Codeoscopic Madrid
C/. Infanta Mercedes, 92.
Planta 5. 505.
28020 Madrid.
Tel.: +34 912 94 80 80
On Dec 12, 2012, at 9:41 AM, Bertrand Delacretaz <bd...@apache.org> wrote:
> On Wed, Dec 12, 2012 at 9:27 AM, Jose Barragan
> <jo...@codeoscopic.com> wrote:
>> In fact, I'm always include the ticket number and url reference in commit description :)
>
> Cool! I was just looking at
> http://svnsearch.org/svnsearch/repos/ASF/search?start-index=140&path=%2Fincubator%2Fflex
> and didn't see lots of that.
>
> -Bertrand
Re: Suggestion to commits and Jira
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Dec 12, 2012 at 9:27 AM, Jose Barragan
<jo...@codeoscopic.com> wrote:
> In fact, I'm always include the ticket number and url reference in commit description :)
Cool! I was just looking at
http://svnsearch.org/svnsearch/repos/ASF/search?start-index=140&path=%2Fincubator%2Fflex
and didn't see lots of that.
-Bertrand
Re: Suggestion to commits and Jira
Posted by Jose Barragan <jo...@codeoscopic.com>.
In fact, I'm always include the ticket number and url reference in commit description :)
--
Jose Barragan
Software Architect Chief
Codeoscopic Madrid
C/. Infanta Mercedes, 92.
Planta 5. 505.
28020 Madrid.
Tel.: +34 912 94 80 80
On Dec 12, 2012, at 9:26 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de> wrote:
> That's why I was suggesting to sort of make it part of the "apache-flex-way" to simply add those few chars to the commit messages :-)
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]
> Gesendet: Mittwoch, 12. Dezember 2012 09:09
> An: flex-dev@incubator.apache.org
> Betreff: Re: Suggestion to commits and Jira
>
> Hi,
>
> On Wed, Dec 12, 2012 at 8:38 AM, christofer.dutz@c-ware.de <ch...@c-ware.de> wrote:
>> ...My usual workflow for this is to go to the Jira Issue and select
>> the "Source" tab. In all of the
>> Jira+SVN/GIT combinations I have seen Jira displays the commits related to that particular issue...
>
> Stanbol seems to have the same issue, I've added a mention of Flex at
> https://issues.apache.org/jira/browse/INFRA-5635
>
> Note that this (obviously) only works if people include FLEX- references in the commit log messages, which doesn't seem to happen often here.
>
> -Bertrand
AW: Suggestion to commits and Jira
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
That's why I was suggesting to sort of make it part of the "apache-flex-way" to simply add those few chars to the commit messages :-)
-----Ursprüngliche Nachricht-----
Von: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]
Gesendet: Mittwoch, 12. Dezember 2012 09:09
An: flex-dev@incubator.apache.org
Betreff: Re: Suggestion to commits and Jira
Hi,
On Wed, Dec 12, 2012 at 8:38 AM, christofer.dutz@c-ware.de <ch...@c-ware.de> wrote:
> ...My usual workflow for this is to go to the Jira Issue and select
> the "Source" tab. In all of the
> Jira+SVN/GIT combinations I have seen Jira displays the commits related to that particular issue...
Stanbol seems to have the same issue, I've added a mention of Flex at
https://issues.apache.org/jira/browse/INFRA-5635
Note that this (obviously) only works if people include FLEX- references in the commit log messages, which doesn't seem to happen often here.
-Bertrand
Re: Suggestion to commits and Jira
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Bertrand,
But Still, good to know that's the normal workflow, even if it's broken at
the moment, I keep that in mind.
- Fred
-----Message d'origine-----
From: Bertrand Delacretaz
Sent: Wednesday, December 12, 2012 9:08 AM
To: flex-dev@incubator.apache.org
Subject: Re: Suggestion to commits and Jira
Hi,
On Wed, Dec 12, 2012 at 8:38 AM, christofer.dutz@c-ware.de
<ch...@c-ware.de> wrote:
> ...My usual workflow for this is to go to the Jira Issue and select the
> "Source" tab. In all of the
> Jira+SVN/GIT combinations I have seen Jira displays the commits related to
> that particular issue...
Stanbol seems to have the same issue, I've added a mention of Flex at
https://issues.apache.org/jira/browse/INFRA-5635
Note that this (obviously) only works if people include FLEX-
references in the commit log messages, which doesn't seem to happen
often here.
-Bertrand
Re: Suggestion to commits and Jira
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Wed, Dec 12, 2012 at 8:38 AM, christofer.dutz@c-ware.de
<ch...@c-ware.de> wrote:
> ...My usual workflow for this is to go to the Jira Issue and select the "Source" tab. In all of the
> Jira+SVN/GIT combinations I have seen Jira displays the commits related to that particular issue...
Stanbol seems to have the same issue, I've added a mention of Flex at
https://issues.apache.org/jira/browse/INFRA-5635
Note that this (obviously) only works if people include FLEX-
references in the commit log messages, which doesn't seem to happen
often here.
-Bertrand