The project page currently states "since many crucial bugs were fixed on the transfer of maintainership".

I just looked through the bugs list (30 in total for the whole history of this module..?!), and where are the "many" that were crucial and has been fixed since the maintainership change? My quick peek did not reveal any that seems to justify that formulation, so how about go a little softer on the previous maintainer? If in fact version 1.5 is suitable for recommendation (currently green), then that formulation gives the wrong impression.

I suggest reformulating that sentence to just call for review due to new version after change in maintainership.


dpovshed’s picture

Thank you, this is very good point. I'll update the doc right after release 1.6.

dpovshed’s picture

Assigned: Unassigned » dpovshed
Issue summary: View changes
dpovshed’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.