New version #1158

New Issue

Michaelpalacce · 2022-04-09T06:46:26Z

Michaelpalacce commented

2022-04-09 06:46:26 +00:00

Last release of vikunja was 09. 2022

Is it possible to do a new release with all the new features for both the API and the frontend?

Last release of vikunja was 09. 2022 Is it possible to do a new release with all the new features for both the API and the frontend?

konrad commented

2022-04-09 06:53:59 +00:00

I hope to release a new version this month or in the beginning of may. There's still a few bugs I'd like to fix before releasing.

If you want to use the new features you can alway switch to unstable.

I hope to release a new version this month or in the beginning of may. There's still a few bugs I'd like to fix before releasing. If you want to use the new features you can alway switch to unstable.

🎉 2

xeruf commented

2022-07-13 11:15:27 +00:00

Is unstable usable, so I do not have to fear corruption or something, are you yourself using it productively?

Can I run two instances, unstable and stable, on the same database?

Is unstable usable, so I do not have to fear corruption or something, are you yourself using it productively? Can I run two instances, unstable and stable, on the same database?

konrad commented

2022-07-13 14:09:02 +00:00

I hope to release a new version this month or in the beginning of may.

Well this turned out to take longer than I expected :)

Is unstable usable, so I do not have to fear corruption or something, are you yourself using it productively?

My instance runs on unstable. There are other people in the community who do that as well, it is very usable but there's a higher chance encountering bugs. Critical bugs are fixed relatively quickly most of the time, as long as you don't mind those and make backups it should be fine.

Can I run two instances, unstable and stable, on the same database?

I would not do that. That will likely break your database at some point.

> I hope to release a new version this month or in the beginning of may. Well this turned out to take longer than I expected :) > Is unstable usable, so I do not have to fear corruption or something, are you yourself using it productively? My instance runs on unstable. There are other people in the community who do that as well, it is very usable but there's a higher chance encountering bugs. Critical bugs are fixed relatively quickly most of the time, as long as you don't mind those and make backups it should be fine. > Can I run two instances, unstable and stable, on the same database? I would not do that. That will likely break your database at some point.

xeruf commented

2022-07-13 16:28:02 +00:00

it is very usable but there's a higher chance encountering bugs

Considering the number of bugs I already encountered on stable, I am questioning this :P
I guess I'll try it, I'm just a little wary because migrating back is probably not really an option.

A distinction of unstable into beta and nightly could be nice, where beta-builds are at least pretty safe to not screw anything up.

> it is very usable but there's a higher chance encountering bugs Considering the number of bugs I already encountered on stable, I am questioning this :P I guess I'll try it, I'm just a little wary because migrating back is probably not really an option. A distinction of unstable into `beta` and `nightly` could be nice, where beta-builds are at least pretty safe to not screw anything up.

konrad commented

2022-07-13 16:55:35 +00:00

Once we are at 1.0 I'd like to do rcs. But the current unstable builds are more like nightlies.