{"action":"created","issue":{"url":"https://api.github.com/repos/cgeo/cgeo/issues/6956","repository_url":"https://api.github.com/repos/cgeo/cgeo","labels_url":"https://api.github.com/repos/cgeo/cgeo/issues/6956/labels{/name}","comments_url":"https://api.github.com/repos/cgeo/cgeo/issues/6956/comments","events_url":"https://api.github.com/repos/cgeo/cgeo/issues/6956/events","html_url":"https://github.com/cgeo/cgeo/issues/6956","id":304432747,"number":6956,"title":"Next feature release","user":{"login":"Lineflyer","id":949669,"avatar_url":"https://avatars0.githubusercontent.com/u/949669?v=4","gravatar_id":"","url":"https://api.github.com/users/Lineflyer","html_url":"https://github.com/Lineflyer","followers_url":"https://api.github.com/users/Lineflyer/followers","following_url":"https://api.github.com/users/Lineflyer/following{/other_user}","gists_url":"https://api.github.com/users/Lineflyer/gists{/gist_id}","starred_url":"https://api.github.com/users/Lineflyer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Lineflyer/subscriptions","organizations_url":"https://api.github.com/users/Lineflyer/orgs","repos_url":"https://api.github.com/users/Lineflyer/repos","events_url":"https://api.github.com/users/Lineflyer/events{/privacy}","received_events_url":"https://api.github.com/users/Lineflyer/received_events","type":"User","site_admin":false},"labels":[{"id":154240,"url":"https://api.github.com/repos/cgeo/cgeo/labels/Feedback%20required","name":"Feedback required","color":"FAB028","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":22,"created_at":"2018-03-12T15:58:18Z","updated_at":"2018-05-18T10:56:01Z","closed_at":null,"author_association":"MEMBER","body":"Here we are once again. Lets chat about the next possible feature release and the ToDo before we can release.\r\n\r\nThe main change in our `master` branch is the promotion of the new mapsforge implementation. This also means, that the known bugs should get some attention and we should try to classify them (i.e. which bug is not OK for going live).\r\nI took a look at the list of bugs labeled with \"New Map\": https://github.com/cgeo/cgeo/issues?q=is%3Aopen+sort%3Aupdated-desc+label%3A%22New+Map%22+label%3ABug\r\n\r\nThere are 10 issues currently on that list, where my personal impression is, that the following should be solved or at least taken a closer look before release:\r\n- [ ] #5902 <-- Regression of info shown on the map, for me this is a must solve issue\r\n- [ ] #5900 <-- Regression regarding waypoints on map\r\n- [x] #6395 <-- Regression regarding waypoints on map\r\n- [x] #6984 <-- Map zooming out on rotation\r\n\r\nThe other listed bugs are IMHO not nice, but also not critical and could be solved at a later point of time. Still if something else on the list is also being solved, it wont harm.\r\n\r\nBesides that, we also have one regression in terms of features not yet implemented on the new map but exisiting in the old map: #5885 (1/4 mile circles around caches). I would however consider this as a minor regression which can be fixed later.\r\n\r\n@rsudev \r\nDid I miss something important when it comes to bugs or unimplemented features of the old map implementation?\r\n\r\n\r\n\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/cgeo/cgeo/issues/comments/390171776","html_url":"https://github.com/cgeo/cgeo/issues/6956#issuecomment-390171776","issue_url":"https://api.github.com/repos/cgeo/cgeo/issues/6956","id":390171776,"user":{"login":"Matze2","id":12542802,"avatar_url":"https://avatars0.githubusercontent.com/u/12542802?v=4","gravatar_id":"","url":"https://api.github.com/users/Matze2","html_url":"https://github.com/Matze2","followers_url":"https://api.github.com/users/Matze2/followers","following_url":"https://api.github.com/users/Matze2/following{/other_user}","gists_url":"https://api.github.com/users/Matze2/gists{/gist_id}","starred_url":"https://api.github.com/users/Matze2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Matze2/subscriptions","organizations_url":"https://api.github.com/users/Matze2/orgs","repos_url":"https://api.github.com/users/Matze2/repos","events_url":"https://api.github.com/users/Matze2/events{/privacy}","received_events_url":"https://api.github.com/users/Matze2/received_events","type":"User","site_admin":false},"created_at":"2018-05-18T10:56:01Z","updated_at":"2018-05-18T10:56:01Z","author_association":"CONTRIBUTOR","body":"I don't want to interrupt your crowdin discussions. I just want to give short input about the maturity of the new maps feature.\r\n\r\nAt the beginning I was very skeptical about the new Map but now I start to like it.\r\nNot only it allows to use appealing offline maps like Freizeitkarte it contains also another \"feature\" for base members which might be just there by accident.\r\n\r\nIt now shows \"more often\" PMO caches on the live map. Base members which also have access to PMO coordinates can now find candidates much easier where it is worth to \"organize\" the coordinates.\r\n\r\nI was always interested in this feature since the rough position is known in the nearby list - so why not make it available.\r\n\r\nThank you all for the big effort to make the new Maps really working! 👍 \r\n"}}
{"actor":{"display_login":"Matze2"}}