Remove the macro section

Author: anatoliykmetyuk

docs/blog/_posts/2020-06-16-25th-dotty-milestone-release.md

@@ -15,23 +15,6 @@ Alternatively, you can try this version of Scala online via [Scastie](https://sc
 Enjoy the ride🚀!
 
 <!--more-->
-# Progress on macro compatibility with Scala 2
-One of the most challenging parts of the migration from Scala 2 to Scala 3 are macros. Scala 3 has re-implementing the entire metaprogramming mechanism from scratch, and so all the Scala 2 macros must also be rewritten from scratch using the Scala 3 metaprogramming capabilities.
-
-Under these conditions, cross-compilation of a library between Scala 2 and Scala 3 also becomes more challenging since you need to split your sources between the two versions.
-
-To address this challenge, we are currently working on a solution to allow macro definitions of Scala 2 and Scala 3 macros to reside in the same file. This co-habitation will look as follows:
-
-```scala
-object Macro1 {
-  import scala.language.experimental.macros
-  def lineNumber: Int = macro LineNumberMacroScala2.thisLineNumberImpl
-  inline def lineNumber: Int = ${ LineNumberMacroScala3.thisLineNumberExpr }
-}
-```
-
-Currently, this is a work in progress. You can dive deeper into the current state of things by looking at PR [#8811](https://github.com/lampepfl/dotty/pull/8811).
-
 # Avoid excessive slowdowns when suggesting missing imports in error messages
 Dotty brings to the user an enhanced error reporting when it comes to programming with givens. This better error reporting, however, proved to be a trade-off. Sometimes it takes an unreasonable amount of time and space to compute a quality suggestion to the end user.