[ECODP-dev] Reporting new issues in release 01.00

Mon Oct 14 11:12:37 UTC 2013

Hi,

There have been a couple of new issues reported recently. Please can you
ensure that for any issue reported we have the basic details we need to
investigate. (I.e. Steps to recreate, which release the issue exists within
etc).

As the new contractor will need a record of any recent issues I would also
suggest that these issues shouldn't simply be reported by email. Therefore
please can you either add them to Jira or the issues list on the EC ODP
extension? That way there will be a record of current state for the new
contractor.

With regards to these small issues

- Legal notice link - I've created an issue for this
https://github.com/okfn/ckanext-ecportal/issues/19
- Search redirects to English - Couldn't recreate - Please create a ticket
with steps to recreate

Clearly it doesn't make sense to create a new release each time minor
issues are reported and it's much more efficient for us to work through a
batch of issues. Are you planning to collate all the feedback to create a
maintenance release once the PO has finished all their testing? If so what
is the timescale on this?

Thanks,

Darwin

*Darwin Peltan*

*Project Manager  |  skype: darwinp  |  twitter:
@darwin<http://twitter.com/darwin>
*

*The Open Knowledge Foundation <http://okfn.org/>*

*Empowering through Open Knowledge*

*http://okfn.org/  |  @okfn <http://twitter.com/OKFN>  |  OKF on
Facebook<https://www.facebook.com/OKFNetwork> |
Blog <http://blog.okfn.org/>  |  Newsletter<http://okfn.org/about/newsletter>
*
*
CKAN | http://ckan.org | @ckanproject <http://twitter.com/ckanproject>
|open source data management platform
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20131014/836c6b61/attachment.html>