| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2016-10-07 | 690 Bytes | |
| Release 2.1.0.tar.gz | 2016-10-07 | 108.7 kB | |
| Release 2.1.0.zip | 2016-10-07 | 110.1 kB | |
| Totals: 3 Items | 219.5 kB | 0 | |
Reverse the order that the bot examines an updated feed's items.
If you usually have only a single item show up at a time from most of your feeds, this change won't matter to you.
It's possible that this behavior change will be undesirable for some situations, hence the jump from 2.0.x to 2.1.
For github commit feeds it's common that there will be multiple new items in the feed and that the order is relevant (since it's common for several commits to be pushed in at one time). The bot was processing feeds from start to end of file, which means newest to oldest in most feeds, and therefore getting the order wrong on those feeds.
There may be other feeds where this is the case.