Hi All, I plan on doing a release candidate soon with mac binaries as well as a new aarch64 binary. I hope to get an RC out within a week or so.
Gary On Sun, Aug 9, 2020, 07:13 sebb <seb...@gmail.com> wrote: > It occurs to me that we don't *have* to release binaries. > > We could just release the source, as is done by several other ASF > projects (including httpd). > > Sebb. > > On Mon, 3 Aug 2020 at 15:15, Geoffrey Blake <geoffrey.w.bl...@gmail.com> > wrote: > > > > Hi Gary, has a solution for the Mac build been reached? Do you > > require some assistance here? As Bindul suggested, Travis has support > > for uploading artifacts to AWS S3: > > > > https://docs.travis-ci.com/user/uploading-artifacts/ > > > > This may alleviate the issue with accepting an unknown artifact, and > > with Travis, you have more confidence the artifact not only built but > > passed unit-tests as well. > > > > -Geoff > > > > On Mon, Jul 27, 2020 at 2:26 PM Bindul Bhowmik <bindulbhow...@gmail.com> > wrote: > > > > > > Hi Gary, > > > > > > (Please ignore if it has been discussed already) > > > > > > On Mon, Jul 27, 2020 at 12:07 PM Gary Gregory <garydgreg...@gmail.com> > wrote: > > > > > > > > Hi All, > > > > > > > > Thanks to Geoffrey Blake's help setting up a Docker Ubuntu Trusty > (14.04) > > > > environment, I am working toward creating an RC for 1.1.0, but in > order to > > > > get Mac64 support we are quite sure I need to build that binary on a > Mac, > > > > which I do not own or have simple access to. > > > > > > > > Is there an acceptable workflow for me, the Release Manager, to > procure > > > > said binary from another person? Does that person need to be on the > Commons > > > > PMC, a Commons Committer, an Apache Commons, an Apache Member, or > can it be > > > > Anyone? > > > > > > > > There is an obvious trust issue here since I would not be the one > building > > > > the Mac64 binary but would be delivering it through our dist area > and Maven > > > > Central. > > > > > > commons-crypto is built on OSX on travis. So, a thought on getting the > > > binaries out of that: > > > If you had a place for travis to upload the artifacts: you could fork > > > the repo, alter the .travis.yml to add a deployment step to upload the > > > built OSX binaries to your location. I think this gets you, the > > > release manager, a known good binary. You can add whatever 'on' > > > conditions for the deploy to only upload binaries from the tag, etc. I > > > am suggesting forking the repo, so the altered .travis.yml is not in > > > the release source tag and the secrets to upload the binary are only > > > in your github/travis org. > > > > > > > > > > > Yes, I know that in theory, Apache only delivers source code and > that our > > > > binary distributions are only a convenience, so there might be > nothing to > > > > talk about, still, I want to make sure to check on expectations and > > > > processes. > > > > > > > > Gary > > > > > > Bindul > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
