Skip to content
This repository was archived by the owner on Jun 9, 2025. It is now read-only.

Conversation

@patrickunterwegs
Copy link
Member

No description provided.

@patrickunterwegs patrickunterwegs marked this pull request as draft January 26, 2023 08:57
@patrickunterwegs patrickunterwegs marked this pull request as ready for review February 10, 2023 11:47
@patrickunterwegs
Copy link
Member Author

Hi @rfc2822 , we should make sure DAVx5 and jtx Board get released together for those changes!

@rfc2822
Copy link
Member

rfc2822 commented Feb 10, 2023

Hi @rfc2822 , we should make sure DAVx5 and jtx Board get released together for those changes!

Which DAVx⁵ version number/code did you finally set as minimum requirement in jtxBoard, 4.3.1? We could create issues in DAVx5 and jtxBoard and link them together (and assign the 4.3.1 milestone at least for the DAVx5 issue) to make sure we don't forget it.

@rfc2822 rfc2822 merged commit de24b0a into main Feb 10, 2023
@rfc2822 rfc2822 deleted the jtx-board-2-3-new-recur-handling branch February 10, 2023 12:03
@patrickunterwegs
Copy link
Member Author

Hi @rfc2822 , we should make sure DAVx5 and jtx Board get released together for those changes!

Which DAVx⁵ version number/code did you finally set as minimum requirement in jtxBoard, 4.3.1? We could create issues in DAVx5 and jtxBoard and link them together (and assign the 4.3.1 milestone at least for the DAVx5 issue) to make sure we don't forget it.

Yes, the check is for 4.3.1, so the app checks for version code 403010000.
You mean to not forget what exactly?

@rfc2822
Copy link
Member

rfc2822 commented Feb 10, 2023

You mean to not forget what exactly?

Just that we have to release the version at the same time. Before releasing, we have a look at the respective milestone, so we are remembered then.

@patrickunterwegs
Copy link
Member Author

For me it's okay just to agree on it now, I'd like to release a beta as soon as possible, maybe on Monday?

@rfc2822
Copy link
Member

rfc2822 commented Feb 10, 2023

@devvv4ever @sunkup What do you think? We just had the 4.3 release, but we could do 4.3.1 soon with only this patch + the new DAV:owner detection. The latter one is almost ready I think, but we'd need some beta time.

@patrickunterwegs
Copy link
Member Author

@devvv4ever @sunkup What do you think? We just had the 4.3 release, but we could do 4.3.1 soon with only this patch + the new DAV:owner detection. The latter one is almost ready I think, but we'd need some beta time.

Sounds good 👍

@rfc2822
Copy link
Member

rfc2822 commented Feb 10, 2023

Perfect, please follow up in bitfireAT/davx5#209

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants