any objections to my cutting nak/chalk releases?

[David Hall]

Just to sync with Breeze.

[Elias Ponvert]

I've been meaning to, but you go ahead. I still need to get credentials with Maven Central. Thanks!

[David Hall]

Ok. It's considered best practice to have cross paths in the jar names, so I'm going to do that too.

[David Hall]

ok, chalk 1.3.2 and nak 1.2.1 are released.

-- David

[Elias Ponvert]

Thanks! Couple questions:

- Cross paths in the jar names? not sure what you mean 

- I'm not seeing new SBT versions or associated tags. Any objection to me doing that?

[David Hall]

On Thu, May 29, 2014 at 7:41 AM, Elias Ponvert <pon...@gmail.com> wrote:

Thanks! Couple questions:

- Cross paths in the jar names? not sure what you mean 

Most Scala projects have the scala version in the artifact name. (e.g. breeze_2.10, breeze_2.11) (This is source of the "org.scalanlp" %% "breeze" versus "org.scalanlp" % "chalk".) For whatever reason, it was decided to not do this for Chalk and Nak. Best practice is to include it, so I did.

 

- I'm not seeing new SBT versions or associated tags. Any objection to me doing that?

Looks like I forgot to push them for nak, Chalk is here:

 https://github.com/scalanlp/chalk/tree/releases/v1.3.2

I'll push the tags when I'm back at that computer.

[Elias Ponvert]

Gotcha. Awesome, thanks!