hey all, after the "polonius work week" I'm going to be a bit swamped at work, and since Niko won't be attending either, I propose we do the updates async, what do you think ?
Not sure how far I am going to get but I'd like to:
polonius#137 seems ready, merging :tada:
I'll prepare a version-bump PR, maybe Matthew or Albin can review it whenever they have the time (I'm not pinging either of you, it's late :) — and will try to publish ( :fingers_crossed:)
@Jake Goulding I was also confused by this. I can also bump to a "real" 0.6 and change the releases.md so that those 2 unreleased but documented versions are under the 0.6 heading if you find it'd be better/clearer
(that was re: https://github.com/rust-lang/polonius/pull/140#discussion_r350433885 for anyone following at home)
I dunno if either is more correct. More like "what went wrong that those were never published but someone changed the changelog"?
probably just a mistake in forgetting to bump all the cargo.tomls when trying to update polonius-engine (which is the only crate we need to publish)
if neither is more correct than the other, at least 0.8 will start fresh :)
(I don't even think the parser's 0.3 was published on crates.io but was indeed bumped in the repo)
@Jake Goulding moved to 0.6 instead, and fixed the previously erroneous releases.md, wdyt?
@Matthew Jasper thanks
ah I don't think we're able to publish, seems like only niko is an owner