Description of problem: midori is version 0.2.6 in fedora but already version 0.2.10 is available. Version-Release number of selected component (if applicable): 0.2.6-1.fc13 How reproducible: everytime Steps to Reproduce: 1. yum list midori 2. 3. Actual results: Installed Packages midori.i686 0.2.6-1.fc13 @updates Expected results: Installed Packages midori.i686 0.2.10-1.fc13 @updates Additional info: I think it has needed an update for a while.
0.2.8 is in fact the newest upstream release. Where are you seeing 0.2.10? We decided not to update f12/f13 because there were interface changes that might be confusing. (no bookmarks icon/menu on the menubar). We might revisit this with 0.2.8 however as some of the changes were reverted.
sorry my bad mistake. the confusing update was 0.2.7 and the new change is 0.2.8 (not 0.2.10) which reverts the bookmarks icon/menu on the toolbar.
Hi, anything new on this front? 0.2.8 has now been out for ten days. thanks!
Yeah, I guess we can push to f13/f12 now since that interface change was reverted. Will do so today. Testing of the updates very welcome.
midori-0.2.8-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/midori-0.2.8-2.fc13
midori-0.2.8-2.fc12 has been submitted as an update for Fedora 12. https://admin.fedoraproject.org/updates/midori-0.2.8-2.fc12
IMHO midori 0.2.8 should not bee pushed to F13. The controversial part of the interface changes were reverted, but the new solution is very different from 0.2.6. This is a violation of our stable updates vision: "Stable releases should provide a consistent user experience throughout the lifecycle, and only fix bugs and security issues." https://fedoraproject.org/wiki/Stable_release_updates_vision#Vision_Statement @Globe Trotter: Can you elaborate *why* midori needs an update? If there is no good reason, IMHO this contradicts our https://fedoraproject.org/wiki/Updates_Policy
Humm... I guess I need to install 0.2.6 and look at it against 0.2.8. My understanding was that the user visible change was reverted...
I guess I can pull these for now until we discuss it further. 0.2.6 and 0.2.7 include some very nice performance and non user visible changes. I guess it depends what we mean by 'user experience'. If thats any change in the UI? Translation updates? How about the allowing speed dial to have different sizes? v0.2.8 + Re-implement Bookmarks menu and toolbar button + Show transferbar even if statusbar is hidden + Smart case for inline search while typing + Use Alt+Shift+Right instead of Ctrl+Right for Next Page + Adding, edit and delete buttons for user scripts/ styles + Rename 'Minimize Tab' to 'Show Tab Icon Only' + Delete key in completion deletes items + Don't show homepage in bookmarkbar + Fix crash when using location arrow button v0.2.7 + Multiple word completion in location + Database backed bookmarks + Search bookmark panel and drag bookmarks + Bookmarks in address completion + Removed bookmarks and history from menubar + Add 'Minimize New Tabs' and 'Copy Addresses of Tabs' + Refactorings and optimisations in the core + Adblock compatibility improvements and speedup + Changeable speed dial size + Delayed pages at startup, or after a crash
So, digging thru git logs, it seems that the changes here are probibly not worth pushing to stable. It's just enhancements and fixes for minor issues, no major bugs. (The 0.2.8 fix for the location bar might be, but that was introduced in 0.2.7 :) So, I would say we should avoid pushing until theres a better reason. :( Sorry for the trouble here.
Please don't get me wrong: I don't mind pushing the new version. In fact, I think that many people would like it. Nevertheless it contradicts the updates policy that you yourself drafted. IMHO this is a nice opportunity that we should ether reconsider the updates policy or offer an additional channel for enhancement updates.
Yes, I was thinking the crasher in autocomplete was worth the update, but didn't note correctly that that happened in 0.2.7, which isn't in f12/f13. :) Yes, some enhancement framework would be good.
The crasher in autocomplete isn't fixed in 0.2.8 ether, it's only fixed in GIT.
*** Bug 668149 has been marked as a duplicate of this bug. ***
Revisiting this, we may want to ask for an update exception for the next release... There are several crashers in 0.2.8 (in f14 currently) and I think the ui changes are somewhat minor. 0.2.10 is probibly going to come along soon too, so I would like to wait until then to evaluate if we can ask for an exception for that, or try and backport the crasher fixes.
Nirik, I think you are too strict here. Bug 668149 was filed against F14 which came with 0.2.8. The changes between 0.2.8 and 0.2.9 are minor, in fact I don't see any. On the other hand 0.2.9 fixes a number of bugs e.g. bug 636967.
Just to be clear: What I wanted to say is that for F14 there are no big changes and the update IMHO does not violate the stable updates policy. I don't think we need an exception.
Well, I guess you are correct... there are some UI changes, but they are all additive, like adding an identify-as to the menubar, and the --help-execute command line option, and minor. So, I can look at doing a 0.2.9 for f14...
I had to add in: http://git.xfce.org/apps/midori/commit/?id=97a7ae9955d4264f922452d6933f3a0e1e4b03f6 As without it, midori crashes after a few minutes of use.
midori-0.2.9-4.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/midori-0.2.9-4.fc14
midori-0.2.9-4.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update midori'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/midori-0.2.9-4.fc14
midori-0.2.9-4.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.