I don't have a lot of time for Views 1 right now, but there are a couple of bugs in Views 1.6 that really need to be fixed. I've been hoping for a year now that someone would volunteer to write these patches, but no one has.
Ironically, both of the patches I need relate to taxonomy, and both of these problems exist because Views is trying to use Drupal's API but the API is simply not adequate to Views' needs.
In case #1, Views is trying to re-use taxonomy_form, and unfortunately embeds the entire form into the views data. This is incredibly bad and wrong. It needs to not re-use taxonomy_form so that it can use a callback to fetch a list of possible terms (or use the autocomplete field, as appropriate).
In case #2, Views is using taxonomy api to get a list of vocabularies and terms, but because this gets run through db_rewrite_sql, if the current user doesn't have access to vocabularies/terms due to a module, then these vocabularies and terms are excluded from the views data, which then causes views that actually utilize them to suddenly and mysteriously fail. This can be alleviated by not using the taxonomy module API and fetching directly from the database, in order to avoid db_rewrite_sql issues.
These are the 2 issues that really prevent a Views 1.7 from happening.

Comments
Issue URLs
#1: http://drupal.org/node/272288
#2: http://drupal.org/node/272289
Add new comment