New version #1158

Closed
opened 6 months ago by Michaelpalacce · 6 comments

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?
Owner

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.

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?
Owner

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.

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.
Owner

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

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

Closing this as I belive it has been solved, please ping if you're still having issues with it.

Closing this as I belive it has been solved, please ping if you're still having issues with it.
konrad closed this issue 1 day ago
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/api#1158
Loading…
There is no content yet.