> We can either (a) wait out a release cycle of clientgo/cli/wskdeploy to get a
> fixed cli or (b) leave the bash installers in for this release and cleanup
> after the next cli release.
I would do it later then.
-r
On 2019/06/17 13:07:33, Rodric Rabbah wrote:
> If the weather package is functional and can run with newer node kinds then
> I’d favor keeping it.
I verified weather is functional with nodejs:10. Have a PR pending to update
the documentation. Will merge as soon as the current travis
+1 to everything Rodric said!
On Mon, 17 Jun 2019 at 14:07, Rodric Rabbah wrote:
>
> If the weather package is functional and can run with newer node kinds then
> I’d favor keeping it.
>
> I’d favor removing the combinators as we have composer now and we didn’t
> document them properly (my
If the weather package is functional and can run with newer node kinds then I’d
favor keeping it.
I’d favor removing the combinators as we have composer now and we didn’t
document them properly (my fault).
I would consider removing the bash installers since they’re redundant with the
wsk
As Rodric mentioned in [1], the catalog is the last package we need to
release before we can start on the main repo.
This is a discussion thread to figure out what (if anything) needs to be
done before we can start the release process. Here are three questions I
have:
1. Should we remove the
