Latest upstream release: 3.3.0beta1 Current version in Fedora Rawhide: 3.2.0 URL: http://sylpheed.sraoss.jp/en/download.html Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Would be nice to get some updates to sylpheed.....
But not 3.3 beta. The development cycle for 3.2 was a year (3.2beta1 was released 2011-07-01 and the final came out 2012-06-29). If we have the same for 3.3, we'll see 3.3 in June 2013, this would be Fedora 19 then. Therefore I'll stick to the 3.2 stable series even in rawhide.
sylpheed-3.2.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/sylpheed-3.2.0-1.fc18
sylpheed-3.2.0-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/sylpheed-3.2.0-1.fc17
sylpheed-3.2.0-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/sylpheed-3.2.0-1.fc16
(In reply to comment #2) > But not 3.3 beta. The development cycle for 3.2 was a year (3.2beta1 was > released 2011-07-01 and the final came out 2012-06-29). If we have the same > for 3.3, we'll see 3.3 in June 2013, this would be Fedora 19 then. Sorry, Fedora 19 will be released in End of May 2013, so we have two options: 1. Stick to 3.2.x for Fedora 19 and delay 3.3.x till Fedora 20. This means we must not build 3.3.x before the F19 mass branch which should happen somewhere in Feburary. 2. Ship 3.3.x in Fedora. This means we'll have to live with a pre-release for ~2 months, should be something like beta8, beta 9 or the RC. If we want this, we should build 3.3.0beta1 for rawhide now. Itamar, what is your opinion? I think we can go for option 2, but we definitely should stick to 2.3 for all other Fedora releases than F19.
Sylpheed has been in beta in many releases for Fedora. Even now, the release is 3.2.0beta9, which you have kindly updated. Is this a major issue: so far even the beta has been remarkably stable.
sylpheed-3.2.0-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
sylpheed-3.2.0-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
sylpheed-3.2.0-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
sylpheed-3.3.0 stable has been released. Time to push this out also?
*** Bug 861429 has been marked as a duplicate of this bug. ***
sylpheed-3.3.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/sylpheed-3.3.0-1.fc18
sylpheed-3.3.0-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/sylpheed-3.3.0-1.fc17
Package sylpheed-3.3.0-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing sylpheed-3.3.0-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-18336/sylpheed-3.3.0-1.fc17 then log in and leave karma (feedback).
sylpheed-3.3.0-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
sylpheed-3.3.0-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.