Giters

cgeo / send2cgeo

Script for Mozilla Firefox and Google Chrome browser to send geocaches directly from your browser to c:geo on your phone.

Home Page:http://www.cgeo.org/send2cgeo.html

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

next send2cgeo release

bekuno opened this issue · comments

commented

I think we have now reached a good state to be ready for a new release.

  • Solved Issues:
    • #44 extended line height for premium caches in basic member list view
    • #66 send2cgeo on old map stops opening the cache details
    • #68 send2cgeo only works in english on the browsemap
    • #77 s2cgeo does't work on recentlyviewed and nearest list
    • #81 GCLH2 does not work while send2cgeo got new update
    • #82 Non-functional change of coordinates
    • #85 s2cg button after loging a cache
    • #93 premiumCheck() does not work
  • with PR:
    • #83 use .href.match()
    • #86 Solve Problems after switch to jQuery
    • #87 s2cgeo does't work on recentlyviewed and nearest list
    • #88 s2cg button after loging a cache
    • #91 send2cgeo only works in english on the browsemap
    • #92 Fit on the cache detail button to rest of the script.
    • #94 premiumCheck and alignment at the new search

Is something missed here?

commented

I think so too.
No, nothing missing here, but I have 2 new, little PRs:

  • #91 / #68 send2cgeo only works in english on the browsemap
  • #92 Fit on the cache detail button to rest of the script
commented

I've fix two other bugs:

  • #94 / #93 premiumCheck() does not work
  • #94 / #44 No misalignment in the new search for PM-Caches
commented

Will merge branches next weekend when back home. Internet connection is not the best here in Madagascar.

commented

Thanks @capoaira for your efforts to fix and improve. Really highly appreciated as the script was not really maintained for a longer time.

commented

Madagascar sounds cool. Have fun!

commented

Back home.
I have not tested anything myself, but I have read in my mails, that the current status of master should be good.
Do I have your OK to raise version number and release to users by merging branch to release?

commented

@Lineflyer welcome home.
Please see the check list above.
PR #92 is ok now and ready to merge. After that you can release a new release.

commented

Version has been raised to 0.49. Branch master has been merged to branch release thus 0.49 is live for users to update.