Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

External dev communications #2337

Closed
robocoder opened this issue Apr 19, 2011 · 3 comments
Closed

External dev communications #2337

robocoder opened this issue Apr 19, 2011 · 3 comments
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.

Comments

@robocoder
Copy link
Contributor

Devs who customize Piwik and/or write new plugins may not necessarily be following our commit log.

The piwik-hackers mailing list is low volume, and can be used to communicate a summary of:

  • compat busters
  • new APIs
  • examples, tips
  • compatibility with trunk (CI testing?)
@mattab
Copy link
Member

mattab commented Apr 23, 2011

it sounds good to use piwik-hackers for these types of announcements. I guess, next step is to agree on this, then advertise piwik-hackers as specifically for these types of announcements and related questions?

@robocoder
Copy link
Contributor Author

Have thought about this some more. I think the best approach is to have the CI server test for compatibility with the latest release and trunk, and detect/notify which plugins break,

@mattab
Copy link
Member

mattab commented Apr 28, 2011

Agreed, once we have the plugin repository..

@robocoder robocoder added this to the Community and Marketing milestone Jul 8, 2014
@mattab mattab added the wontfix label Aug 3, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Development

No branches or pull requests

2 participants