Add _sync_id for collections

[sunkup]

For https://github.com/bitfireAT/davx5/issues/603 .

Should:

• add _sync_id: Long? property holding value for Calendars._SYNC_ID to AndroidCalendar
• add _sync_id: Long? property to JtxCollection and at.techbee.jtx.JtxContract – depends on [Feature] Add _sync_id column to collection TechbeeAT/jtxBoard#1635

[patrickunterwegs]

Hi @rfc2822 , hi @sunkup ,
I have added the column to jtx Board in a feature branch which is currently in an open pull request:
TechbeeAT/jtxBoard#1638

I have created a new pull request here for the update of the contract.
As I wasn't sure at what place you imagined to put the value in jtx Board, I have stopped there and would rather leave this up to you.

I assume that the minVersion of jtxBoard also needs to be updated in DAVx5 once this is done. Please use the following version codes:
versionCode = 210000000
versionName = "2.10.00"

There is a release in the pipeline where I wouldn't add this change yet (2.9.3), if you're sure that this column is exactly what you need, then I'd merge it right after the release. Are you sure about it?
As this creates an updated version dependency I'd like to release this change a couple of weeks before you do the DAVx5 release.
Please keep me updated about when you would release it in DAVx5.

[rfc2822]

As I wasn't sure at what place you imagined to put the value in jtx Board, I have stopped there and would rather leave this up to you.

I can do the code in davx5 then.

versionCode = 210000000
versionName = "2.10.00"

👍🏻 Have added it to the PR.

There is a release in the pipeline where I wouldn't add this change yet (2.9.3), if you're sure that this column is exactly what you need, then I'd merge it right after the release. Are you sure about it?

Yes, sounds good!

As this creates an updated version dependency I'd like to release this change a couple of weeks before you do the DAVx5 release. Please keep me updated about when you would release it in DAVx5.

If I understand it correctly, the column would be available since the version after the next version (which is released to be soon):

1. jtxBoard, next version, without sync_id – soon
2. jtxBoard, version after next version, with sync_id
3. Then a few weeks.
4. DAVx5 release that requires sync_id

Correct?

Is there a rough plan when you want to release the version after the next version? We can do other things in DAVx5 until then.

[sunkup]

👍🏻 Have added it to the PR.

@rfc2822 Does the PR need any further changes? I have started working on https://github.com/bitfireAT/davx5/pull/627 which now only waits for this one to be merged.

[github-actions]

This PR/issue depends on:

• [Feature] Add _sync_id column to collection TechbeeAT/jtxBoard#1635