Add compat-table/babel/core-js release steps to RELEASE-STEPS.md.

[phulin]

As requested, this PR just adds steps for updating compat-table and babel to the release documentation. I've already filed a PR against compat-table and will deal with babel when that gets merged:

compat-table/compat-table#1786

Closes #661

[zloirock]

It should be added also to core-js, see zloirock/core-js#942

[phulin]

Of course, thank you!

[phulin]

@zloirock Added instructions, although they're honestly a little dense. If you have an obvious better solution, I'd be curious to hear it.

[zloirock]

You can use core-js-compat/data.json when you built core-js.

[nicolo-ribaudo]

Some tests might need to be updated. I suggest replacing npm run build with make bootstrap, and then add an OVERWRITE=true yarn jest step to update the fixtures if necessary.

[phulin]

Great, thanks - something is wrong here which I figure is better to discuss in the babel PR.

[gbrail]

This looks fine with me, but I see some discussion about the specific steps -- can you resolve the comments above or let me know if you think it's good to go anyway? Thanks!

[phulin]

I think this is good to go now. There's some further work that could be done to make regenerating the core-js info easier, but that can easily happen the next time we need to do this based on these instructions.

[p-bakker]

Would it make sense to at least write in a comment here exactly what improvements could be made and then add a little note in RELEASE-STEPS.MD referring to that comment, as I think for most of the Rhino contributors here things might not be as clear as they are for you?

[p-bakker]

@phulin Any change you can resolve the comments on this PR and have a look at my previous comment, to see if it makes sense to do that or not?

[tonygermano]

@phulin Do you know what would be required to have Rhino taken off of the "Obsolete platform" list?

[p-bakker]

FYI: compat-table/compat-table#1687

So maybe the answer to your question is: convincing @ljharb it is not obsolete :-)

[ljharb]

@p-bakker to be fair, when i made that comment there was no indication that there’d ever be a new and/or updated version of rhino.

if you’re releasing new versions that implement most of the living JS standard, then obv the new versions wouldn’t be obsolete.

[p-bakker]

@ljharb point taken :-)

We do have a bit of a backlog of things to implement to get back up to standard (which is being worked on, albeit slowly), but the project is far from dead for a usage perspective

So, fair to say that is we put out a couple of releases that close the gap to the latest EcmaScript version, we should ring the bell to get Rhino taken off of the 'obsolete platform' list?

[ljharb]

That sounds like a fine plan to me.

(usage doesn’t matter all that much, IE 9 still gets plenty of usage, but it’s still obsolete)

[phulin]

@phulin Any change you can resolve the comments on this PR and have a look at my previous comment, to see if it makes sense to do that or not?

Yep, I have been meaning to do this and just haven't gotten around to it. It's a good point, it's all in my head right now and should get written down. Thanks.

[p-bakker]

@phulin dont mean to push, but any chance you could wrap this one up so it can be merged? Will shortly want to build on top of it

[phulin]

@phulin dont mean to push, but any chance you could wrap this one up so it can be merged? Will shortly want to build on top of it

Added some inline notes on how one could contribute back to core-js to make it easier.

[phulin]

Not sure what is going on w/ the CI...

[p-bakker]

Tnx, looks good to me. @rbri, @gbrail can you give this a quick look over and merge?

Not sure what is going on w/ the CI...

First-time committer, CI had to be launched manually

[gbrail]

There was a small problem with duplicating the last few lines of RELEASE-STEPS so I squashed and merged this manually. Thanks for updating this!