Drop support for Plone 3.x

[hvelarde]

Keeping support for Plone 3.x is a burden nowadays; we must drop it.

[renfers]

A rewrite with Plone 4.3.x and Plone 5 as targets would be a good idea!
DX types only!

[schminitz]

It's a good idea to not support 3.x anymore, but I think this is not a ticket that can be fixed. We will not adapt code to remove support, we just have to not support when a bug is found :)

[hvelarde]

yes, is a ticket that can be fixed: it includes changes to the package distribution and make clear on the package documentation that we're not supporting that version anymore.

[pbauer]

I'm +1 on a rewrite for 4.3.x with p.a.contenttypes and Plone5. The package has reached a point where the amount of conditional code renders it unmaintainable. Having only one Event-type and one Collection-Type (both are actually behaviors) would make it much smaller.

[tdesvenain]

Hi Philip, i understand what you mean, but

I'm -1 on removing any compatibility on archetypes or topic

IMHO this product is used on very large projects and has to keep a long
term maintenance and backward compatibility

Thomas

2014-06-04 17:47 GMT+02:00 Philip Bauer [email protected]:

I'm +1 on a rewrite for 4.3.x with p.a.contenttypes and Plone5. The
package has reached a point where the amount of conditional code renders it
unmaintainable. Having only one Event-type and one Collection-Type (both
are actually behaviors) would make it much smaller.

Reply to this email directly or view it on GitHub
#27 (comment)
.

Thomas Desvenain

Téléphone : 09 51 37 35 18

[pbauer]

@tdesvenain
The problem is that the state of the code prevents development and even maintenance (at least I shy away from trying to get it to work with the cirretn p.a.event and collections in p.a.contenttypes).

I would much prefer creating a new product (e.g. collective.fullcalendar) that does not care about archetypes, topics and older versions of collections but takes all the good and working code from Solgema.fullcalendar, cleans it up a little and aims for compatabaility with Plone 5 (at least the popups for creating events will have to be different I guess). Migrations are no big issue since it is basically just a view that does not modify content in any significant way.

[kamon]

I am also +1 on another package that takes care of forward compat. I think we are holding oursleves back by not starting the process now, and in a few months time, the issue might be raised again.
I am willing to help with the cleanup effort, even by planning something like a remote sprint to ease coordination.