|
Notes |
|
|
|
Adding a copy of the email thread for reference.
What do you guys think if, in the new bug tracker, we add a custom field for Fix Requests (background: bugs are logged as Defects and defects are solved by one or more Fix Requests linked to the defect) called "Fixed in SVN Revision"?
We could make that field mandatory to close the Fixed Request with resolution Fixed.
That way:
1) It would be automatically enforced
2) It would be easier to search than a comment
Jaime: do you think it is possible? I created feature request 61 in Mantis to track this.
Paolo
- Hide quoted text -
On Fri, Mar 14, 2008 at 5:03 PM, Ismael Ciordia, Openbravo <ismael.ciordia@openbravo.com> wrote:
Hi Jordi,
I agree with you but it would be better if release management team take care of this.
Ismael
-----Mensaje original-----
De: Jordi Mas [mailto:jordi.mas@openbravo.com]
Enviado el: viernes, 14 de marzo de 2008 16:27
Para: Ismael Ciordia, Openbravo
CC: 'qa'
Asunto: RE: [qa] Indicating the revision number when closing a bug
Isma,
Is this is going to be a new policy from now it would be good to comment it on your next engineering meeting and also to send a message to openbravo-developer-announce.
Jordi,
El dv 14 de 03 del 2008 a les 16:00 +0100, en/na Ismael Ciordia, Openbravo va escriure:
> Agree
>
> -----Mensaje original-----
> De: qa-bounces@openbravo.com [mailto:qa-bounces@openbravo.com]En nombre de Jordi Mas
> Enviado el: viernes, 14 de marzo de 2008 15:28
> Para: qa
> Asunto: [qa] Indicating the revision number when closing a bug
>
>
> Hello,
>
> In a blog comment to my blog post a user says[1]:
>
> ;-----------------------------------------------------------------------------------------------------------------------------------------
> BTW, I noticed that lot's of bug corrections in the bug tracker don't include cross references to the corresponding SVN changes. Please could you ensure those are made? It's very important indeed to see them in order to gain good readability on which build may or may not have the listed regression. It also learns your community about what kind of resolutions have been made for what kind of bugs. Thanks and keep it great.
> ;-----------------------------------------------------------------------------------------------------------------------------------------
>
> He is right. It is a common practise in open source projects to:
>
> · Indicate in the commit comment or the ChangeLog if you are fixing a particular bug in the commit (we are currently doing this)
> · When you are closing a bug in Tracker, indicate in which revision (see [2] or [3]) you have closed the bug. For example, it is very common to include a comment like "Fixed. See revision XXXXX"
>
> I think that this is a good policy because people looking for the fix for a specific bug can quickly spot it.
>
> Jordi,
>
> [1] http://jordimash.blogspot.com/2008/02/openbravo-community-plans-for-2008.html [^]
> [2] http://dev.processing.org/bugs/show_bug.cgi?id=174 [^]
> [3] http://deuce.doc.wustl.edu/bugzilla/show_bug.cgi?id=2845 [^]
>
> --
> Jordi Mas, jordi.mas@openbravo.com - http://planet.openbravo.com [^]
> IRC channel #openbravo at irc.freenode.net - 24 hours per day!
--
Jordi Mas, jordi.mas@openbravo.com - http://planet.openbravo.com [^]
IRC channel #openbravo at irc.freenode.net - 24 hours per day! |
|
|
|
|
|
|
|
|
|
|
|
|
|
Field created and added in the workflow when resolving a bug. The rest of the feature requests suggested in the notes will be resolved when the integration with subversion gets done (feature request 0000384). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|