4 ms·

I'm a bit out of the loop, is there an article explaining the death and rebirth of jq development, alluded to in the release notes?

defrost 3y ago
* First release of jq in 5 years 114 points by drewda 62 days ago | past | 27 comments https://news.ycombinator.com/item?id=36951830 https://news.ycombinator.com/item?id=36951830 * jq 1.7 434 points by wwader 25 days ago | past | 206 comments https://news.ycombinator.com/item?id=37412698 https://news.ycombinator.com/item?id=37412698
- isuckatcoding 3y ago
  I’m not sure this answers the question. I was expecting some post about someone like the main contributor quitting or something.
  - deleted 3y ago
    [deleted]
  - defrost 3y ago
    To the best of my recollection no one in the former HN comment threads expanded on the long hiatus .. suggesting an absence of any real drama. Which leaves us with the RC release candidate Announcement: After a five year hiatus we're back with a GitHub organization, with new admins and new maintainers who have brought a great deal of energy to make a long-awaited and long-needed new release. https://github.com/jqlang/jq/issues/2802 https://github.com/jqlang/jq/issues/2802 and the 1.7 release Announcement: It's been almost five years since the release of jq 1.6. Recently we have had a great influx of contributor and maintainer energy. We now have 12 maintainers (up from 3), with about 4 or 5 active maintainers (up from 0), we have 8 admins with several active admins, and several owners at least two of whom are active. As a result the project will not again have such a long hiatus. https://github.com/jqlang/jq/issues/2876 https://github.com/jqlang/jq/issues/2876 Either any dirty laundry is well buried or (more likely) this was simply a case of the original implementers hitting some plateau of achievement and fading away leaving JQ to eventually be picked up by others. Others would have to chime in, I have nothing I can add.
    - naniwaduni 3y ago
      As far as I'm aware, there was no real drama, just Maintainers Having Lives. There was actually some progress being made in the intervening time on the timescale of months, it just never made it into a release—some distros actually took to shipping HEAD iirc.

defrost 3y ago

* First release of jq in 5 years 114 points by drewda 62 days ago | past | 27 comments https://news.ycombinator.com/item?id=36951830 https://news.ycombinator.com/item?id=36951830 * jq 1.7 434 points by wwader 25 days ago | past | 206 comments https://news.ycombinator.com/item?id=37412698 https://news.ycombinator.com/item?id=37412698

isuckatcoding 3y ago
I’m not sure this answers the question. I was expecting some post about someone like the main contributor quitting or something.
- deleted 3y ago
  [deleted]
- defrost 3y ago
  To the best of my recollection no one in the former HN comment threads expanded on the long hiatus .. suggesting an absence of any real drama. Which leaves us with the RC release candidate Announcement: After a five year hiatus we're back with a GitHub organization, with new admins and new maintainers who have brought a great deal of energy to make a long-awaited and long-needed new release. https://github.com/jqlang/jq/issues/2802 https://github.com/jqlang/jq/issues/2802 and the 1.7 release Announcement: It's been almost five years since the release of jq 1.6. Recently we have had a great influx of contributor and maintainer energy. We now have 12 maintainers (up from 3), with about 4 or 5 active maintainers (up from 0), we have 8 admins with several active admins, and several owners at least two of whom are active. As a result the project will not again have such a long hiatus. https://github.com/jqlang/jq/issues/2876 https://github.com/jqlang/jq/issues/2876 Either any dirty laundry is well buried or (more likely) this was simply a case of the original implementers hitting some plateau of achievement and fading away leaving JQ to eventually be picked up by others. Others would have to chime in, I have nothing I can add.
  - naniwaduni 3y ago
    As far as I'm aware, there was no real drama, just Maintainers Having Lives. There was actually some progress being made in the intervening time on the timescale of months, it just never made it into a release—some distros actually took to shipping HEAD iirc.