+972 52-548-6969
RavenDB has the best users
time to read 1 min | 51 words
Talk about making my job easy. Thank you Barry, and I am sorry it took me 17 minutes to get the fix out.
FUTURE POSTS
- Optimizing the cost of clearing a set - 4 hours from now
- Scaling HNSW in RavenDB: Optimizing for inadequate hardware - 2 days from now
There are posts all the way to May 14, 2025
RECENT SERIES
-
RavenDB News
(2):
02 May 2025 - May 2025 -
Recording
(15):
30 Apr 2025 - Practical AI Integration with RavenDB -
Production Postmortem
(52):
07 Apr 2025 - The race condition in the interlock -
RavenDB
(13):
02 Apr 2025 - .NET Aspire integration -
RavenDB 7.1
(6):
18 Mar 2025 - One IO Ring to rule them all
RECENT COMMENTS
-
By Samyon Ristov on The null check that didn't check for nulls
-
By Johannes Egger on The null check that didn't check for nulls
-
By riccardo on The null check that didn't check for nulls
-
By Chris B on The null check that didn't check for nulls
-
By Tim on When racing the Heisenbug, code quality goes out the Windows
Syndication
| Main feed | |
| Comments feed |
Comments
You've got the best business model in the world, don't pay developers just have the community fix your product! You should start offering reduced licenses for people who find/fix bugs. That should iron out a few more kinks in the product.
@jon I hope you were being sarcastic. Most of these types of bugs are edge cases that don't show up outside of real world use. Oren has a great track record of fixing these bugs quickly. Even quicker if the customer provides a failing test. If I'm not mistaken a bug report is NOT a bug fix.
@Killman of course!
There should actually be a strong incentive for users to do this. If they provide you a failing test for an issue, chances are you will incorporate that into your automated runs. Thus, the likelihood that the issue that broke them specifically will re-emerge has dropped drastically.
I wouldn't presume to expect any form of free or reduced price for a non-OSS license just for submitting a bug report, even one that came in the form of a failing test. But, that would be a nice incentive to go so far as to fork the github project, fix the bug, then issue a pull request.
A free or reduced license for use in closed source project(s) would be a nice bonus for getting a pull request accepted into the core. But if you think about it, having ones name in the list of contributors of such a large project would be a real bonus for the old resume and the value of that might far exceed the cost of a free production license.
Comment preview