These unstable release tags will probably never have actual release nodes, and they are before the beta, or even alpha releases, so you generally shouldn't use them on your production site. But, if you're up for an experiment in the bleeding of bleeding edge, try it out. I'm not too sure if they upgrade path will be supported, so we'll have to wait and see. I think I'll wait for the Alpha releases to update my site to Drupal 7 to be on the safe side.
There was some talk recently about releasing pre-alpha versions of Drupal 7 for development and testing purposes and this got me thinking about the actual Drupal 7 code freeze. For those of you who are "in the cold" and don't know what a code freeze is (horrible pun, sorry), it's a given amount of time where features are denied from going into Drupal. Although it's sad to see additional features not be able to go into Drupal, it gives the developers a bit of time to fix bugs and optimize performance before the official releases go out.
If you have a look at Dries' Drupal 7 Timeline, you see that he predicts a November 15th code freeze if we have full test coverage. Now, if you have a look at the Drupal 7 test coverage report, you can see that we're pretty close! So, assuming that we get the three month code freeze, that means we only have about two months left to get all the features and awesomeness that we so ever want in Drupal 7. What awesomeness is missing from Drupal 7, you ask?
Here are the items remaining on my wish list:
Although Drupal 7 has already achieved its awesomeness status, having these items added to its mastery would absolutely blow my mind.