I experienced some trouble with feed readers which expect the most recent entry be always at the beginning of the feed XML. Although it is not part of the RFC4287 it appears that it is a common consensus to start with the newest entry.
Background: A recurring process inspects my data and generates change notifications via an atom feed. The FeedGenerator is pickled and stored to disk to avoid regeneration of the whole feed on each cycle.
Coverage remained the same at 90.364% when pulling 770603320032a6afc7e82b27bcb4926468fa22d8 on stbisplinghoff:master into 84dd4373aebcdc3a77440170e1583007f8c81a2b on lkiesow:master.
I experienced some trouble with feed readers which expect the most recent entry be always at the beginning of the feed XML. Although it is not part of the RFC4287 it appears that it is a common consensus to start with the newest entry.
Background: A recurring process inspects my data and generates change notifications via an atom feed. The FeedGenerator is pickled and stored to disk to avoid regeneration of the whole feed on each cycle.