Just to let you all know that we managed to close 58 old tickets as a result of this event. Fantastic!
Thanks Matt On 27/04/17 08:43, Matt Caswell wrote: > > > Hi all > > Our next "Code Health Tuesday" event will be on Tuesday 2nd May. > > This time we would like to focus on closing off Github issues (with a > particular focus on old ones - including all those we brought over from RT). > > Thanks! > > Matt > > FAQ: > > Q: How do I participate? > A: Review the old issues in Github. If an issue can be closed then post > a comment in the issue suggesting its closure along with your reasons. > If an issue still needs to be fixed then raise a PR to fix it and > include "Fixes #XXX" in the commit message (where XXX is the issue > number) Include the words "code health" in the PR title. > > Q: Which branches should I target? > A: Any currently supported branch (i.e. master, 1.1.0 and 1.0.2) where > the issue applies > > Q: What are good reasons for recommending the closure of an issue? > A: There are lots of possible reasons. Some are: > - It has already been fixed > - It is no longer relevant > - It does not affect currently supported versions (master, 1.1.0 and 1.02) > - We can no longer reproduce it > - The issue is incorrect > - It is a duplicate of some other issue > > Q: How do I find the issues that were brought over from RT? > A: Use this link: > https://github.com/openssl/openssl/issues?q=is%3Aissue%20is%3Aopen%20rt > -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
