| Summary: | seamonkey-2.3.1 is available (but seamonkey-2.3 is sufficient for fedora) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | seamonkey | Assignee: | Kai Engert (:kaie) (inactive account) <kengert> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | caillon, cfeller, gecko-bugs-nobody, hicham.haouari, kengert, long, stransky, thoger |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-08-24 20:11:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Upstream Release Monitoring
2011-06-11 10:42:00 UTC
*** Bug 713993 has been marked as a duplicate of this bug. *** *** Bug 711953 has been marked as a duplicate of this bug. *** 2.2 is out already. It's unclear if upstream is planning to release any 2.0.x update with just security fixes (probably not). What is the current plan for Fedora? Move all branches to 2.2? IMHO we should rebase to 2.2 but I don't have time for it. Would be great if anyone can handle it. Thanks for quick reply and clarification. Latest upstream release: 2.3 Current version in Fedora Rawhide: 2.0.14 URL: http://www.seamonkey-project.org/releases/ 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 I worked on this during the weekend, and have a F15 build of SeaMonkey 2.3 http://koji.fedoraproject.org/koji/taskinfo?taskID=3290353 Does this work for you? I also built 2.3 for rawhide. I would appreciate test feedback. We can close this bug as soon as someone gives some positive test report. Thanks Latest upstream release: 2.3.1 Current version in Fedora Rawhide: 2.3 URL: http://www.seamonkey-project.org/releases/ 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 I learned that the difference between 2.3 and 2.3.1 is minimal. The difference should be irrelevant for Fedora. 2.3.1 allows additional security certificates for verifying update from official Mozilla update servers. Fedora disables Mozilla operated updating, because it's using our own RPM update system. I would like to skip SeaMonkey 2.3.1, 2.3 should be sufficient. Marking this fixed, because seamonkey 2.3 is available in rawhide. Please comment if you have a different experience. |