-
|
I know Daniel is busy but it seems strange to me that somebody that has access to that kind of PA does not use it to move this project forward. There are known issues being reported and still no updates/releases. Please bear with me, I'm asking this with all possible respect. I'm just curious (and possibly spoiled from other open source projects). Thank you Daniel for everything you do. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
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 or after it. What's encouraging is that Daniel has addressed this directly. In a reply on #1112 he said the next release will be "migrating to a fast-release system that's far more collaborative, where I work with the public repo the same way everyone else does. Meaning through public code pushes." If that lands, threads like this one stop being necessary. Until then, I wouldn't read the silence as the project being abandoned. It's just where we are in the cycle. |
Beta Was this translation helpful? Give feedback.
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…