Tag flux-sched v0.4.0

[grondo]

We're preparing an 0.7.0 tag for flux-core. We'll need a new flux-sched release to go along with this version.

[grondo]

Ok, I missed tagging flux-sched v0.4.0 with the v0.7.0 version of flux-core, but we're preparing v0.8.0 of flux-core now, and we'll need a version of flux-sched to go with it.

Ok to tag v0.4.0 of flux-sched after the flux-core release is done?

Here's what I have for changes since v0.3.0:

flux-sched version 0.4.0 - 2016-08-24

Fixes

• Fix allocation of cores unevenly across nodes (count cores per node when building JSC request #226)
• Fixes and updates to track latest libflux-core API changes
  (sim: track changes in flux-core to jansson functions #255, simulator: update KVS lookup functions #253, simulator: use future-based RPC API #246, simulator: Fix flux_request_decode() usage #238, simulator: Update for recent kvs API changes #234)
• simulator: fix and re-enable sim integration tests (Fix simulator and re-enable sim integration tests #250)
• Fix autoreconf when using side-installed autotools (fix autoreconf when using side-installed versions of autotools #243)
• flux-waitjob: fixes to avoid flux-core issue Fix another typo #1027 (avoid flux-core bug 1027 #244)
• Other fixes (Misc fixes #227, Ats fixes, performance and memory leaks #231)

New features

• simulator: add ISO time parsing to job traces (Added ISO time parsing to job traces #260)
• resrc: add resource API context support (resrc: Add resource API context support #236)

Cleanup

• simulator: refactor, cleanup, and ensure proper initialization.
  (sched/simulator: Add missing sim_state = NULL assignments #240, Fix simulator and re-enable sim integration tests #250)

[dongahn]

Yes. And from my perspectuve, the readme LGTM except for 2016 vs 2017. Thank you @ grondo!

[grondo]

the readme LGTM except for 2016 vs 2017.

Thanks for catching that

[grondo]

Ok, v0.4.0 released and RPMs are building locally for TOSS3 now.