> it could just be fixed in master rather than back-port and re-roll the RC
I don't think the release script is part of the released product. That said, we can just fix the release script in branch 2.4 without creating a new RC. We can even create a new repo for the release script, like spark-website, to make it clearer. On Tue, Apr 30, 2019 at 7:22 AM Sean Owen <sro...@gmail.com> wrote: > I think this is a reasonable idea; I know @vanzin had suggested it was > simpler to use the latest in case a bug was found in the release script and > then it could just be fixed in master rather than back-port and re-roll the > RC. That said I think we did / had to already drop the ability to build <= > 2.3 from the master release script already. > > On Sun, Apr 28, 2019 at 9:25 PM Wenchen Fan <cloud0...@gmail.com> wrote: > >> > ... by using the release script of Spark 2.4 branch >> >> Shall we keep it as a policy? Previously we used the release script from >> the master branch to do the release work for all Spark versions, now I feel >> it's simpler and less error-prone to let the release script only handle one >> branch. We don't keep many branches as active at the same time, so the >> maintenance overhead for the release script should be OK. >> >>> >>>
