Comment 1 for bug 635890

Not a complaint ... BUT ...

Can we identify the need to handle exceptions/signals in a blueprint
before tracking bugs on vaporware? I'd like to get the rpm-embed-ruby blueprint targeted
at some milestone somehow.

In other words, a forward looking "feature" would be
    There's a need to handle exceptions/signals with embedded ruby ...
instead of the defect
    The current implementation of embedded Ruby in rpmio/rpmruby.c does not handle errors

Absolutely there has been no attempt to handle exceptions attempted yet.

Note that blueprints can also be linked to bugs if you wish.

There's no clear answer ... just I'd like to see forward looking feature approaches
rather than backward defect/bug fixing.