Pegjs: Release PEG.js 0.12.0

[futagoza]

The 0.11.0 release is near! Here are the remaining steps:

• [x] Upgrade all used libraries to their newest versions
• [ ] Drop support for
  
  
  
  • [ ] Node 6.x
  
  
  • [ ] Node 8.x
  
  
  • Internet Explorer
  
  
• [ ] Test Node.js support
  
  
  
  • [ ] 10.x
  
  
  • [ ] 12.x
  
  
  • [ ] 14.x _(Upcoming in 04/2020)_
  
  
• [ ] Test browser support (latest versions only)
  
  
  
  • [ ] Chrome
  
  
  • [x] Firefox
  
  
  • [ ] Opera
  
  
  • [ ] Safari
  
  
  • [ ] Edge
  
  
• [ ] Misc _(Optional)_
  
  
  
  • [ ] Update issue and pr templates for GitHub (example)
  
  
  • [ ] Update the wiki
  
  
  • [ ] Drop forum support; Encourge discussions in GitHun issues instead
  
  
  • [ ] More tests
  
  
  • [ ] Increase covereage
  
  
  • [ ] @pegjs/standalone
  
  
• [ ] Release!
  
  
  
  • [ ] Update CHANGELOG.md
  
  
  • [ ] Add note about the ill-fated 0.11.0 and it's eventual rewrite 😅
  
  
  • [ ] Update version to 0.12.0
  
  
  • [ ] Publish to NPM
  
  
  • [ ] Create a release on GitHub
  
  
  • [ ] Update website (#578)
  
  
  • [ ] Tweet
  
  

[futagoza]

@dmajda @Mingun

I've updated the CHANGELOG.md file, and before release I'm thinking of adding slightly more information for the major changes.

For now, I'm doing other stuff (including an overhaul of the website), but while I'm doing that I'de be grateful if you guys looked over the list and point me to anything I should change or you think I missed.

[dmajda]

Hi @futagoza! I don’t follow PEG.js development anymore, so I can’t really give much comments beside that the changelog looks really impressive and that I’m glad that you managed to get to the release. Keep up the good work!

[futagoza]

Thanks @dmajda

I don’t follow PEG.js development anymore

Sorry, should have been more clear; was actually referring to any changes you guys have made that I've forgotten to add, then I'de update the changelog (unless it's been removed of course 😅)

[Mingun]

As though nothing is forgotten. I left several comments under commit 87dcc13d0f87843d8eb5980f8fa1f493d13a7db0, generally with wishes to add references to specific issues

[futagoza]

@Mingun just pushed 4723176 with what you noted

[lindner]

Anything us folks can do to help finalize this release?

[srenault]

Any news on this?

[tilgovi]

@futagoza anything in particular you'd like help on? Seems like a few folks here might be willing and I see all the commit activity.

[GreenImp]

Is there any update on when v0.11.0 may be released?

[cr-roypeled]

@futagoza need help releasing the version?

[futagoza]

@lindner @srenault @tilgovi @GreenImp @cr-roypeled Sorry for the late reply 🙇

I'm kind of overloaded with my work right now but have been (on my time off) working on a rewrite of the PEG.js library written in TypeScript. It originally started off as a way to fix a bug in the new plugin system for 0.11 (the intention was to find the root of the problem and brainstorm a fix using TypeScripts type system) before finally releasing it, but sprawled out of control into a full-blown rewrite 😅 that is also changing the current AST and the library's API (including options) to enable a better development flow in general.

Due to this, I'm not comfortable with releasing 0.11 now with the current changes; or releasing it with the upcoming new changes as 0.11 because they eclipse what was intended for 0.11 personally. Sorry for the long wait folks 🙇

[StoneCypher]

buddy, i don't mean to be rude, but the version of peg on npm is more than three years old. saying "i'm scrapping and starting with an even bigger thing" is a problem

if you're three years in and scuttling the work, it's time to try a different development pattern. this is a very heavily used library and we're all waiting on important things that won't get merged

i just implemented typescript support against 11. it took me about an hour. i don't know whether to put it up, because i don't think you're going to merge 11.

i could write it against 10 in the same hour. you could publish 0.10.1, with support for es modules and typescript, and this project could immediately go back to being healthy again.

we really don't want these big overarching redesigns blocking the library for three years.

we need this library to be back in a place where patches can be committed and published again.

are you willing to accept patches against 10? that's the right thing to do here.

please let this go back to being a healthy community project. either pick that 0.10.0 is accepting patches, or merge and publish 0.11.0.

let us help. don't leave the library in a state where nobody but you can work.

[polgfred]

This is the way you treat a personal itch-scratching project, not a project that other people depend on.