Release date for next version of Spilo

[pratapagiri]

Could you please let us know the date of the next release ?

[PaniniHode]

At least approximately)

[DanSalt]

+1

[hughcapet]

In 2024. The release cycle is unfortunately on hold now

[DanSalt]

Hi @hughcapet -- many thanks for the reply :)

Is there a post anywhere that gives more details as to why the lack of updates, and when in 2024 it's expected to resume? We currently use these images for production deployments, and so we need to consider the operational risk of a component that's not being updated frequently.

[hughcapet]

@DanSalt As I took over this project, I want to get into the details and probably rethink some processes first. That is why the current solution is simply to stop releasing. However the main branch is still updated regularly (with an exception for this month) and deployed internally in Zalando. But let me ask you, what stops you from building the image yourself? Tagging simply runs the docker build.

[DanSalt]

Thanks for the insights, @hughcapet . I think just understanding the situation helps us. Whilst we'd prefer to consume directly from the Zalando build pipelines, we can definitely build the image ourselves. Sounds like the 'pause' is more on the build and release processes, rather than the code itself. From your last comment, can we assume that successful builds will perform all the same release validation as you do internally?

[PaniniHode]

spilo16.txt It seems to build for 16 version doesn't work

[PaniniHode]

At the same time, i build image from branch dev-16 with one click and change nothing

[hughcapet]

yes, 16 support is only provided when you build from dev-16