Improving release process

[laughedelic]

Current release process (in the upcoming v0.4.0):

          Seq[ReleaseStep](
            genDocsForRelease
          , checkSnapshotDependencies
          , inquireVersions
          , checkReleaseNotes
          , runTest
          , setReleaseVersion
          , commitReleaseVersion
          , tagRelease
          , publishArtifacts
          , setNextVersion
          , pushChanges
          )

proposed by @evdokim, we should try to publish earlier and fail everything if it fails. Second thing, is that generated docs should be committed (like version):

          Seq[ReleaseStep](
            // check artifact generation, smth like 'package'
          , genDocsForRelease // and commit if it's changed
          , checkSnapshotDependencies
          , inquireVersions
          , checkReleaseNotes
          , runTest
            // do 'set version in ThisBuild := ...' for publishing
          , publishArtifacts // <-- moved here
            // if it succeeds, continue:
          , setReleaseVersion
          , commitReleaseVersion
          , tagRelease
          , setNextVersion
          , pushChanges
          )

[laughedelic]

So, now release process looks like this:

          checkSnapshotDependencies // no snapshot deps in release
          , checkGHCreds            // check that we can publish Github release
          , checkPackaging          // try to package the artifacts
          , genDocsAndCommit        // generate literator docs and commit if needed
          , runTest                 // compile and test
          , inquireVersions         // ask about release version and the next one
          , tempSetVersion          // set the chosed version for publishing
          , publishArtifacts        // try to publish artifacts
          , setReleaseVersion       // if it was ok, set the version finally
          , commitReleaseVersion    // and commit it
          , tagRelease              // and make a tag
          , releaseOnGHStep         // and publish notes on github
          , setNextVersion          // bump the version
          , commitNextVersion       // commit it
          , pushChanges             // and push everything to github

Guys, @eparejatobes @evdokim, please, check it and give me some feedback — may be something is missing or you think that the order is wrong.
We discussed it some time ago, and I really want to improve it.

[eparejatobes]

First release a working version for Windows, then we will discuss this!

[laughedelic]

A working version of what?

[eparejatobes]

Of this

[laughedelic]

I don't understand, what is not working here on windows? (I can't check)
(do you mean just this: laughedelic/literator#12 ? then it's fixed and released)

[eparejatobes]

Updating sbt-release etc

[laughedelic]

here: #9

[eparejatobes]

@laughedelic what do you mean? that PR is not merged

[laughedelic]

yes, because it depends on this PR. I mean that sbt-release and literator are updated to the version with those windows-specific fixes.

[eparejatobes]

@laughedelic really I don't understand what you are saying. This is a really simple thing:

1. we have issues using this in Windows
2. they can be fixed by updating some deps

So we just go and update those things and then we can think about all sort of improvements, new features, etc.

I'm missing something?

[laughedelic]

thanks for saying it directly. because for me it was not obvious

[eparejatobes]

anyway let's use this for its purpose, discuss the release process/steps

[eparejatobes]

I'm OK with it. @evdokim ?

[laughedelic]

@eparejatobes here you go: v0.3.2

[eparejatobes]

cool thanks