intrigeri: > Hi, > > some of us are tired of having to ask for review'n'merge on this list, > duplicating the (semantically more powerful) action of setting > a ticket as Ready for QA in Redmine. Recently, we tend to forget more > and more often to send such email; moreover, some teams (e.g. the doc > and test suite teams) have simply stopped sending them already.
[snip detailed explanations] Very good point. > I see two options from this point: > > A) Decide that the Atom feed is good enough and document it, with its > aforementioned limitation (so that people can adjust their config). > I volunteer to do that if we decide to go this way. > > B) Decide that it's not good enough, and then look into a push > notification solution. Or, set up a dedicated mailing-list that > a rss2email instance will email. That rss2email will need to run as > often as reasonably possible, so that it misses as few Ready for QA > tickets as possible.. > > With my "OMG we need to provide a Perfect™ way to track this stuff" > hat on, of course I'm inclined to prefer (B). But realistically, I did not expect otherwise from you with that hat on ;) From my point of view (B) would be the Perfect™ solution, but... read on. > I believe that (A) will be good enough for 99.99% of use cases I care > about, and our sysadmin team is overloaded with new services design > help + deployment requests already, so the benefits of (B) don't seem > worth adding it to that team's plate. I should probably simply start using a feed reader and then I'll be part of that 99.99% of people :) See if it works out for some time and if not, switch to solution (B)? > Thoughts, opinions? Cheers! u. _______________________________________________ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
