Le samedi 21 octobre 2017, 12:32:54 CEST Robert Scholte a écrit : > > One thing I see is that we can automate a check that the current > > official-image > > is our currently recommended Maven version: it's just about adding a new > > check > > to dist-tool-plugin that will be checked every day by Jenkins job [3] > > Without talking in solutions, we have this general question: Are we > informing others by their format or are we offering some generic message > for others to make them aware there's a new version. > > This disttool solution sounds like the first one (we trigger Carlos in > some way so he can make a new image), which is exactly what SDKMan asked > us to do. Currently the tool is meant to check that the full release process has been done and tell if a step was forgotten. The tool does not trigger someone specifically: it triggers a build failure, with an explanation on what to do to fix. If nobody cares about the job failure (which happens often), nothing gets done: in general, I do care, then either I ping the offender (some of you Maven devs know what I'm talking about :) ), either I just do the job.
I don't know if adding some code and configuration to send an email to someone would be easy: I don't know if there is a smtp server available on Jenkins nodes. > > IMHO whatever we do for Docker, we should do the same for SDKMan and offer > that solution for other interested parties. summary: there is a little difference between helping a Maven dev doing the full release process (by checking forgotten steps), given he's credentials to do everything, and pinging someone who is the only one to have the credentials Regards, Hervé > > Robert > > > [1] https://github.com/carlossg/docker-maven > > > > [2] > > https://github.com/docker-library/official-images/blob/master/library/mave > > n > > > > [3] > > https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/ > > > >> If we want that dockerfile in Maven-core repo, i’m Fine with that too > > > > given the content, a separate repo more reasonable > > > >> Now the other question is how to get the image from that dockerfile into > >> docker... > > > > IIUC, that's the second point I wrote: we don't really put the image but > > update a commit reference to our Dockerfiles > > > >> I’m happy for Carlos to continue doing in a personal capacity... > > > > +1 > > I'd be happy to just have this as an official PMC asset, with Carlos as > > our > > expert who wrote the subtle bunch of images, since IIUC, it's not really > > one > > image but a collection that one can choose from > > > > Regards, > > > > Hervé > > > >> So i’d be > >> > >> “The dockerfile has been released by the Maven project and a member of > >> the > >> PMC has uploaded the image” > >> > >> > Regards, > >> > > >> > Hervé > >> > > >> > [1] https://github.com/docker-library/official-images > >> > > >> > [2] > >> > >> https://github.com/docker-library/official-images/blob/master/library/mav > >> e > >> > >> > n > >> > > >> > Le samedi 21 octobre 2017, 06:58:50 CEST Manfred Moser a écrit : > >> > > From my perspective it is just like sdkman including the > >> > >> conclusion. We > >> > >> > have > >> > > >> > > other tasks at our hands, maintaining a docker images is not > >> > >> something > >> > >> > > we > >> > > should bother with. However needs one can easily create one and > >> > >> there > >> > >> > will > >> > > >> > > be thousands of variations different users want. > >> > > > >> > > Let them create it on their own. > >> > > > >> > > Manfred > >> > > > >> > > Hervé BOUTEMY wrote on 2017-10-20 18:46: > >> > > > true, from a general perspective, it's like sdkman > >> > > > > >> > > > we need to discuss then decide if we want to maintain Maven Docker > >> > > > integration (contrary to our current decision to not maintain > >> > >> Maven > >> > >> > > > sdkman integration but let sdkman community do it) > >> > > > > >> > > > can we think about a general solution? perhaps not really a > >> > >> solution, > >> > >> > but > >> > > >> > > > a > >> > > > decision process, yes > >> > > > > >> > > > to me, on each tool integration, there are key decision drivers: > >> > > > - importance of the tool on the market > >> > > > - interest of Maven devs to actually do integration maintenance > >> > > > - complexity of integration, technical prerequisites (with IDEs, > >> > >> for > >> > >> > > > example, a dedicated independant project like m2e is necessary) > >> > > > - time factor: things evolve over time (e.g. 2 years ago, Docker > >> > >> was > >> > >> > not > >> > > >> > > > what it is nowadays) > >> > > > > >> > > > any other key driver to document? > >> > > > > >> > > > once done, we'll discuss more precisely about the Docker > >> > >> integration > >> > >> > case > >> > > >> > > > and probably finish with a vote :) > >> > > > > >> > > > Regards, > >> > > > > >> > > > Hervé > >> > > > > >> > > > Le vendredi 20 octobre 2017, 11:30:49 CEST Robert Scholte a écrit > >> > > > > >> > > >> Isn't this actually the same case as sdkman[1]? > >> > > >> Just wondering if we need to think about a general solution > >> > >> instead > >> > >> > > >> of > >> > > >> pulling everything into our project when possible. > >> > > >> > >> > > >> thanks, > >> > > >> Robert > >> > > >> > >> > > >> [1] http://markmail.org/message/oofvszmf56tbr7et > >> > > >> > >> > > >> On Thu, 19 Oct 2017 19:30:57 +0200, Hervé BOUTEMY < > >> > > >> > [email protected]> > >> > > >> > > >> wrote: > >> > > >> > great idea > >> > > >> > > >> > > >> > ok, we need a git repo at ASF > >> > > >> > > >> > > >> > what else? > >> > > >> > Is there some sort of release process? some sort of source to > >> > > >> > release? > >> > > >> > > >> > Regards, > >> > > >> > > >> > > >> > Hervé > >> > > >> > > >> > > >> > Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit : > >> > > >> >> Thanks for the pointer, Carlos! I had searched the archives, > >> > >> but > >> > >> > maybe > >> > > >> > > >> >> I > >> > > >> >> didn't go back far enough. > >> > > >> >> > >> > > >> >> I think moving these Dockerfiles into an ASF repo would be > >> > >> great > >> > >> > for > >> > > >> > > >> >> their > >> > > >> >> maintainability. > >> > > >> >> > >> > > >> >> Thanks, > >> > > >> >> > >> > > >> >> Mike > >> > > >> >> > >> > > >> >> On 2017-10-19 03:50, Carlos Sanchez <[email protected]> wrote: > >> > > >> >> > Arnaud is correct, I sent an email to users@ back on Fri, > >> > >> Nov 7, > >> > >> > > >> >> 2014,> > >> > > >> >> > >> > > >> >> > 00:23 when I created the image> > >> > > >> >> > > >> > > >> >> > > >> > > >> >> > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier > >> > >> <[email protected]> > >> > >> > > >> >> > wrote:> > >> > > >> >> > > >> > > >> >> > > These images are kindly managed by a PMC member of our > >> > >> project > >> > >> > > >> >> (Carlos) > >> > > >> >> > >> > > >> >> but> > >> > > >> >> > >> > > >> >> > > yes they aren't managed directly by the project> > >> > > >> >> > > > >> > > >> >> > > We can easily see with him to improve this IMO.> > >> > > >> >> > > > >> > > >> >> > > When he started that (several years ago) Docker wasn't > >> > >> what it > >> > >> > is > >> > > >> > > >> >> nowadays.> > >> > > >> >> > >> > > >> >> > > With docker being mainstream I agree that we can > >> > >> reconsider > >> > >> > this.> > >> > > >> > > >> >> > > The docker image build/distribution could perhaps be part > >> > >> of > >> > >> > our > >> > > >> > > >> >> release> > >> > > >> >> > >> > > >> >> > > process.> > >> > > >> >> > > > >> > > >> >> > > WDYT Carlos ?> > >> > > >> >> > > > >> > > >> >> > > On Thu, Oct 19, 2017 at 4:16 AM, Mike Drob > >> > >> <[email protected]> > >> > >> > > >> >> wrote:> > >> > > >> >> > >> > > >> >> > > > I guess the natural follow-on question is whether the > >> > >> Maven > >> > >> > > >> >> community> > >> > > >> >> > >> > > >> >> > > > would consider publishing an official set of images? Or > >> > > >> >> > >> > > >> >> alternatively> > >> > > >> >> > >> > > >> >> > > > whether they should send a takedown notice to protect > >> > >> their > >> > >> > > >> >> > > > brand > >> > > >> >> > >> > > >> >> and> > >> > > >> >> > >> > > >> >> > > > trademarks...> > >> > > >> >> > > > > >> > > >> >> > > > On 2017-10-18 18:36, "Manfred Moser" > >> > >> <[email protected] > >> > >> > > >> >> wrote:> > >> > > >> >> > >> > > >> >> > > > > No. As you can see from the github URL this is NOT an > >> > > >> > apache > >> > > >> > > >> >> URL.> > >> > > >> >> > >> > > >> >> > > > > https://github.com/carlossg/docker-maven> > >> > > >> >> > > > > > >> > > >> >> > > > > > >> > > >> >> > > > > Mike Drob wrote on 2017-10-18 16:32:> > >> > > >> >> > > > > > >> > > >> >> > > > > > Hello,> > >> > > >> >> > > > > > > >> > > >> >> > > > > > Are the images at https://hub.docker.com/r/_/maven/ > >> > > >> >> > >> > > >> >> considered to > >> > > >> >> > >> > > >> >> be> > >> > > >> >> > >> > > >> >> > > > official> > >> > > >> >> > > > > >> > > >> >> > > > > > maven docker images and blessed/published by the > >> > >> PMC?> > >> > >> > > >> >> > > > > > Thanks,> > >> > > >> >> > > > > > Mike> > >> > > >> > ---------------------------------------------------------------------> > >> > > >> > > >> >> > > > > > To unsubscribe, e-mail: > >> > [email protected]> > >> > > >> > > >> >> > > > > > For additional commands, e-mail: > >> > > >> >> > > > > > [email protected]> > >> > > >> > ---------------------------------------------------------------------> > >> > > >> > > >> >> > > > > To unsubscribe, e-mail: > >> [email protected] > >> > >> > > >> >> > > > > For additional commands, e-mail: > >> > [email protected]> > >> > > >> > > >> > ---------------------------------------------------------------------> > >> > > >> > > >> >> > > > To unsubscribe, e-mail: > >> [email protected]> > >> > >> > > >> >> > > > For additional commands, e-mail: > >> [email protected] > >> > >> > > >> >> > > --> > >> > > >> >> > > -----> > >> > > >> >> > > Arnaud H�ritier> > >> > > >> >> > > http://aheritier.net> > >> > > >> >> > > Mail/GTalk: aheritier AT gmail DOT com> > >> > > >> >> > > Twitter/Skype : aheritier> > >> > > >> > --------------------------------------------------------------------- > >> > > >> > > >> > To unsubscribe, e-mail: [email protected] > >> > > >> > For additional commands, e-mail: [email protected] > >> > >> --------------------------------------------------------------------- > >> > >> > > >> To unsubscribe, e-mail: [email protected] > >> > > >> For additional commands, e-mail: [email protected] > >> > >> --------------------------------------------------------------------- > >> > >> > > > To unsubscribe, e-mail: [email protected] > >> > > > For additional commands, e-mail: [email protected] > >> > >> --------------------------------------------------------------------- > >> > >> > > To unsubscribe, e-mail: [email protected] > >> > > For additional commands, e-mail: [email protected] > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [email protected] > >> > For additional commands, e-mail: [email protected] > >> > > >> > -- > >> > >> Sent from my phone > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
