[Laszlo-dev] JIRA policy for fixes going into multiple branches
Jim Grandy
jgrandy at openlaszlo.org
Wed Jun 6 14:34:35 PDT 2007
It is ambiguous, especially when an issue has been reopened. I don't
see too much opportunity for confusion, though, since the meaning is
tied to the Status (Open/Resolved).
jim
On Jun 6, 2007, at 2:09 PM, P T Withington wrote:
> That is what I have been doing, pasting the log from the check-in
> into a comment when I fix a bug. Doing it for each branch. I
> think that is ok, but we also need to clear up the ambiguity of
> 'Fix version/s' -- we are using it both to say which version we
> want the fix to be done for, and to say that it has been fixed in
> that version. The only way to distinguish is whether the bug is
> closed or not. Is everyone ok with that?
>
> Is there a way we can munge Jira to accept arbitrary text in the
> 'Fixed in change#' field?
>
> On 2007-06-06, at 16:59 EDT, Jim Grandy wrote:
>
>> We could get rid of the Fix Number field and just put the
>> information in a comment, with branch name:
>>
>> Checked in as r3654 in branches/legals
>>
>> jim
>>
>> On Jun 6, 2007, at 1:37 PM, Max Carlson wrote:
>>
>>> Please chime in. From IRC:
>>> maxcarlson: should this be two separate issues?
>>> [1:33pm] maxcarlson: There will be two different fix numbers
>>> [1:34pm] maxcarlson: maybe a sub-task for 3.4.2 and another for
>>> 4.0.3
>>> [1:34pm] p7w: We haven't sorted that out.
>>> [1:34pm] maxcarlson: that's what I've been doing...
>>> [1:34pm] jgrandy: Typically we keep one bug, and just shift-
>>> select the additional release when the change is integrated.
>>> [1:34pm] maxcarlson: but there's only one field for the revision
>>> number.
>>> [1:34pm] jgrandy: It's a bit cumbersome, but works better than
>>> duping bugs all over...
>>> [1:34pm] maxcarlson: I suppose the subversion changes would be
>>> picked out...
>>> [1:34pm] p7w: Er, but fix-version can mean we want it fixed or it
>>> has been fixed
>>> [1:34pm] maxcarlson: (in the svn tab)
>>> [1:34pm] jgrandy: Separate with commas. Doesn't have to be
>>> machine readible.
>>> [1:35pm] p7w: we need to take this discussion off line
>>> [1:35pm] p7w: svn won't let you put in a comma
>>>
>>> --
>>> Regards,
>>> Max Carlson
>>> OpenLaszlo.org
>>
>
More information about the Laszlo-dev
mailing list