How did you spend $500 on dinner for 9 people? I hosted Christmas dinner for my family with about 10 adults and 10 kids, and it cost at most $200 divided between 5 families, alcohol included.
Dinner for twenty people at $200 is farcical in the US unless your family owns a farm or something. Going to need more details because I'm inclined to say that's bullshit.
Beer and liquor alone would blow past that figure.
No farm is needed. It's not that hard. I spent about: $25 on a chicken dish (chicken from Costco + ingredients), $15 for baked mac & cheese (ingredients from Meijer), $20 on ciders, $40 on 2 bottles of Cherry Republic wine. The other family members: $20 on raw vegetables and cheese platter; $20 on fruit; $10 potato dish; $10 vegetable dish; $15 on dessert; $15 on salad. Oh and $2 on juice boxes for the little kids (~4 from a juice box 40 pack from Costco). I'm estimating what the others spent, but that's what it would cost me to make the same dishes. That totals to $192.
If your version of hosting is "let's outsource it and just open the wallet", then, yes, sure, you can spend a lot of money. It ain't hosting, though. You failed the "what if I just replaced you with a bank account" test.
All I can say is I hate when projects just lazily list every pull request for its change log / release notes. It makes it very difficult to discover what breaking changes there are.
That has been my concern as well. The script I wrote tries to bucket entries into categories, including "Backward Incompatible Change" so those are easier to spot. Since it is automated I am trading some accuracy for time saved, which seemed like the only practical choice for me, since I had to backfill a lot of history, but it’s been surprisingly decent so far.
I am also planning to add some PR templates so contributors include the context up front, which should make any release note generation more accurate.
Are you using any tooling to help with changelog curration? I know towncrier is all about fragments, so contributors must had write a brief summary of their contribution, which would be more in-line with your preference.
Not related really, as you can (and should) publish BREAKING.md separately. Release notes should inform more about new stuff than the update process. Usually PRs have details, so release notes can be easily automated. Migrations, on the other hand…
+1 on separating "how to upgrade" due to breaking changes from "what’s new". A dedicated BREAKING.md / MIGRATIONS.md is a really good idea.
One thing I am trying to do is make the generator surface breaking/migration items explicitly, but I still think anything that requires human judgment (migration steps, caveats) should be hand-curated in a dedicated document like you suggested.
Why would I regret it? I work on open source projects to satisfy a particular itch. I can work on an interesting topic in my free time and drop it if I get bored. I don't have the stress of worrying about deadlines or monetization. The fact that it sits out in the open rather than hidden away on some dusty hard drive is a perk because at least a few people have found them useful. If you can utilize their features to make money yourself, good for you. Why should I care outside of greed or envy?
The stale-bots are even worse than that. The reporter may have responded quickly, and the bug may be acknowledged as real. But if there's simply no activity in the issue for the month following, it will be closed.
reply