On 01/09/2014 03:17 PM, Łukasz Stelmach wrote:
Hello.
Hi
I've got some comments for my changes in Gerrit recently (thank you
Philippe) asking me to add a reference to a ticket in Jira.
I was just suggesting :)
As much as like the idea of integration of those system, I am not sure
we need a ticket for every change.
For each change I dont think it's a good idea,
but It would makes sense to have some meta bug
for general tasks ... ie: "xyz support on profile abc" and attach to it
I consider Jira being a system for
passing a problem between different people before solving it, without
a risk of forgetting the problem.
In my other project, jira was also used to describe tasks ,
and we used to discuss over there not on mailing list...
benefit is granularity ...
drawback is that someone could miss some information
if he's not involved into that specific task...
However, if *I* find a problem which
*I* can and do solve by creating and uploading a patch to Gerrit, I
don't find it necessary to create *and* maintain another entry in
a different system.
I agrea , there is no need to slow down the process... this could be
(more?) painful
but at the sametime if you can't maintain the evolution of the change
(ie, version jump) it would be harded for the integrator to guess
why that change or patch is there and should be kept or not ...
( I am not talking about sharing/merging projects between profiles ...
how to prepare those tasks and make them easier?)
To find the right balance
I would reuse existing "meta" JIRA entries and not create new ones ...
Both the problem and the solution can be discussed
in gerrit.
Yes that's the purpose of the tool ... but once it's merged the
discussion is almost gone for ever
while jira search feature is more user friendly ...
Or I wish JIRA has a gerrit plugin
*Iff* the conclusion is that the patch isn't a sutiable
solution and there is no obvious one, then I can see a reason in
creating a ticket with a reference to the change and abandoning the
change.
/me nods
RFC. What is the official policy?
The one on tizen.org :)
Note, I started a draft over there and will be happy to have some
feedback there
https://wiki.tizen.org/wiki/Talk:Packaging/Guidelines
Note also the "Origin:" keyword in case patches are also upstream
Kind regards,
Now the idea had been said, everyone is aware
I can ease up commenting about benefits of crosslinking jira and gerrit
Note on tizen.org ATM I don't give negative note if there are none BugIds,
Just invite developers to do so...
Regards
--
mailto:[email protected] -- gpg:0x467094BC
xmpp:[email protected]
https://dockr.eurogiciel.fr/blogs/embedded/author/pcl/
.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
