[cmsms-dev] MinimumCMSVersion

[Robert Campbell]

Yeah, there are modules that are way backwards compatible (CustomContent is so 
stupid it can't be anything but backwards compatible).  but still, it, and 
all others should require at a minimum the latest stable version of CMS

On Saturday 29 September 2007 13:55:40 Shechina wrote:
> I support this idea, although there are modules that are way, way backwards
> compatible.
>
> Anything to motivate people to upgrade is a good thing, even if it will
> annoy some of the user base.
>
> _SjG_
>
> On 9/28/07, Robert Campbell <calguy1000 at gmail.com> wrote:
> > As a matter of policy... I think that all new module versions should have
> > their MinimumCMSVersion set to the latest stable release at the time when
> > the
> > module is released.
> >
> > This prevents obvious problems, like I've encountered with the
> > RegisterModulePlugin and RestrictUnknownParams calls,  And also
> > encourages people to upgrade more rapidly.
> >
> > But also it prevents some people from trying to 'backport' modules to use
> > them
> > ol older versions of CMS.
> >
> > Of course you can never get past the inventive person that actually reads
> > the
> > code.... but if the person reads and understands the code they should
> > also understand that things aren't necessarily backwards compatible.  and
> > therefore they support themselves.
> >
> > What do you think.
> > _______________________________________________
> > cmsms-dev mailing list
> > cmsms-dev at lists.cmsmadesimple.org
> > http://lists.cmsmadesimple.org/mailman/listinfo/cmsms-dev