Hi Javor, many thanks for the very detailed explanation. It helps a lot! On Sun, 2008-06-29 at 19:43 +0300, Javor Nikolov wrote:
> C) Current status is NEW and a mixed-case "Status" message (Status 7: > RESOLVED FIXED). Then I get error message: > ** Scmbug error 7: Bug '7' is in the 'NEW' state, instead of the > 'ASSIGNED' or 'REOPENED' states. > > (and as a result the commit to svn fails, and no changes in bugzilla either) > > Why? I agree that transition from NEW to RESOLVED FIXED is not a valid > one but we don't have an all-lower-case "status" here. It shouldn't be > processed like status change at all. Shouldn't it be processed like in > A as a regular svn log text - i.e. "Status: ..." to remain just a part > of bugzilla comment log. The commit is forbidden here because of a different reason. The status transition from NEW to RESOLVED FIXED is a valid one. But committing a log message against a bug that is in the NEW state is not valid because policy open_bug_state is enabled: http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-26-5/manual/html-single/manual.html#VERIFICATION-CHECKS-OPEN-BUG-STATE Does this make sense ?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
