Hey Cyril, I can fully understand, that you may be under stress and frustrated, when you prepare a release. Many thanks for all your work and thanks that you reflect yourself afterwards and asked for apologies, that is great.
>From your mail I think, it may makes sense to document your needs (expectations), when a release is is created at some place. So it is easy to lookup your needs and what things do you need when from others, while releasing. Because at least me, I have no idea about your needs. > I suppose it's basically either something that I (feel the need to) vent > about on the spot, or something that should be ending up in some ticket > or mail-based report once the release is over. I think I've done the > latter since my very first release, and I'll now focus on avoiding the > former when preparing the next releases. That is a great attitude to try not to do the same mistakes twice. Yes the new way may have new issues but that way we learn, what works and what doesn't. The next step should be to document, what works and what doesn't so others don't have to do the same mistake again. hefee
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
