On Wed, Oct 2, 2013 at 4:16 PM, Jacek Cała <jacek.c...@gmail.com> wrote:
> I'd say it is as simple as it sounds: it just blocks another ticket from
> closing, meaning that when you look at the view page and see some blockers
> you may want first to check whether they've already been closed.
>
In that case, what happens when i write:
abcdef, defabc, deadbeef
in the field (possibly without commas, or a mixture). Ignoring the
complication of having to parse/grok the content (it's a minor
complication, granted, but parsing text is always at least a slight
annoyance), there's another problem: DVCS. i edit the field, then you close
the ticket in your copy before i sync my changes to the blocker list. So
we've now got a closed ticket with open blockers. i don't see how that
could be made to work (meaning "automatically enforced") 100% reliably in a
DVCS.
I didn't expect it to be a "rocket" feature but exactly a client-side
> customization others {may/may not} find useful.
>
i don't deny that, i'm just thinking more in terms of "ratio of code to
users," and so far you're the only(?) one who's expressed an interest in
blockers.
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
