Kestrel: the way forward

Tim Altman, developer of Opera from the United States, wrote yesterday in the blog Opera Desktop Team:

We would like to give you information about Kestrel. Back in June, we announced that the first "weekly" [ assembly ] would appear "within a few weeks." With great regret, we have to admit the fact that we underestimated the amount of time we needed to give Kestrel the public. When we release a version with as many changes as in Kestrela, we would like our users to use it as much as possible so that we get good [ meaning “high-quality” ] reviews. We have strict quality standards that we have not yet reached. Then, in June, we thought that we would need only a few weeks to achieve the required level. However, while we were developing and testing more and more, we continued to find serious problems that we cannot, with a clear conscience, provide to our users.



When can you count on Kestrel's vaccine? Hard to say. It depends on whether we find new problems and, if so, how serious they are. I know that many of you can't wait to test what we have been developing for a year, and we also can't wait to hear your feedback. We all have to show patience in order for you to get a fairly stable assembly that makes this process worthwhile.

')

We still have a long way to go. Kestrel's original assemblies will not replace 9.23. There are many, many more problems that need to be fixed. For example, Kestrel is even far from stability 9.23, and Opera Post is not ready for use as a product. After the first build, releases should appear often, but not necessarily every week, or always on Fridays. We will try to fix as many problems as we can in each release, but not all the bugs sent to us in a week will be fixed next.

Lastly, Altman opened up a couple of new features in the field of personal activity (mail and RSS), however, not very revolutionary:



- in the main news feeds window (I don’t know how it is in Russian, sorry) all channels will be updated when you press F5, even if “their time has not come yet”.

- Fixed crap when View> Encoding (“View> Encoding”, as far as I can guess) did not change anything in messages.



We wait.