In D6 only the dev version of the Flickr module works correctly. This is the only version in D6 that makes its API calls over SSL, see #2261371: Flickr API Going SSL-Only - Likely Impact?.

In the usage statistics per release we see that only approximately 1% of the D6 installs of the Flickr module uses the dev version, even almost half a year after Flickr pulled the plug of API calls over HTTP.

We can conclude that maintenance efforts on D6 are done for a handful of sites that still might use the module actively. We prefer to focus our efforts on making D7 ready for a D8 port. D6 maintenance will continue for critical bug fixes only.

All the D6 issues that are in 'Patch (to be ported)' status, will be set to 'Closed (won't fix)'. However, if someone submits a patch for D6, it will be reviewed promptly and committed if it gets to RTBC status.

The usage statistics for D7 tell us that new stable releases get adopted quickly, the dev version is popular and the usage in general is increasing. The D7 version is alive. It's best to put our limited resources into the Drupal version that is most actively used.

Thanks.

Comments

lolandese’s picture

lolandese CreditAttribution: lolandese commented
Issue summary: View changes
lolandese’s picture

lolandese CreditAttribution: lolandese commented
Issue summary: View changes
lolandese’s picture

lolandese CreditAttribution: lolandese commented

All the D6 issues that are in 'Patch (to be ported)' status, will be set to 'Closed (won't fix)'.

Setting most of these issues back to D7 and being 'fixed (closed)'.

Main reason is the fact that links to these issues show the status on hover without revealing the version (6 or 7). This might give the impression that the mentioned issue will not be solved, while in fact it is already fixed for the D7 version. 'Fixed (closed)' reflects the current status correctly for D7. 'Closed (won't fix)' is only valid for the minimally maintained D6 version of the module.