That was one of the reasons I was unsure where to put the script.
src/main/scripts is fine although it isn't obvious from that location
that it's unrelated to the use of Calcite. I'm not strongly opposed to
just pasting it in the documentation.
--
Michael Mior
mm...@apache.org

Le jeu. 27 juin 2019 à 14:40, Julian Hyde <jh...@apache.org> a écrit :
>
> src/main/scripts would be an OK location.
>
> As this particular script is for a very limited audience - not developers, 
> but only for release managers - we could consider just putting the text into 
> the howto. I hate finding lots of scripts in projects when it is not clear 
> what is the audience or purpose of these scripts. We should definitely keep 
> development/release scripts clearly separate from scripts needed at runtime.
>
> Julian
>
>
> > On Jun 26, 2019, at 8:15 AM, Kevin Risden <kris...@apache.org> wrote:
> >
> > Top level has src/ which has a bunch of config files for
> > checkstyle/forbidden-apis/etc. Might be a decent spot.
> >
> > Kevin Risden
> >
> >
> > On Wed, Jun 26, 2019 at 11:07 AM Michael Mior <mm...@apache.org> wrote:
> >
> >> A Gradle task is great if we migrate to Gradle, but I don't think it's
> >> a compelling reason in itself. I would personally prefer to just have
> >> a copy of the script somewhere in the repo because the only purpose of
> >> putting it in the HOWTO would be so someone could copy and paste and
> >> run it. That said, I'm not sure where a good spot for such scripts to
> >> live would be in the folder hierarchy.
> >> --
> >> Michael Mior
> >> mm...@apache.org
> >>
> >> Le mar. 25 juin 2019 à 16:23, Julian Hyde <jh...@apache.org> a écrit :
> >>>
> >>> Or just paste the script into HOWTO.
> >>>
> >>> It works fine on macOS, Linux and Windows/Cygwin, which I think covers
> >> it.
> >>>
> >>> Julian
> >>>
> >>>
> >>>> On Jun 25, 2019, at 1:19 PM, Vladimir Sitnikov <
> >> sitnikov.vladi...@gmail.com> wrote:
> >>>>
> >>>> Michael>If we're going to use it, I think we
> >>>> Michael>might as well have a copy in the Calcite repo.
> >>>>
> >>>> I have a plan here:
> >>>> 1) We migrate to Gradle
> >>>> 2) The script can be written as a Gradle task so it is easily
> >> available,
> >>>> and it works in all OSes
> >>>>
> >>>> Vladimir
> >>>
> >>
>

Reply via email to