Apache OpenOffice (AOO) Bugzilla – Issue 127739
links to weekly development builds incorrect for linux 64 bits
Last modified: 2018-03-25 11:46:06 UTC
Reproducing: 1) Open 'Development builds' page: https://www.openoffice.org/download/devbuilds.html 2) Click 'Linux 64-bit snapshot build: 8 languages, built every Sunday from branch; RPM, DEB format.' 3) Links leads to (outdated) page https://ci.apache.org/projects/openoffice/install/41x/ Expected: Opening the (correct) page: https://ci.apache.org/projects/openoffice/install/linux64/
Oh wait. That's for 4.2.0, actually (was looking only on the date field in the tiniest of pointsizes). So, no more weeklies for 4.1.*? Shouldn't it be advertised on the 'development builds' page, then?
I do not see the goal of this issue. All your issues could be better answered on dev mailing list. :) No more changes are planned for 4.1.x release. We had only planned 2 bugfix releases, due to regression issues we did 3. Our primary goal is to get 5 years of development out of the door and stop backporting stuff. A possible 4.1.6 is only planned in case of emergency, like a security issue. This is currently unknown to us. I close this report as not an ooo issue since I really don't know what to fix. Hope you are fine with this resolution. Again you are welcome to write mails. :) All the best Peter
Okay, thank you, but be it as it may, the site _is_ somewhat uninformative/misleading there, and I definitely remember selecting an appropriate category :) (JFYI-like, I'm still using 4.1.5_weekly, as 4.2.0 is still tad unusable for some of us, because of #127315 :)
True. 4.2.0 is not usable. We will announce when we think it can be used with "beta" Quality. Hmm, my point is there is no point in using the 4.1.5 weekly. There are no changes. ;) I address it on the List. Thanks for bringing to topic up.
Pfft... Sorry I was hasty. The wiki page says branch which refers to next release beach. And trunk which is the latest development stuff. So no weekly 4.1.5. I hope it does not take long until 4.2.0 enters beta state.