RE: [Discuss] Unify the release artifacts?

[Dominik Riemer <ri...@apache.org>]

Hi,
as it seems there are no more comments and our next release is not too far away, I'll close this thread and start a vote soon (as this change proposes to archive existing source repos).

Dominik

-----Original Message-----
From: Patrick Wiener <wi...@apache.org> 
Sent: Tuesday, August 31, 2021 10:23 AM
To: dev@streampipes.apache.org
Subject: Re: [Discuss] Unify the release artifacts?

Hi,

I also added some thoughts to the wiki which are basically some pro/con aspects for both of your suggestions.
Overall, I don’t have a favorite as of now :/ maybe some other folks do have more suggestions.

Patrick

> Am 31.08.2021 um 07:23 schrieb Philipp Zehnder <ze...@apache.org>:
> 
> Hi Dominik,
> 
> I added my thoughts to the wiki page.
> I am really looking forward to the integration of our repositories, because this will also allow us to integrate the cypress e2e tests into the gitlab actions pipeline.
> 
> For example, we can create a trigger for pull requests to run the e2e tests before it can be merged.
> This will reduce the manual testing effort for the reviewer and give us more confidence that the changes will not break anything.
> 
> Philipp
> 
> 
>> On 30. Aug 2021, at 23:20, Dominik Riemer <ri...@apache.org> wrote:
>> 
>> Hi all,
>> 
>> I've created a wiki page to organize the unification of our three 
>> repos at [1]
>> 
>> Please comment or add any ideas how we can make this as smooth as possible!
>> 
>> I suggest to have a vote on this once there is consensus as the process also requires the extensions and installer repos to be archived.
>> 
>> Dominik
>> 
>> [1] 
>> https://cwiki.apache.org/confluence/display/STREAMPIPES/Merging+repos
>> 
>> On 2021/08/17 19:54:27, Philipp Zehnder <ze...@apache.org> wrote: 
>>> Hi Dominik,
>>> 
>>> yes this is a good idea, it is a good chance to clean up our branches.
>>> 
>>> Philipp
>>> 
>>>> On 17. Aug 2021, at 21:51, Dominik Riemer <ri...@apache.org> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> to proceed with the integration of the extensions and installer repo into the main project, I'll soon start to clean up some branches that are no longer needed - it would be great if you could have a look and also remove merged or now obsolete branches.
>>>> 
>>>> Dominik
>>>> 
>>>> On 2021/07/27 11:01:27, Dominik Riemer <ri...@apache.org> wrote: 
>>>>> Hi,
>>>>> 
>>>>> sounds that there is a strong preference towards merging all three repos.
>>>>> 
>>>>> So I guess there are at least two open questions:
>>>>> * @Chris Should we have a vote on this? I think that removing a source repo requires a vote as per ASF rules?
>>>>> * How do we technically merge the repos? It would be nice to preserve the Git history, but I'm not sure how we can handle this as I assume there are also a few branches that would need to be merged into individual branches of the core project.
>>>>> 
>>>>> Any thoughts and experiences are welcome!
>>>>> 
>>>>> Dominik
>>>>> 
>>>>> On 2021/07/21 11:52:56, Patrick Wiener <wi...@apache.org> wrote: 
>>>>>> +1 for merging everything into one code base including the installation options. 
>>>>>> 
>>>>>> It’s related anyways and would also make maintaining and 
>>>>>> developing things much easier
>>>>>> 
>>>>>> Patrick
>>>>>> 
>>>>>>> Am 21.07.2021 um 13:44 schrieb Dominik Riemer <ri...@apache.org>:
>>>>>>> 
>>>>>>> Just a second-thought addition:
>>>>>>> Maybe we should indeed consider to also merge the whole installer into the core project - I think most users will survive downloading a larger bundle and we should probably try to make the release process as simple as possible so that we can have future releases more frequently and also don't require a 6-week release process.
>>>>>>> 
>>>>>>> Dominik
>>>>>>> 
>>>>>>> On 2021/07/21 11:32:22, Dominik Riemer <ri...@apache.org> wrote: 
>>>>>>>> Hi Chris,
>>>>>>>> 
>>>>>>>> thanks for bringing this up and a strong +1 for simplifying the release process.
>>>>>>>> 
>>>>>>>> We already had this discussion in the past and didn't follow up on this.
>>>>>>>> 
>>>>>>>> My preference would be to merge the incubator-streampipes-extensions project into the main project to have a single build for the whole project. Concerning the installer, I'd rather prefer to keep it as a standalone project as this should be just a minimal-size artifact to provide installation scripts for Docker, K8s and the CLI. But as the installer doesn't work anyways at release validation time as the artifacts are not yet available, it could be a separate vote process and we could also easily reduce the frequency of releases by pointing to the latest release in the version tag.
>>>>>>>> 
>>>>>>>> What do others think? I'd personally like to at least merge the extensions and core projects soon.
>>>>>>>> 
>>>>>>>> Dominik
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On 2021/07/21 08:48:00, Christofer Dutz <ch...@c-ware.de> wrote: 
>>>>>>>>> Hi all,
>>>>>>>>> 
>>>>>>>>> I have observed quite a bit of hesitation of IPMC votes to come in.
>>>>>>>>> One thing I noticed when reviewing your latest release (and the prior ones):
>>>>>>>>> 
>>>>>>>>> You currently have 3 release artifacts:
>>>>>>>>> - Core
>>>>>>>>> - Extensions
>>>>>>>>> - Installer
>>>>>>>>> 
>>>>>>>>> Unfortunately thoroughly doing a release validation is like 
>>>>>>>>> doing 3 release validations as most of the steps involved have 
>>>>>>>>> to be executed 3 times.
>>>>>>>>> 
>>>>>>>>> This definitely caused a bit of frustration when I was 
>>>>>>>>> finished with the first artifact and noticed there were 2 more 
>>>>>>>>> to go. I could imagine this could be something that might be keeping the others from voting.
>>>>>>>>> 
>>>>>>>>> Would it be possible to merge the release artifacts to one big bundle? 
>>>>>>>>> In that case it would drastically reduce the amount of work.
>>>>>>>>> 
>>>>>>>>> Chris
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>> 
>>> 
>