openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Santana <csantan...@gmail.com>
Subject Re: Graduation (was: Podling Report Reminder - December 2018)
Date Mon, 03 Dec 2018 23:55:20 GMT
The position of the ASF is that the foundation release source artifacts
only.

For convenient binaries/artifacts I agree they are useful to provide, but
there are not consider a release or artifacts that we need a vote on it.

I don't think this is blocker to graduate, having releases (ie source tgz)
is the minimum requirement.

After graduation we can continue the discussion and implementation on of
this convenient official/blessed artifacts (docker image, maven, npm) via
ASF automation process after doing a release
>1) How to ensure someone following just this list can follow the
action. Might be solved by just clearly documenting where to look so
that newbies and occasional contributors can jump in easily, and
making sure the places that are linked to don't require permanent
attention.

Bertrand for the information item I think best visible place would be the
website, improve it with more info and guidance on how to contribute and
where to look and maybe more links to the biweekly notes, and monthly
reports

>2) Clarifying where and how releases happen, last time I looked (2-3
months ago?) some "releases" were still happening directly from GitHub
repositories without Incubator PMC votes.

Bertrand I don't follow what you mean by releases directly from github
without PMC votes?
All our releases have gone thru Votes first and then publish into the
Apache server, and link in the website.
http://openwhisk.incubator.apache.org/downloads.html

And we will continue releasing new modules, and releasing updates to
already released modules.

I think Vincent will cut another release of core and java for the package
namespace rename
I think Dave will do the composer-python onced legally cleared
I have intentions to release new runtimes ruby,go and updated ones

I think the Train of releases will continue at faster pace hopefully as we
improve docs and tools to help release manager to go thru the voting and
publishing or releases.

-- Carlos








On Mon, Dec 3, 2018 at 3:01 PM David P Grove <groved@us.ibm.com> wrote:

>
>
>
> Bertrand Delacretaz <bdelacretaz@apache.org> wrote on 12/03/2018 10:51:24
> AM:
> >
> > On Mon, Dec 3, 2018 at 4:00 PM David P Grove <groved@us.ibm.com> wrote:
> > > ...it
> > > seems that our release process is being impeded by a lack of engagement
> > > from eligible voters on the IPMC mailing list...
> >
> > I agree, and besides having more mentors one way to fix that is to
> > graduate ;-)
>
> +1
>
> >
> > From my point of view as one incubation mentor there are two things
> > that need to be addressed before graduation, and both might not need a
> > lot of work, I just might not have the right information to consider
> > these issues solved.
> > ...
> > 2) Clarifying where and how releases happen, last time I looked (2-3
> > months ago?) some "releases" were still happening directly from GitHub
> > repositories without Incubator PMC votes.
> >
>
> Agreed. There is still work to be done to formalize and automate our
> releases. This is especially true around the reality of users expecting to
> consume pre-built artifacts from dockerhub, maven, npmjs, pypi, homebrew,
> etc.  IMO the project does not yet have a good handle on how we get from
> official Apache source releases to the artifacts that users will actually
> consume from these diverse channels.
>
> A vanishingly small fraction of users actually want (or are even able to)
> to take a source release and build it themselves, especially across all the
> different technologies that make up OpenWhisk.
>
> --dave
>


-- 
Carlos Santana
<csantana23@gmail.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message