I've likewise read it and give it a +1.
On Tuesday, October 9, 2012 6:08:56 AM UTC-5, Andreas Håkansson wrote:
I said the same thing back when OWIN first reached, if only for a brief moment, 1.0, but I am going to say it again. Why the rush? Why put something at 1.0 that's not even been given proper testing in the wild? The way I see it, the members of this user group pretty much are in control of the entire echosystem of frameworks and servers that would be first to implement the specification and after that, and only then, will the general public start to use OWIN (no matter what version the specification is at) and write middleware for it. When it reaches the wider audience there are bound to be a lot of edge cases pop up that will (hopefully) have an impact on the design as it moves forward
The RC is more or less an "private club release candidate" because John Doe's not taken it for a spin.. a selective few has? Am I missing something here? =)
I see what you are saying Andreas, but I would also ask why leave it at 0.X for a really long time when we really do some things running on this? I think the model is (now) very simple. We also have a solid versioning strategy, so we can always version it later. This is also a spec; the implementations in Gate, Katana, etc. can all be versioned and fixed independently. I'm happy to have a flag shoved in the ground at this point. I think that may be necessary broader adoption in the Microsoft space, despite that not being the case in other dev cultures.