Thanks for the Discourse V1 brownies!
-
Given that Discourse doesn't seem to have any regression testing, knowing if a bug was (at one point) discofixed means nothing with regards to its current status.
Filed under: Monkey patching by trained apes
-
+,
-
You'll never know. Over on meta.d jeff deletes old bug reports, or bug reports he doesn't want the public to know about, or bugs that he doesn't like, or bugs that he doesn't agree with...
Or he moves bug reports into completely different categories. That double like thing? Yeah, not a bug, that's more of a support request.
You can find most bugs documented in the likes thread, somewhere.
-
[quote=Kuro]going through Discourse Categories is hard smiley[/quote]
What about that statement made you think: "Yeah, that guy CLEARLY wants to go through a 16k (and rising) topic to sometimes find something of note in between!" ?
I could try to search for the term "Bug" in that topic. That might yield some results. But since somebody wanted to make a wiki anyway, I figured: let him do it and see what everybody can contribute. I don't think we have any wiki that is really being used by everybody. Might as well see if we can maintain one
Filed Under: This is a social experiment of sorts!
-
I'd suggest search but the search has definitely gone backwards since 1.0.
-
And lightbox which won't load on your post until you F5 (thanks to the above line item for reminding me).
CLOSED FIXED
Publish lightboxing on the message bus by riking 路 Pull Request #2705 路 discourse/discourse
With this change, images appear to lightbox instantly on my development machine. As per https://meta.discourse.org/t/easy-way-to-display-images-in-full-resolution/19324/13?u=riking, https://meta.di...
-
what about the other 19 in the list above? lightbox was the most nit-picky of all of those!
-
well it was an easy fix actually
-
I blame you for breaking uploads.
-
I blame you for temporarily breaking uploads.
-
One might have thought that a sane project run by sane people would use some sane development techniques.
If it was me, and I was hosting my project on github, I might be sorely tempted to use the github issue tracker. Y'know, rather than the current approach, which clearly doesn't work.
I would also suggest that no PR ever be accepted if it doesn't have a fucking regression test.
Yes, I know @codinghorror is a stupid enough cunt to think that the rules of software development don't apply to him, but they do. His "project for the next 10 years" is liable to become "fixing the same bugs, over and over again, for the next 10 years". If it lasts that long.
-
That's called job security, tufty.
-
Marketing, to be even more brief.
-
No, marketing comes before job security, and after. 'We fixed 4<thousand> issues! (that were already fixed once)'
-
I thought that marketing was about creating strawmen arguments (which I do not take a shot at every mention of) to profit off of something made up.
-
Marketing is about selling a product, making adoption (relatively) painless, and making it an absolute bitch to export your data to another provider.
-
Monetized encapsulation.
-
No, marketing would be
We've fixed
nhigh-priority bugs in the lastxdaysThe current situation is
Nobody knows how many bugs have been reported, let alone fixed.
-
-
damn those <sarcasm> tags
-
So was that really what killed image uploading altogether? Sneaky way of fixing the no-lightbox on posted images until F5. I apporve.
-
We could use a similar approach to fix most bugs with Discourse: temporarily disable posting. That would fix streaming posts, markdown/bbcode/html, etc.
-
