You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by Dominik Riemer <ri...@apache.org> on 2021/06/04 12:32:00 UTC
What about a new release?
Hi all,
as our last release 0.67.0 is already some while ago, and we have so many
new features and improvements, I think it is time to plan a new release!
Are there any features or things you are still working on that should make
it into the next version? If not, we can move all issues that are still open
to 0.69.0 and cut the release branch within the next week.
I'd volunteer as a release manager for this release, but if anyone else
wants to do it as well, I'll be happy to assist in the process.
Cheers
Dominik
Re: What about a new release?
Posted by Patrick Wiener <wi...@apache.org>.
Hi,
I went through the issues and [1] can be closed - If for some reason it doesn't work with the latest changes in dev
we can reopen it.
I tested k8s [2] deployment and it worked for me, however the user that reported the issue still wanted to try the fixes
at his setup and has not yet reported back. We can ping him and decide what to do in a couple of days.
There are a couple of issues related to consul such as [3],[4] where I’m not quite sure wether these aren’t resolved due
to the new service builder concept? @Dominik can you comment on this?
Finally, [5] used to be fixed, but I experience some issues with single value static selection in the UI such that upon initializing
the customization dialog of this sink, the radio button selects the default value for a configuration option, but later sends it as a
„null“ value to the backend (Current workaround: actively select another option value then select the original one).
So this is not really an issue of the sink itself but within the UI I guess.
Patrick
[1] https://issues.apache.org/jira/browse/STREAMPIPES-252 <https://issues.apache.org/jira/browse/STREAMPIPES-252>
[2] https://issues.apache.org/jira/browse/STREAMPIPES-264 <https://issues.apache.org/jira/browse/STREAMPIPES-264>
[3] https://issues.apache.org/jira/browse/STREAMPIPES-224 <https://issues.apache.org/jira/browse/STREAMPIPES-224>
[4] https://issues.apache.org/jira/browse/STREAMPIPES-223 <https://issues.apache.org/jira/browse/STREAMPIPES-223>
[5] https://issues.apache.org/jira/browse/STREAMPIPES-299 <https://issues.apache.org/jira/browse/STREAMPIPES-299>
> Am 16.06.2021 um 07:15 schrieb Philipp Zehnder <ze...@apache.org>:
>
> Hi Dominik,
>
> thanks for cleaning up our issues.
> I am currently working on refactoring the connect UI.
> I think we should not include the refactoring in this release, because it still requires some work, therefore I moved the issues related to this.
>
> We used to have some end2end tests with cypress.io. I recently started to reactivate them, because I think they will improve the quality of StreamPipes.
> We have a lot of UI functionalities as well as different components that interact with third party systems. It takes a lot of time and is very error prone to test everything manually.
> Since I'm not quite sure yet what the best setup for the testing framework is, I'd be happy to discuss it with you guys.
>
> Philipp
>
>> On 15. Jun 2021, at 19:11, Dominik Riemer <ri...@apache.org> wrote:
>>
>> Hi,
>> I now went through the list of open issues for 0.68.0 and either moved open issues to 0.69.0 or closed issues which I believe have been resolved.
>> There are still some open issues targeted for 0.68.0 where I'm not sure about the status - can you please have a quick look at these issues?
>> I plan to create the release branch within the next days.
>>
>> Dominik
>>
>> On 2021/06/08 14:26:02, udeho <ud...@student.kit.edu> wrote:
>>> Hi,
>>>
>>> just merged the open PR for the changes in the SQL sinks, so no more to-dos from my side either.
>>> I am also in favor of a new release.
>>>
>>> Cheers
>>> Tim
>>>
>>> On Juni 7 2021, at 9:13 am, Patrick Wiener <wi...@apache.org> wrote:
>>>> Hi,
>>>>
>>>> looks good to me - there are already several new features
>>>> but also some important fixes. As mentioned, we can push
>>>> the other minor open issues to 0.69.0 to get this one on the road
>>>> especially with ApacheCon Asia ahead of us in August it would be
>>>> great to have the 0.68.0 version out :)
>>>>
>>>> Patrick
>>>>> Am 06.06.2021 um 10:10 schrieb Philipp Zehnder <ze...@apache.org>:
>>>>>
>>>>> Hi Dominik,
>>>>>
>>>>> thanks for starting the discussion on the next release.
>>>>> From my side, there are no open points.
>>>>> Then, as you wrote, we can push all open features to the next version and start testing the current version.
>>>>>
>>>>> Philipp
>>>>>
>>>>>
>>>>>> On 4. Jun 2021, at 14:32, Dominik Riemer <ri...@apache.org> wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>>
>>>>>>
>>>>>> as our last release 0.67.0 is already some while ago, and we have so many
>>>>>> new features and improvements, I think it is time to plan a new release!
>>>>>>
>>>>>> Are there any features or things you are still working on that should make
>>>>>> it into the next version? If not, we can move all issues that are still open
>>>>>> to 0.69.0 and cut the release branch within the next week.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I'd volunteer as a release manager for this release, but if anyone else
>>>>>> wants to do it as well, I'll be happy to assist in the process.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> Dominik
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>
Re: What about a new release?
Posted by Philipp Zehnder <ze...@apache.org>.
Hi Dominik,
thanks for cleaning up our issues.
I am currently working on refactoring the connect UI.
I think we should not include the refactoring in this release, because it still requires some work, therefore I moved the issues related to this.
We used to have some end2end tests with cypress.io. I recently started to reactivate them, because I think they will improve the quality of StreamPipes.
We have a lot of UI functionalities as well as different components that interact with third party systems. It takes a lot of time and is very error prone to test everything manually.
Since I'm not quite sure yet what the best setup for the testing framework is, I'd be happy to discuss it with you guys.
Philipp
> On 15. Jun 2021, at 19:11, Dominik Riemer <ri...@apache.org> wrote:
>
> Hi,
> I now went through the list of open issues for 0.68.0 and either moved open issues to 0.69.0 or closed issues which I believe have been resolved.
> There are still some open issues targeted for 0.68.0 where I'm not sure about the status - can you please have a quick look at these issues?
> I plan to create the release branch within the next days.
>
> Dominik
>
> On 2021/06/08 14:26:02, udeho <ud...@student.kit.edu> wrote:
>> Hi,
>>
>> just merged the open PR for the changes in the SQL sinks, so no more to-dos from my side either.
>> I am also in favor of a new release.
>>
>> Cheers
>> Tim
>>
>> On Juni 7 2021, at 9:13 am, Patrick Wiener <wi...@apache.org> wrote:
>>> Hi,
>>>
>>> looks good to me - there are already several new features
>>> but also some important fixes. As mentioned, we can push
>>> the other minor open issues to 0.69.0 to get this one on the road
>>> especially with ApacheCon Asia ahead of us in August it would be
>>> great to have the 0.68.0 version out :)
>>>
>>> Patrick
>>>> Am 06.06.2021 um 10:10 schrieb Philipp Zehnder <ze...@apache.org>:
>>>>
>>>> Hi Dominik,
>>>>
>>>> thanks for starting the discussion on the next release.
>>>> From my side, there are no open points.
>>>> Then, as you wrote, we can push all open features to the next version and start testing the current version.
>>>>
>>>> Philipp
>>>>
>>>>
>>>>> On 4. Jun 2021, at 14:32, Dominik Riemer <ri...@apache.org> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>>
>>>>>
>>>>> as our last release 0.67.0 is already some while ago, and we have so many
>>>>> new features and improvements, I think it is time to plan a new release!
>>>>>
>>>>> Are there any features or things you are still working on that should make
>>>>> it into the next version? If not, we can move all issues that are still open
>>>>> to 0.69.0 and cut the release branch within the next week.
>>>>>
>>>>>
>>>>>
>>>>> I'd volunteer as a release manager for this release, but if anyone else
>>>>> wants to do it as well, I'll be happy to assist in the process.
>>>>>
>>>>>
>>>>>
>>>>> Cheers
>>>>>
>>>>> Dominik
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
Re: What about a new release?
Posted by Dominik Riemer <ri...@apache.org>.
Hi,
I now went through the list of open issues for 0.68.0 and either moved open issues to 0.69.0 or closed issues which I believe have been resolved.
There are still some open issues targeted for 0.68.0 where I'm not sure about the status - can you please have a quick look at these issues?
I plan to create the release branch within the next days.
Dominik
On 2021/06/08 14:26:02, udeho <ud...@student.kit.edu> wrote:
> Hi,
>
> just merged the open PR for the changes in the SQL sinks, so no more to-dos from my side either.
> I am also in favor of a new release.
>
> Cheers
> Tim
>
> On Juni 7 2021, at 9:13 am, Patrick Wiener <wi...@apache.org> wrote:
> > Hi,
> >
> > looks good to me - there are already several new features
> > but also some important fixes. As mentioned, we can push
> > the other minor open issues to 0.69.0 to get this one on the road
> > especially with ApacheCon Asia ahead of us in August it would be
> > great to have the 0.68.0 version out :)
> >
> > Patrick
> > > Am 06.06.2021 um 10:10 schrieb Philipp Zehnder <ze...@apache.org>:
> > >
> > > Hi Dominik,
> > >
> > > thanks for starting the discussion on the next release.
> > > From my side, there are no open points.
> > > Then, as you wrote, we can push all open features to the next version and start testing the current version.
> > >
> > > Philipp
> > >
> > >
> > >> On 4. Jun 2021, at 14:32, Dominik Riemer <ri...@apache.org> wrote:
> > >>
> > >> Hi all,
> > >>
> > >>
> > >>
> > >> as our last release 0.67.0 is already some while ago, and we have so many
> > >> new features and improvements, I think it is time to plan a new release!
> > >>
> > >> Are there any features or things you are still working on that should make
> > >> it into the next version? If not, we can move all issues that are still open
> > >> to 0.69.0 and cut the release branch within the next week.
> > >>
> > >>
> > >>
> > >> I'd volunteer as a release manager for this release, but if anyone else
> > >> wants to do it as well, I'll be happy to assist in the process.
> > >>
> > >>
> > >>
> > >> Cheers
> > >>
> > >> Dominik
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> >
>
>
Re: What about a new release?
Posted by udeho <ud...@student.kit.edu>.
Hi,
just merged the open PR for the changes in the SQL sinks, so no more to-dos from my side either.
I am also in favor of a new release.
Cheers
Tim
On Juni 7 2021, at 9:13 am, Patrick Wiener <wi...@apache.org> wrote:
> Hi,
>
> looks good to me - there are already several new features
> but also some important fixes. As mentioned, we can push
> the other minor open issues to 0.69.0 to get this one on the road
> especially with ApacheCon Asia ahead of us in August it would be
> great to have the 0.68.0 version out :)
>
> Patrick
> > Am 06.06.2021 um 10:10 schrieb Philipp Zehnder <ze...@apache.org>:
> >
> > Hi Dominik,
> >
> > thanks for starting the discussion on the next release.
> > From my side, there are no open points.
> > Then, as you wrote, we can push all open features to the next version and start testing the current version.
> >
> > Philipp
> >
> >
> >> On 4. Jun 2021, at 14:32, Dominik Riemer <ri...@apache.org> wrote:
> >>
> >> Hi all,
> >>
> >>
> >>
> >> as our last release 0.67.0 is already some while ago, and we have so many
> >> new features and improvements, I think it is time to plan a new release!
> >>
> >> Are there any features or things you are still working on that should make
> >> it into the next version? If not, we can move all issues that are still open
> >> to 0.69.0 and cut the release branch within the next week.
> >>
> >>
> >>
> >> I'd volunteer as a release manager for this release, but if anyone else
> >> wants to do it as well, I'll be happy to assist in the process.
> >>
> >>
> >>
> >> Cheers
> >>
> >> Dominik
> >>
> >>
> >>
> >>
> >>
> >
>
Re: What about a new release?
Posted by Patrick Wiener <wi...@apache.org>.
Hi,
looks good to me - there are already several new features
but also some important fixes. As mentioned, we can push
the other minor open issues to 0.69.0 to get this one on the road
especially with ApacheCon Asia ahead of us in August it would be
great to have the 0.68.0 version out :)
Patrick
> Am 06.06.2021 um 10:10 schrieb Philipp Zehnder <ze...@apache.org>:
>
> Hi Dominik,
>
> thanks for starting the discussion on the next release.
> From my side, there are no open points.
> Then, as you wrote, we can push all open features to the next version and start testing the current version.
>
> Philipp
>
>
>> On 4. Jun 2021, at 14:32, Dominik Riemer <ri...@apache.org> wrote:
>>
>> Hi all,
>>
>>
>>
>> as our last release 0.67.0 is already some while ago, and we have so many
>> new features and improvements, I think it is time to plan a new release!
>>
>> Are there any features or things you are still working on that should make
>> it into the next version? If not, we can move all issues that are still open
>> to 0.69.0 and cut the release branch within the next week.
>>
>>
>>
>> I'd volunteer as a release manager for this release, but if anyone else
>> wants to do it as well, I'll be happy to assist in the process.
>>
>>
>>
>> Cheers
>>
>> Dominik
>>
>>
>>
>>
>>
>
Re: What about a new release?
Posted by Philipp Zehnder <ze...@apache.org>.
Hi Dominik,
thanks for starting the discussion on the next release.
From my side, there are no open points.
Then, as you wrote, we can push all open features to the next version and start testing the current version.
Philipp
> On 4. Jun 2021, at 14:32, Dominik Riemer <ri...@apache.org> wrote:
>
> Hi all,
>
>
>
> as our last release 0.67.0 is already some while ago, and we have so many
> new features and improvements, I think it is time to plan a new release!
>
> Are there any features or things you are still working on that should make
> it into the next version? If not, we can move all issues that are still open
> to 0.69.0 and cut the release branch within the next week.
>
>
>
> I'd volunteer as a release manager for this release, but if anyone else
> wants to do it as well, I'll be happy to assist in the process.
>
>
>
> Cheers
>
> Dominik
>
>
>
>
>