+100 to having a release plan like this!
There are 28 open regressions, I assume/hope those will be taken care of before RC1? I.e. after feature freeze, but before RC, right? There are 22 open issues assigned to the 0.5.x milestone. The description for that one says “Bugs to fix in the 0.5.0 or 0.5.x timeframe”. Might be a good idea to make a call on each of these and decide which of those have to be fixed for 0.5.0 (in which case they should be fixed before RC1) and which will go into 0.5.1. Here is one idea on how to handle this in terms of logistics: rename the 0.5.0 milestone to “0.5.0-beta” (or “0.5.0-feature-freeze” or something like that). These are the items that need to get done before the feature freeze. Create a new milestone “0.5.0-RC1”, and assign those issues that need to be fixed before RC to that milestone. I guess that should be most issues with a “regression” label (but maybe not all, seems possible that you decide to fix some of the regressions later), and some subset of the issues with the 0.5.x label. If needed, create more RC milestones as things go on, i.e. “0.5.0-RC2” etc. Change the description of the 0.5.x milestone to say, “Things to do in a 0.5.x release”, and anything assigned to that milestone will definitely not be done for 0.5.0. Very exciting to see 0.5 come to a close!! Cheers, David From: [email protected] [mailto:[email protected]] On Behalf Of Tony Kelman Sent: Thursday, July 14, 2016 10:25 AM To: julia-news <[email protected]> Cc: Julia Users <[email protected]> Subject: [julia-users] ANN: steps towards 0.5.0 release [candidates] See https://github.com/JuliaLang/julia/issues/17418 for how this process is going to go. Please keep any discussion on that github issue focused so the noise level stays manageable. If you have any questions or comments, you can ask them here (don't cc julia-news if you do so though, that list is intended to be low-volume).
