mhoyeI felt this in my teeth.
Lemme lean into this a little harder: JIRA is what companies buy when they should have invested in manager training five years ago.
Benjamin Smedberg@mhoye very curious about this because I can’t tell if you mean jira in particular or bug tracking systems in general.
@bsmedberg Every project needs issue trackers, but describing Jira as an issue tracker is like describing McDonald's as a restaurant. It's a organizational culture and language least-common-denominator normalization tool whose endpoint happens to resemble an issue tracker.
A well-functioning issue tracker is a core part of making an org visible and legible to itself; adopting a tool that forces every part of an org to speak the same operational language is the lowest-trust path to that goal.
Stefanie Janine Stölting@mhoye @bsmedberg #PostgreSQL doesn't use any bug tracker. There's only a mailing list.
Seems to work pretty well in the last 26 years.
Seems to work pretty well in the last 26 years.
Oliver Maksimović@sjstoelting that's interesting. On the other hand, what works for one org may not work for others. I'm not defending Jira, it's a pile of trash. But, email for issue tracking / project management is (to me) as bad as Jira 😦
Tito Ciuro@oliver @sjstoelting But how do you manage priorities, manage bug state (proposal, in progress, verify, complete, etc), etc? Just replying to an issue helps keep track everything about the issue, but not within its ecosystem. Curious how you do that per release. There’s got to be another doc keeping track of it, no?
@titociuro @oliver It's very well documented. PostgreSQL has a thing called CommitFest https://wiki.postgresql.org/wiki/CommitFest_Checklist?ref=timescale-blog
A list of previous and coming CommitFests can be found here: https://wiki.postgresql.org/wiki/CommitFest_Checklist?ref=timescale-blog
This is for new features. Bug fixes are done on email lists.
@sjstoelting @oliver Amazing. Such detail! My hat off to you, team.