The Katana project for the ASP.NET 4.x Microsoft.Owin components has now moved to aspnet/AspNetKatana from CodePlex. This includes the source code, wiki content, and some issues.
This move was made to unify the engineering infrastructure with other ASP.NET projects. The MyGet feeds have also been moved as part of this effort to https://dotnet.myget.org/f/katana-dev/ (nightly builds) and https://dotnet.myget.org/f/katana-release/ (stabilization builds).
We’re also preparing a Microsoft.Owin 4.0.0 release that targets common customer issues (https://github.com/aspnet/AspNetKatana/issues?utf8=%E2%9C%93&q=is%3Aissue%20milestone%3A4.0.0-alpha1%20). Bugs addressed in this release will have their tracking issues migrated from CodePlex. We will not proactively migrate other old bugs from CodePlex. Please open new issues on GitHub if you find something that needs our attention.
You can stay up-to-date with the Katana project by checking out the Katana Roadmap.
The Katana project for the ASP.NET 4.x Microsoft.Owin components has now moved to aspnet/AspNetKatana from CodePlex. This includes the source code, wiki content, and some issues.
This move was made to unify the engineering infrastructure with other ASP.NET projects. The MyGet feeds have also been moved as part of this effort to https://dotnet.myget.org/f/katana-dev/ (nightly builds) and https://dotnet.myget.org/f/katana-release/ (stabilization builds).
We’re also preparing a Microsoft.Owin 4.0.0 release that targets common customer issues (https://github.com/aspnet/AspNetKatana/issues?utf8=%E2%9C%93&q=is%3Aissue%20milestone%3A4.0.0-alpha1%20). Bugs addressed in this release will have their tracking issues migrated from CodePlex. We will not proactively migrate other old bugs from CodePlex. Please open new issues on GitHub if you find something that needs our attention.
You can stay up-to-date with the Katana project by checking out the Katana Roadmap.