Can we release a new version?

[wtagain]

The lasted released version is 9 months ago，during this time， some issues have been fixed，so can we release a new version?

[wtagain]

@Jolg42 Hi, can we release a new version?

[Connum]

An additional year later, I'd love to see the support for more lookup tables I added released as well! :)

[Jolg42]

Hi there!
I'll try to check that in the next days, though I didn't follow what happened here in a while and could use help if someone wants to be a maintainer 😃

[saragee3]

Bumping this — will there be a new release soon? Looks like there are some commits after 1.3.4 that addresses performance improvements, additional glyph support, etc. Thanks!

[ILOVEPIE]

@Jolg42 If this project needs a maintainer, I'd be happy to help, I've got a project that depends on this one and really need some of these features and PRs to be merged.

[ILOVEPIE]

If I don't hear back from @Jolg42 within a week or two on this, I'll just continue development under my organization's fork.

[Connum]

If I don't hear back from @Jolg42 within a week or two on this, I'll just continue development under my organization's fork.

That would be a real shame!

[ILOVEPIE]

If I don't hear back from @Jolg42 within a week or two on this, I'll just continue development under my organization's fork.

That would be a real shame!

Why? It would still be open source.

[Connum]

Why? It would still be open source.

Sure, but this could be a chance to breathe new life into this seemingly abandoned project, and most people will probably not be looking at the forks, so having a new maintainer would be preferable to abandoning the main repo and moving active development to a lesser known fork.

[ILOVEPIE]

Still waiting on @Jolg42, he apparently saw a message I sent him on mastodon, but so far no movement yet.

[ILOVEPIE]

Seeing as it's been several months with no movement, I will be continuing development of opentype.js on my fork which is available here. If and when @Jolg42 returns I would be more than happy to shift development back to the main repository, but it looks like he's abandoned this project so it doesn't seem likely.

I will need some co-maintainers at least temporarily to help go through old PRs and apply ones that are worth applying, anyone who wishes to help with that process can reply to this message, or contact me via discord where i go by ILOVEPIE#9201.

[Connum]

That's great news!
A notice at the top of the README in your fork might be a good idea, stating that your fork intends to take over active development since the original is abandoned.
My PRs should be good to go. I'd love to help, but I have very limited to no time to work on any open source projects right now. You can add me as a co maintainer if you like, but I can't promise I'll be of any help really for the foreseeable future.

[Jolg42]

See suggestion in #541 for npm publish

[Zireael07]

Is a new release coming?

[Connum]

Is a new release coming?

Yes, when it's done. 😉

But you can always build your own dist files from the master branch or install it as a git dependency via npm.

[ILOVEPIE]

we should nail down what will be in 2.0.0