Bug 712580 - seamonkey-2.3.1 is available (but seamonkey-2.3 is sufficient for fedora)
Summary: seamonkey-2.3.1 is available (but seamonkey-2.3 is sufficient for fedora)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kai Engert (:kaie) (inactive account)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 711953 713993 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-11 10:42 UTC by Upstream Release Monitoring
Modified: 2011-08-24 20:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-24 20:11:43 UTC
Type: ---


Attachments (Terms of Use)

Description Upstream Release Monitoring 2011-06-11 10:42:00 UTC
Latest upstream release: 2.1
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

Comment 1 Michael J Gruber 2011-06-30 08:07:33 UTC
*** Bug 713993 has been marked as a duplicate of this bug. ***

Comment 2 Michael J Gruber 2011-06-30 08:08:50 UTC
*** Bug 711953 has been marked as a duplicate of this bug. ***

Comment 3 Tomas Hoger 2011-07-11 08:40:13 UTC
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?

Comment 4 Martin Stransky 2011-07-11 08:57:00 UTC
IMHO we should rebase to 2.2 but I don't have time for it. Would be great if anyone can handle it.

Comment 5 Tomas Hoger 2011-07-11 09:03:12 UTC
Thanks for quick reply and clarification.

Comment 6 Upstream Release Monitoring 2011-08-17 10:53:33 UTC
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

Comment 7 Kai Engert (:kaie) (inactive account) 2011-08-21 20:46:57 UTC
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?

Comment 8 Kai Engert (:kaie) (inactive account) 2011-08-22 20:51:15 UTC
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

Comment 9 Upstream Release Monitoring 2011-08-24 10:48:24 UTC
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

Comment 10 Kai Engert (:kaie) (inactive account) 2011-08-24 20:10:24 UTC
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.

Comment 11 Kai Engert (:kaie) (inactive account) 2011-08-24 20:11:43 UTC
Marking this fixed, because seamonkey 2.3 is available in rawhide.

Please comment if you have a different experience.


Note You need to log in before you can comment on or make changes to this bug.