I don't think the official policy is documented yet. At this moment, it's not compulsory to refer to a JIRA ticket whenever submitting a patch. May be needed when closing to a milestone or the platform release. IMO, a meaningful change log or commit message is more helpful for day-to-day development. - Bingwei
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of ?ukasz Stelmach > Sent: Thursday, January 09, 2014 10:17 PM > To: [email protected] > Subject: [Dev] Bugs for changes > > Hello. > > 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. > > As much as like the idea of integration of those system, I am not sure we > need a ticket for every change. I consider Jira being a system for passing a > problem between different people before solving it, without a risk of > forgetting the problem. 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. Both > the problem and the solution can be discussed in gerrit. *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. > > RFC. What is the official policy? > > Kind regards, > -- > Łukasz Stelmach > Samsung R&D Institute Poland > Samsung Electronics _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
