Petition to move to Discourse CI
-
I here by sign this petition requesting, no, ordering by the power of some deity, that the forum is moved to use, not latest, but the CI version of Discourse. Each push, each PR, each commit closer to enlightenment.
Repeat after me:
Release often, release faster!
-
CI
Well I suppose it would save me the bother of manually updating every morning...
However I see a sticking point:
CI was originally intended to be used in combination with automated unit tests written through the practices of test-driven development.
-
-
Give a monkey infinite time and it will write Hamlet.
Actually, @accalia should write a bot for automated unit tests.
-
Why limit yourself to commits? When you commit, your code is already old and obsolete. I propose syncing TDWTF with @sam's text editor.
-
Actually, @accalia should write a bot for automated unit tests.
one word there: Selenium (via browserstack for preference)
-
Well I suppose it would save me the bother of manually updating every morning...
i can make @shadowmod do that if you want?
-
Not for that; not sure about automating indiscriminately updating. ..
-
Not for that; not sure about automating indiscriminately updating. ..
sanity... there's hope for you yet. ;-)
-
each commit closer to enlightenment
Is enlightenment where we realise that we really should be using something else?
-
Give a monkey infinite time and it will write Hamlet.
proof:
Given infinite time
Evolution will turn the monkey to a person.
A person will turn into Shakespeare.
Shakespeare will write hamlet.
-
A person will turn into Shakespeare.
Except that Shakespeare was not a single person
Shakespeare of Stratford was a front to shield the identity of the real author or authors, who for some reason did not want or could not accept public credit
-
Except that Shakespeare was not a single person
Also I see an "or" in the reference.
-
Except that Shakespeare was not a single person
all but a few Shakespeare scholars and literary historians consider it a fringe belief and for the most part acknowledge it only to rebut or disparage the claims.
-
I actually think you guys should update less, not more.. we appreciate the testing, and you guys are really good at it, but you will be feeling some temporal bugs that you could have skipped by updating this often.
Up to you of course.
-
but you will be feeling some temporal bugs
What the heck is a temporal bug? Are we going to get cockroaches from the future? Did you mean temporary?
-
he meant temporary.
temporal sounds "cooler" and has been getting some traction as slang for temporary in some parts of 'murica.........
much to my displeasure.
-
-
he meant temporary.
temporal sounds "cooler" and has been getting some traction as slang for temporary in some parts of 'murica.........
much to my displeasure.
This will not stand!
At least not if I am around to call people out on it. @codinghorror might as well have shouted "pussy in the chain wax" here.
-
no gramming flag for you., too easy a target. ;-)
-
What's it called? Discopedia? Disaurus?
-
please. if i consult anything it's going to be the discopaedia.
and if i'm being posh about it i'll replace that AE with a proper ashe symbol
-
Revised question:
Is displeasure in the discopædia?
-
I actually think you guys should update less, not more.. we appreciate the testing, and you guys are really good at it, but you will be feeling some temporal bugs that you could have skipped by updating this often.
Up to you of course.
I FULLY SUPPORT ALL OF THIS!!!!!!!!!!!!!!!!!!!!
-
We need a spin on the morbs meme:
I disagree with whatever @codinghorror just said.
-
-
I actually think you guys should update less, not more.. we appreciate the testing, and you guys are really good at it, but you will be feeling some temporal bugs that you could have skipped by updating this often.
Do you seriously think people here DON'T want any bugs in the forum?** - in case you couldn't tell: people here love bugs in forum software
-
-
I actually think you guys should update less, not more.. we appreciate the testing, and you guys are really good at it, but you will be feeling some temporal bugs that you could have skipped by updating this often.
Given the fact that most of the time when I do the 'daily update' around 0800/0900 UTC the last commits are in the order of hours ago, giving the impression that the devs have actually stopped for the day, would you care to expound on how you define temporal (or temporary if that's what you meant?)
-
-
Is this a temporal bug?
(from here)
-
"temporal"?
Is that your excuse for allowing bug ridden commits to a repo? Such behavior should result tar and feathering. Sure bugs can happen, but the majority seem to be obvious as fuck bugs and not race conditions,edge cases or other sillyness.
-
Is this a temporal bug? It's only been around like 3 months, so it seems pretty temporal to me.
What about the bug where typing "3." at the beginning of a line results in "1." in the post? Is that a temporal regression? It's been regressed like 4 months or so, so that seems pretty temporal.
-
Temporary bugs:
What @codinghorror was talking about — bugs that get fixed quickly, often by stupid hacks that introduce other bugs.Temporal bugs:
The way Discourse (by design) hides actual time stamps, and rounds the elapsed time it does display.
"You must wait N hours," where N is completely wrong.
Failure to load the document in a reasonable amount of time (infinispin).What Blakey's talking about:
CDCK don't give a .
-
What about the bug where typing "3." at the beginning of a line results in "1." in the post? Is that a temporal regression? It's been regressed like 4 months or so, so that seems pretty temporal.
Technically that has been "regressed" since 2004 since it's part of the original Markdown spec. But you know Blakey, I admire a man who isn't about to let mere ignorance keep him from having an opinion on something ;)
-
No, technically it was fixed here at some point. And it is not part of your markdown spec. Ignorance is one thing, but multiple users remember it working differently before. You're doing it wrong.
-
Nope. That's how it has always worked. See for yourself:
http://johnmacfarlane.net/babelmark2/?normalize=1&text=2.+Two 3.+Three 4.+Four
-
- Hello?
- I think this is a bit dumb.
- Do you really call this sane?
Honestly, if it hadn't shown up the way people expect for a while, people would just complain that the spec is dumb. But that isn't the case, and so there's only one thing that needs to be said about your ability to fix bugs. You're Doing It WrongTM
-
I, for one, think that the ordered list issue is stupid, and blame this on the Markdown spec. I choose to direct my anger at them.
-
As far as I know, his 'Common' version doesn't do:
-
10
-
9
-
8
-
7
-
6
-
5
-
4
-
3
-
2
-
1
- 10
- 9
- 8
- 7
- 6
- 5
- 4
- 3
- 2
- 1
Which seems to have a second bug, actually. @discoursebot!
(Essentially, there is no line between the first
2. 2
and1. 1
and there IS a single line after the first1. 1
. The rest is code formatted. Or should be.)
-
-
@Magus - Days Since Last Discourse Bug: 0
-
Technically that has been "regressed" since 2004 since it's part of the original Markdown spec.
No. One of your devs (EvilTrout?) fixed it very shortly after the new Markdown spec whatever-its-called made that the correct behavior.
Then less than a month later, it was regressed again.
You already know all this, of course, being a professional software development operation which has changes well-documented by your bug tracker.
But you know Blakey, I admire a man who isn't about to let mere ignorance keep him from having an opinion on something
I appear to know more about the history of Discourse development than you do.
-
I appear to know more about the history of Discourse development than you do.
-
Oh look! Vanishing posts are back!
-
What the everloving fuck?
-
Who said they ever went away?
-
`OpenHard`
uhhh....
-
I have no idea what you mean.
-
Oh look! Vanishing posts are back!
Just another temporal bug. Manipulating space and time ain't easy.
-