Implement Swift object expiration.
Do we really want it for 1.3.2?
Is a backport too difficult or too risky?
*** Bug 1262117 has been marked as a duplicate of this bug. ***
Feature testing is complete. Doc text looks fine. Moving to verified
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.