intrigeri: > 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.
People on this list are probably glad that we don't open a thread for each one of our documentation tickets :) > Nevertheless, at least I have always resisted getting rid of these > email, on the grounds that we have no other working, tested and > advertised way of following what changes are proposed to go into > Tails, and of voicing concerns *before* changes land in our release > Git branches. I still strongly feel we need that, but perhaps I'm > overdoing it a little bit. I'm not in favor of completely getting rid of them. I think that even if we use one of the solutions that you are proposing, we should still notify the list when we feel that more than two people should have a look at a branch. For example, when doing non-trivial changes to the code or when writing big chunks of documentation. I will at least continue doing that. I know that this might be completely subjective but I believe it will work and be better than do reviews only on Redmine. The point is to find the best signal/noise ratio on the list. > 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. Sounds good. -- sajolida _______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
