← Back to context Comment by msephton 20 hours ago It's already released in the latest nightly build. 3 comments msephton Reply DrammBA 18 hours ago Are the nightly releases the expected way to get timely bugfixes? amazingman 15 hours ago That is how software releases generally work. AFAICT this is not a bug with broad impact or security implications. fartfeatures 6 hours ago I guess thats arguable, a memory leak can make a system unpleasant to use although I accept it can be solved by repeatedly restarting the offending app.
DrammBA 18 hours ago Are the nightly releases the expected way to get timely bugfixes? amazingman 15 hours ago That is how software releases generally work. AFAICT this is not a bug with broad impact or security implications. fartfeatures 6 hours ago I guess thats arguable, a memory leak can make a system unpleasant to use although I accept it can be solved by repeatedly restarting the offending app.
amazingman 15 hours ago That is how software releases generally work. AFAICT this is not a bug with broad impact or security implications. fartfeatures 6 hours ago I guess thats arguable, a memory leak can make a system unpleasant to use although I accept it can be solved by repeatedly restarting the offending app.
fartfeatures 6 hours ago I guess thats arguable, a memory leak can make a system unpleasant to use although I accept it can be solved by repeatedly restarting the offending app.
Are the nightly releases the expected way to get timely bugfixes?
That is how software releases generally work. AFAICT this is not a bug with broad impact or security implications.
I guess thats arguable, a memory leak can make a system unpleasant to use although I accept it can be solved by repeatedly restarting the offending app.