Eya, I don't think it necessarily falls to you. Whomever is doing the work needs to open a discussion thread. We should probably add this to our documentation so that it doesn't feel like anyone specifically is being singled out.
This is new to all of us, there will inevitably be mistakes that we can learn from and add to our documentation. John On Wed, Apr 6, 2022 at 9:54 AM Eya Badal <e...@apache.org> wrote: > Next time, I will open a discussion thread so everyone can have visibility > on the steps and actions that need to be taken. > > As of now, I believe we need to have a better system to build the docker > and push it to the docker hub. > > Thank you, > Eya > > On 2022/04/06 16:48:47 John Gemignani wrote: > > My issues are twofold - > > > > 1. Issues that involve the master repository, like this one, need to > be > > addressed or communicated to the entire team. > > 2. We do not delete anything from the master repository unless there > is > > a compelling, valid reason. And, deletes, even tags, need to be > > communicated to the entire team. > > > > Both of these basically come down to communication and verification. We > > need to make sure everyone understands that anything that modifies the > > master repository is communicated and okayed by others. > > > > John > > > > On Wed, Apr 6, 2022 at 9:17 AM Nicholas Sorrell <n...@cint.io> wrote: > > > > > Hi John, > > > > > > The automated email is certainly misleading, as I don't know where it's > > > getting the 0.3.0 stuff from. > > > > > > Here's the full context of the tagging: > > > - Eya and I were trying to get the automated build to trigger at Docker > > > Hub (https://hub.docker.com/r/apache/age) > > > - I pushed a v0.7.0 annotated tag (on Saturday 2-APR) on top of the > > > v0.7.0-rc0 tag (same commit hash (d0175f4)) to trigger the build > > > - The build did not trigger at Docker Hub, so Eya and I worked > together to > > > fix the build trigger at Docker Hub > > > - To re-trigger the build for v0.7.0, I first had to delete the > existing > > > v0.7.0 tag and then push a new one at the same commit hash (d0175f4) > > > - That tag triggered a successful build at Docker Hub, and the tag can > be > > > viewed here as the most recent tag: > > > https://github.com/apache/incubator-age/tags > > > - The release, assets, and source code were not altered in any way, > this > > > was only a tag added to tree > > > > > > Hope this helps, and happy to answer any other questions. > > > -Nick > > > > > > ________________________________ > > > From: John Gemignani <john.gemign...@bitnine.net> > > > Sent: Wednesday, April 6, 2022 11:52 AM > > > To: dev@age.apache.org <dev@age.apache.org>; Nicholas Sorrell < > > > n...@cint.io> > > > Cc: comm...@age.apache.org <comm...@age.apache.org> > > > Subject: Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 -> > > > b5cdd67) > > > > > > @Nicholas Sorrell<mailto:n...@cint.io> > > > > > > What was done that triggered this? > > > > > > John > > > > > > On Tue, Apr 5, 2022 at 4:38 PM <sorr...@apache.org<mailto: > > > sorr...@apache.org>> wrote: > > > This is an automated email from the ASF dual-hosted git repository. > > > > > > sorrell pushed a change to annotated tag v0.7.0 > > > in repository https://gitbox.apache.org/repos/asf/incubator-age.git > > > > > > > > > *** WARNING: tag v0.7.0 was modified! *** > > > > > > from d0175f4 (commit) > > > to b5cdd67 (tag) > > > tagging d0175f4a2fb03f28c356ea43da3bd48a47f5ef42 (commit) > > > replaces v0.3.0.rc0-incubating > > > by Nick Sorrell > > > on Tue Apr 5 19:37:34 2022 -0400 > > > > > > - Log ----------------------------------------------------------------- > > > v0.7.0 > > > ----------------------------------------------------------------------- > > > > > > > > > No new revisions were added by this update. > > > > > > Summary of changes: > > > > > > > > >
