Re: [Tails-dev] Getting rid of review'n'merge email on this …

Delete this message

Reply to this message
Author: anonym
Date:  
To: The Tails public development discussion list
Subject: Re: [Tails-dev] Getting rid of review'n'merge email on this list
On 05/04/2015 05:35 PM, intrigeri wrote:
> 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 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.


It seems we can get a perfect solution easier by having an Atom feed for
both to Ready for QA and Fix committed.

Full background:

(21:31:37) anonym: intrigeri: actually, I just thought of something you
said in your email re: killing review'n'merges
(21:33:38) anonym: intrigeri: Goal: enough time to voice "concerns
*before* changes land in our release Git branches"
(21:33:38) anonym: Problem with solution A: "if a ticket was marked as
Ready for QA, and then review'n'merged, and then flagged as "Fix
committed", all that between two fetches of my feed reader, then I would
never get any notification for that ticket"
(21:33:57) anonym: I don't see how a review'n'merge email would have
avoided that problem
(21:34:19) anonym: it would be sent at the same time as the ticket was
marked Ready for QA
(21:34:24) anonym: so you would still miss it
(21:34:40) intrigeri: anonym: Right, a review'n'merge email would not
solve the "before" part.
(21:35:16) intrigeri: anonym: But in 99% of cases, it'll still allow
interested control freaks^W^Wpeople to notice the change before next
release.
(21:35:39) anonym: intrigeri: so, augment solution A with also
subscribing to Fix committed
(21:36:04) anonym: a bit more noise, but oh well
(21:36:06) intrigeri: anonym: you're totally right. awesome!

Cheers!