In the past we used to have Jenkins jobs doing this but I guess when Jenkins "died" all of these were lost.
I am just seeing this as restoring the old behavior so it's fine with me. Personally, I never used them in the past but if those are helpful to other people then why not. Best, Stamatis On Sun, Dec 12, 2021 at 11:08 PM Julian Hyde <jhyde.apa...@gmail.com> wrote: > I have no problems with the technical side of this. And I am supportive of > one-off snapshots, e.g. a snapshot for testing made a week or two ahead of > a release. > > But there are some downsides with regular, automated snapshots, and I am > concerned that projects and companies will become dependent on them, for > the following reasons: > > 1. Snapshots can change without notice. (Bugs may be introduced, APIs > removed without notice.) This is mostly the problem for the downstream > project — in other words, caveat emptor — but may cause work for > committers. It’s certainly a bad idea to base a release on a snapshot. > > 2. Snapshots are not releases. The Apache license does not apply to code > that has not been released. > > 3. If people get too comfortable using snapshots, there will be fewer > resources to make official releases. > > Is the additional convenience worth these downsides? Just asking. I’m > prepared to be persuaded. > > Julian > > > > > On Dec 12, 2021, at 10:23 AM, Jacques Nadeau <jacq...@apache.org> wrote: > > > > Hey All, > > > > I've been wanting to do more testing against master for integration > > purposes and right now that requires private builds. As such, I opened > > CALCITE-4934 [1] to add support for automatic snapshot builds deployed to > > the Apache snapshot Maven repository on master merges. As noted in the > > ticket, this used to be the case many years ago (CALCITE-351 enabled it). > > The right bits are now enabled in GitHub to make this effortless and I've > > confirmed that this looks like it is working correctly [2][3]. > > > > Before merging I wanted to make sure that people were comfortable with > this > > addition since it changes build infra. The PR is pretty trivial [4] and > > modeled off other Apache projects. > > > > Lastly, note that snapshots are *not* Apache Releases and shouldn't be > > presented as such in docs, etc. > > > > Please raise your hand if you have any concerns. > > > > Thanks, > > Jacques > > > > > > [1] https://issues.apache.org/jira/browse/CALCITE-4934 > > [2] > https://github.com/apache/calcite/runs/4499040456?check_suite_focus=true > > [3] > > > https://repository.apache.org/content/groups/snapshots/org/apache/calcite/calcite-core/1.29.0-SNAPSHOT/ > > [4] https://github.com/apache/calcite/pull/2641 > >
