Arnaud HERITIER wrote:
>Who can do that ?
>I think it will concern only updates and new features on plugins (bugs are not
>significant because m2 plugins were totally rewriten
>from scratch).
>
>
an example of a bug is MPIDEA-39. This probably affects both.
>But actually I don't know which f
>
> Hi,
Hi,
>
> We discussed this briefly before. From looking at that, this
> seems to be the most workable solution:
> - for any new features added in m1 or m2, we add a
> description to the plugin site so that we have a comparitive checklist
+1, I'll try to do it as soon as possible in pl
Sounds reasonable to me. Somebody wants to come up with a template for
the plugin feature list?
Concerning all the great work we've done recently (:)), it shouldn't be
too hard to extract the information from the entries in changes.xml.
Maybe this could be implemented as part of the changes
Hi,
We discussed this briefly before. From looking at that, this seems to be
the most workable solution:
- for any new features added in m1 or m2, we add a description to the
plugin site so that we have a comparitive checklist
- for any bugs fixed in m1 that potentially impact m2, when fixed, clon
