Skip to content
Discussion options

You must be logged in to vote

Hi @bak3r, you're not the only one wondering, so it's worth saying out loud.

From the outside the pattern looks like this: Daniel develops PAI mostly on his own private instance day to day, and during those stretches the public repo goes quiet. Then a major version lands, and because each release is closer to a rewrite than an increment, it sets off a wave of issues and PRs. That activity tapers off, the repo goes quiet again, and the cycle repeats.

It's an impressive amount of work, and the releases themselves are genuinely good. But it does make the public repo hard to build on. Known issues sit between cycles with no clear answer on whether they'll be picked up before the next big drop…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by bak3r
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants