ANNOUNCE: Akka HTTP 3.0.0-RC1

[Konrad 'ktoso' Malawski]

Dear hakkers,

We are proud to announce the first Release Candidate of the Akka HTTP's "fully stable" release–the only missing, bit was the Routing DSLs, which we now deem stable enough to support for an extended period of time.

This release marks the first of the 3.0.0 series of this project and signifies a large step in terms of confidence in the library, as well as the move of Akka HTTP into its own repository. From now on Akka HTTP will be versioned separately from Akka “core”. This has been discussed at large with the community on akka-meta, and the akka-http repositories on github. Thank you very much for your input!

For more background why this move, please read “Akka HTTP - stable, growing and tons of opportunity” on akka-meta. While preparing In the meantime we have delivered a Proof-of-Concept of HTTP/2 for Akka HTTP and plan to continue this work later this year–community help is very much welcome on this front as well.

The documentation from now on will be available here:

Some noteworthy changes in the 3.0.0-RC1 (since it's move out from 2.4.11) release are:

• New lightbend/paradox powered documentation

• This will allow us to aggregate it together with Akka and other documentation, as well as link more easily to ScalaDoc pages

• Akka HTTP documentation will from now on live here: http://doc.akka.io/docs/akka-http/current/index.html

• We’ll work on a better theme for it very soon.

• Multipart is now correctly Binary MediaType (instead of WithOpenCharset) #398

• A new designated mailing-list and page for any critical security issues that might come up has been created: http://doc.akka.io/docs/akka-http/current/security.html

• Please follow the linked mailing list if you have production Akka systems, so you’ll be the first to know in case a security issue is found and fixed in Akka.

The plan regarding releasing a stable 3.0.0 is to wait a little bit for community feedback on the release candidates, and call a stable one no longer than a few weeks from now. We’re eagerly awaiting your feedback and can’t wait to ship the stable version of all of Akka HTTP’s modules!

Credits

A total 15 issues were closed since 2.4.11, most of the work was moving source code, documentation and issues to their new places.

The complete list of closed issues can be found on the 3.0.0-RC1 milestone on github.

For this release we had the help of 14 committers – thank you!

A special thanks to Jonas Fonseca who did a tremendously awesome job at migrating all the docs from sphinx (restructuredtext) to paradox (markdown), contributing features that the Akka docs needed to upstream Paradox–thanks a lot!

Credits:

commits added removed

  10   22489   24696 Jonas Fonseca

  10    1927     256 Johannes Rudolph

  10     849     412 Konrad Malawski

   4     448     136 Robert Budźko

   2      37      37 Bernard Leach

   2     107       7 Richard Imaoka

   2      26      24 Jakub Kozłowski

   1     145     101 Jan @gosubpl

   1     108     114 Derek Wyatt

   1      45      33 Wojciech Langiewicz

   1      49       0 @2beaucoup

   1       6       6 Markus Hauck

   1       1       1 Ian Forsey

   1       1       1 Johan Andrén

Happy hakking!

– The Akka Team

[Eric Swenson]

Congratulations!  Is the plan to remove the "experimental" from akka-http-experimental when this moves from RC to final?  -- Eric

[Konrad Malawski]

Yes, that's what all the fuss is about ;-)

In fact, in RC it's already removed: http://search.maven.org/#artifactdetails%7Ccom.typesafe.akka%7Cakka-http%7C3.0.0-RC1%7Cjar

For people not tracking this in detail: please note that all other modules other than "the DSL" have been stable for a long time already.

-- 

Konrad `ktoso` Malawski
Akka @ Lightbend

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[Eric Swenson]

I thought as much, but the documentation you just posted here:  http://doc.akka.io/docs/akka-http/current/scala/http/introduction.html still says:

Akka HTTP is provided in a separate jar file, to use it make sure to include the following dependency:

"com.typesafe.akka" %% "akka-http-experimental" % "3.0.0-RC1" 

— Eric

[Konrad Malawski]

Thanks for noticing, that's bug - fixing it right away.

-- 
Konrad `ktoso` Malawski
Akka @ Lightbend

[Konrad Malawski]

And fixed: https://github.com/akka/akka-http/commit/66adf848b57abdf6803b5713e1787fd23c00ccdb 

-- 

Konrad 'ktoso’ Malawski
Akka @ Lightbend

java.pl / geecon.org / krakowscala.pl / lambdakrk.pl / sckrk.com

You received this message because you are subscribed to a topic in the Google Groups "Akka User List" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/akka-user/Vk34d3pZ5Sc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to akka-user+...@googlegroups.com.

[Rafał Krzewski]

Hi,

I took a quick look at the new Akka HTTP artifacts published on Maven Central, and I've noticed that artifact names don't have Scala version suffix in them. Is this intentional?

Cheers,
Rafał

[Konrad Malawski]

Thanks for reporting.

We spotted this and have fixed the issue already: https://github.com/akka/akka-http/pull/409

The fixed artifacts are right now on their way to maven-central.

Happy hakking.

-- 

Konrad 'ktoso’ Malawski
Akka @ Lightbend
java.pl / geecon.org / krakowscala.pl / lambdakrk.pl / sckrk.com

--

[Sriram P]

Awesome! Its really a good news to get the stable release of akka-http. Thanks a lot for the great effort.

It will be great if some creates a sample application with the stable release for authentication, oauth2 and authorization.

Best Regards,

Sriram

[Gavin Baumanis]

Hi There,

Not sure what the process is to get documentation changes pushed to production - if it isn't automatic...

Nonetheless, the change is not reflected, yet, on the online documentation.