Re Nightly Builds of the Trunk - What is worth reporting as a 'bug'?

Now that the Nightly Builds are becoming practically nightly and remarkable progress toward 2.0 is ongoing, when is worthwhile -- if ever -- to report consistent and predictable misbehaviors as 'bugs'? I'm confused, as the readme.txt file urges feedback about such. However, it seems obvious that some of what *could* be described would surely be known already to the programmers and perhaps even deliberate for some specific reason as development proceeds.

Example: I recently mentioned that repositioning of dynamic signs doesn't 'stick' when a file is saved and re-opened. The same is true of fermatas, too, and probably other symbols. Something else maybe worth mentioning is that after a slur is edited, it continues to be selected until I double-click it yet again. The same is true of hairpins. And if one inadvertently selects a different object and makes adjustments to it in the Inspector while the aforementioned previous object remains selected, the program will always crash. Yet another thing is that Reload isn't functional, and crashes the program instead.

Is any of this important? Or is it stuff that's in the category of 'known issues' and will all come out in the wash before there's an official pre-release version of 2.0? In the latter case, *what* would be considered a legitimate 'bug' worth reporting in a Nightly Build which is by nature prone to misbehavior?

Apologies in advance if this seems like overanalyzing, but I do believe some guidelines would be nice -- if it's possible to formulate them even in general terms.