I'd be in favor in having nightlies made available in a central place for testing. I think it would help users verify whether bugs have been fixed in master or not.
Other ASF projects do make nightlies available with appropriate disclosures that they are not releases: https://jmeter.apache.org/nightly.html Since these packages are not releases, there is no formal policy to govern such details as package signing, so I don't think we have to worry about that. For the other questions you may have to inquire with ASF INFRA. best Wes On Mon, Feb 25, 2019 at 3:51 PM Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote: > > Hi, > > Currently We have nightly package builds, currently under my > github account, which is not really visible. It would be great to > make them available for developer purposes, and additionally > it'd test the binary scripts too. > The nightly packages are produced the same way like it is > documented in the release management guide, except that they > are not getting uploaded to bintray. > > I can setup a cron job to upload the nightly packages to bintray > under `-nightly` postfixed directories (similarly like `-rc` packages > are stored [1]), however I have a couple of questions: > - How should We handle the signing procedure? Simply omit? > - May We host the nightlies under the Apache bintray account? > - Do We want to use JFrog Artifactory over Bintray? > If so should We setup it [2] or does Apache has one already? > > Regards, Krisztian > > [1] https://bintray.com/beta/#/apache/arrow?tab=packages > [2] https://jfrog.com/open-source/#artifactory
