Where is the Issue tracker moving to?

[barryhunter]

Google Code - that hosts the issue Tracker

https://code.google.com/p/gmaps-api-issues/

is going 'Read Only' by the end of the month. 

Where is this being migrated to instead? 

[ralfwessels]

Hi Barry,

"Google Code's data will remain online for a long time"

Thats what this information site says: https://code.google.com/p/support/wiki/ReadOnlyTransition

... and more:

If you have any questions, please contact google-cod...@google.com.

Ralf

[Andrew Leach]

[Email response has not appeared yet. I suppose it might turn up at some point.]

I think Barry's point is that there needs to be an issue tracker, and it needs to be kept updated.

 

If the existing issue tracker is going read-only, then it's no longer fit for purpose in keeping track of issues, and there needs to be a replacement.

 

It's not for the Google Code team to provide that replacement, if they are responsible for the decision to make it read-only; if they were responsible, they wouldn't change anything and would just keep it going!

 

It's for the Google Maps team to provide an issue tracker, and this is the forum to ask about that.

[Mark McDonald]

Hi folks,

I can confirm that this particular tracker will remain read / write for now (beyond the advertised date), just until we find a new home.

I'll reply here when we have more news to share.

Thanks
Mark McDonald (on behalf of the Maps API team)

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-maps-js-a...@googlegroups.com.
To post to this group, send email to google-map...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-maps-js-api-v3.
For more options, visit https://groups.google.com/d/optout.

[Alan Smith]

So why release the incorrect notices in the first place?

[Andrew Leach]

I think Barry's point is that there needs to be an issue tracker, and it needs to be kept updated.

 

If the existing issue tracker is going read-only, then it's no longer fit for purpose in keeping track of issues, and there needs to be a replacement.

 

It's not for the Google Code team to provide that replacement, if they are responsible for the decision to make it read-only; if they were responsible, they wouldn't change anything and would just keep it going!

 

It's for the Google Maps team to provide an issue tracker, and this is the forum to ask about that.

 

Andrew

[Mark McDonald]

The notice applies generally to projects hosted on code.google.com and is correct in that sense. We have a special exemption for this project.

Apologies for the confusion.

[Barry Hunter]

I can confirm that this particular tracker will remain read / write for now (beyond the advertised date), just until we find a new home.

Thank you, thats good to know!