Hi,
> IMO using ’latest’ is a really bad practice to refer to any kind of Docker
> image as no one really knows what version this image refers to etc. This is
> makes it unclear for anyone using StreamPipes what he/she is using.
It’s also likely to be against ASF policy on distributing code to
"big" release.
Dominik
-Original Message-
From: Patrick Wiener
Sent: Monday, September 21, 2020 10:31 AM
To: dev@streampipes.apache.org
Subject: Re: Release version of installer
IMO using ’latest’ is a really bad practice to refer to any kind of Docker
image as no one really
after the release is a
>>> good idea!
>>>
>>> Dominik
>>>
>>> -Original Message-
>>> From: Philipp Zehnder
>>> Sent: Friday, September 18, 2020 10:05 AM
>>> To: dev@streampipes.apache.org
>>> Subject: Re: R
the future as we wouldn't need to release a new version every time along
>> with the core.
>>
>> Starting a discussion on merging the two other repos after the release is a
>> good idea!
>>
>> Dominik
>>
>> -Original Message-
>> From: Ph
other repos after the release is a
good idea!
Dominik
-Original Message-
From: Philipp Zehnder
Sent: Friday, September 18, 2020 10:05 AM
To: dev@streampipes.apache.org
Subject: Re: Release version of installer
Hi,
yes Patrick did an awesome job with the new structure and documentation
Hi,
yes Patrick did an awesome job with the new structure and documentation.
But this would mean we cannot change anything in the CLI, right?
So we can not add more commands or new services, or would this still be
possible?
Maybe we can find a solution that doesn't require the installer to be
Hi,
I think Patrick did some really great work in improving (and documenting!) the
installer (Docker, CLI and k8s) for the upcoming version and I’ve just seen it
even has a script for automatically updating versions.
So I just thought, why not taking the installer out of the release cycle
