← Back to context Comment by msephton 1 day ago It's already released in the latest nightly build. 3 comments msephton Reply DrammBA 1 day ago Are the nightly releases the expected way to get timely bugfixes? amazingman 20 hours ago That is how software releases generally work. AFAICT this is not a bug with broad impact or security implications. fartfeatures 11 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 1 day ago Are the nightly releases the expected way to get timely bugfixes? amazingman 20 hours ago That is how software releases generally work. AFAICT this is not a bug with broad impact or security implications. fartfeatures 11 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 20 hours ago That is how software releases generally work. AFAICT this is not a bug with broad impact or security implications. fartfeatures 11 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 11 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.