Metals: 0.1.0 (copper) release

Created on 2 Apr 2018  路  9Comments  路  Source: scalameta/metals

This issue is to track the release of the 0.1.0 (codename nickel) release:

  • [x] #218 Get the VSCode extension ready
  • [x] #221 Report error for non-scala 2.12 project
  • [x] #222 Move .compilerconfig to .metals/
  • [x] #219 Publish sbt-metals plugin
  • [x] #256 Document how to integrate with a new editor client
  • [x] #257 Document how to integrate with a new build tool
  • [x] #237 Update docs for 0.1.0
  • #239 Upgrade to Scalameta v3.7.0

Most helpful comment

I don't think so. The project status is highly unstable and it will radically change over the next few months. The fewer people use it now, the fast the project will move.

If you're curious enough, the website has fairly comprehensive docs on how to build the extension locally.

All 9 comments

We informally decided to cut a 0.1.0-M1 release once #219 is in

I suggest to cut 0.1.0-M2 before #239 (i.e. once #263 is merged). #239 will be a significant upgrade, so it's good to have a tag before it.

I agree 馃憤

I propose we cut a v0.1.0 with what we have in master right now, wdyt? The Scalameta v4 upgrade will wait for later since it is a big change.

Sounds good to me.

I just pushed the v0.1.0 tag. Will make sure the website is also published to Maven Central so the current state of this project is forever on Maven Central

Do you plan to publish the code extension too in the marketplace?

I don't think so. The project status is highly unstable and it will radically change over the next few months. The fewer people use it now, the fast the project will move.

If you're curious enough, the website has fairly comprehensive docs on how to build the extension locally.

Well, 0.1.0 is out, closing! 馃帀

Was this page helpful?
0 / 5 - 0 ratings