Latest upstream release: 3.0.2 Current version in Fedora Rawhide: 3.0.0 URL: http://sylpheed.sraoss.jp/en/download.html Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_Release_Monitoring
Latest upstream release: 3.1.0beta1 Current version in Fedora Rawhide: 3.0.0 URL: http://sylpheed.sraoss.jp/en/download.html Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_Release_Monitoring
Maintainer seems unresponsive, I will take care of this.
sylpheed-3.0.2-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/sylpheed-3.0.2-1.fc13
3.1.0 Beta 1 is in rawhide now: http://koji.fedoraproject.org/koji/taskinfo?taskID=2251600
Itamar, are you still around? Please be so kind as to reply to this bug report so we know you are still maintaining your packages. If you don't reply, we need to orphan them according to https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers Consider this as step one of the policy and reply within 2 weeks. TIA!
(In reply to comment #2) > Maintainer seems unresponsive, I will take care of this. ok, thanks, I am a bit busy studying for a exam, Can we close this ticket ?
Sure, but we need to make sure that your packages are actively maintained. I am busy too, but I'm still spending times on my packages and their bug reports. If you cannot afford this time ATM due to your exams, please ask for co-maintainers on the mailing list. I'm already co-maintainer for sylpheed, other contributors might help you with the rest of your packages.
sylpheed-3.0.2-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.