Found the same. Figure it may be a bug in the update checker, or a blip in what was published. Since it's not here, I'd assume that this is the authorative repo over some third party update checker.
I'm just waiting for the multiple-DB condition to be fixed, since I sync multiple DBs with multiple accounts and would love for that process to be easier :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sourceforge has a "staging" option for file downloads, which restricts their availability to project maintainers for 3 days after being posted; maybe Danyal checked that box when he uploaded v3.0.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So far only a Tag for the upcoming v3 was set in the source repository and the GoogleAPI_v1.19 branch was merged into the master branch.
Version 3 is not yet ready.
Furthermore, not all new features I have in mind for v3 are implemented yet. One of those features I am thinking about indeed is better support for multiple databases and accounts.
It may still take some time until v3 is released since I have to find the time to implement and test those things.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh, now I see where the problem is. It seems the version checking got updated prematurely.
We'll see if we might as well release this version without any improvements besides the updated Google API and release new features with a later release... That't up to Danyal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
v3 is uploaded. Like Paul said, it's mostly under the hood changes. I like dregad idea, might look into 'staging' a new version to a specific group of people to try out and test the plugin before GA.
Please post here or ping myself or Paul if anyone likes to help with testing efforts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just got a pop-up informing me that v3.0 is available but when I attempt to download I only see links for v2.1.2. Where did they hide v3.0?
Found the same. Figure it may be a bug in the update checker, or a blip in what was published. Since it's not here, I'd assume that this is the authorative repo over some third party update checker.
I'm just waiting for the multiple-DB condition to be fixed, since I sync multiple DBs with multiple accounts and would love for that process to be easier :)
Same here!
Same here too...
Sourceforge has a "staging" option for file downloads, which restricts their availability to project maintainers for 3 days after being posted; maybe Danyal checked that box when he uploaded v3.0.
So far only a Tag for the upcoming v3 was set in the source repository and the GoogleAPI_v1.19 branch was merged into the master branch.
Version 3 is not yet ready.
Furthermore, not all new features I have in mind for v3 are implemented yet. One of those features I am thinking about indeed is better support for multiple databases and accounts.
It may still take some time until v3 is released since I have to find the time to implement and test those things.
Would be possible to avoid that v3 gets detected by Keepas?
Makes useless the update checker...
Oh, now I see where the problem is. It seems the version checking got updated prematurely.
We'll see if we might as well release this version without any improvements besides the updated Google API and release new features with a later release... That't up to Danyal
v3 is uploaded. Like Paul said, it's mostly under the hood changes. I like dregad idea, might look into 'staging' a new version to a specific group of people to try out and test the plugin before GA.
Please post here or ping myself or Paul if anyone likes to help with testing efforts.