--- ** [tickets:#7299] Project feed doesn't show commits with correct/usable date/time stamp** **Status:** open **Milestone:** limbo **Created:** Fri Mar 28, 2014 03:49 PM UTC by Manuel Bilderbeek **Last Updated:** Fri Mar 28, 2014 03:49 PM UTC **Owner:** nobody E.g. at this moment: https://sourceforge.net/p/openmsx/openmsx/feed shows latest commits of 24-03-14.... they all have the same date and time there. But the actual commits have different dates and have a different order. See the git log e.g. at https://sourceforge.net/p/openmsx/openmsx/commit_browser <ctsai-sf> Hmm, I have a suspicion, let me know if this sounds feasible with your situation. <ctsai-sf> I’m thinking that the feed is generated with timestamps based on when the data is scanned/entered into the Allura system, whereas the code browser’s data is generated from the data in the git log. <Quibus> it seems that the timestamps of the feed are not correct either <ctsai-sf> ie., if you made a number of commits before pushing, all those commits will have commits based on the push time <ctsai-sf> In the feed that is. <Quibus> But they were not pushed at the same time, because the last commit is from someone else <ctsai-sf> Hmm… <ctsai-sf> I mean, even if my suspicion is correct, that’s probably not ideal handling, and we should look into changing the behavior. But just trying to get at the root of what’s going on here. <ctsai-sf> Sounds like our options so far are: <ctsai-sf> 1) change pubdate to match commit time, though that doesn’t comply with RSS spec (atom seems okay though) <ctsai-sf> 2) add a new “dc:date” field, but that would only be useful for customized feed readers <ctsai-sf> 3) add more info to the description for a feed item, ie., the actual commit date and possibly more than the first line of the commit msg. <ctsai-sf> That was the last on your topic Quibus. <Quibus> As a plain user, I'd expect both the dates and the order to be the same as the git log, that's all I can say, I guess <Quibus> I'll check with the guy who mentioned this (who wrote our IRC bot based on the feed) <Quibus> <FiXato> Feedzirra supports Atom feeds afaik, so option 1 would be fine for me :-) <Quibus> <FiXato> option 2 could also be implemented into the bot I guess, but might be more work <Quibus> <FiXato> not sure how 3 will fix the ordering <ctsai-sf> To be clear, not really sure if any of those would fix the ordering. <Quibus> FiXato: good, you joined just in time to miss nothing <Quibus> FiXato: do you use the order of the items in the feed, or do you look at a date in the bot? <Quibus> (I mean: do you look at some date field in the feed for using in the bot to determine what is the latest) <FiXato> but regardless of what default order the library returns, I should fairly easily be able to sort by each item's date. <ctsai-sf> Given that, personally I’d like to see a combination of my 2 and 3 from before. Since I’d rather not depart from published spec without very good reason. But also, I’m neither affected by this bug, nor someone who’d be fixing it… <FiXato> yeah, looks like feedjirra sorts entries by their published date. So I would guess that going for option 1, changing pubdate to commit time would solve the issue in our case. <FiXato> even adding another field, if that is allowed per RSS standard, would be sufficient for us I think; just would need a bit more work on the bot. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
