Re: Shouldn't plone.portlet.collection 2.2.x be 3.0.x

which changes are your referring? the one you recently did?
just by reading the last few changes in CHANGES.rst, i cant see very big
changes.

but in general i agree. backwards incompatible changes should make a
major release - except restoring compatibility is trivial. we should
include a statement like this in:
https://github.com/plone/plone.api/blob/master/docs/contribute/conventions.rst#versioning-scheme this document might become the official code guidelines of Plone, at least that's what we plan for Plone 5.

pull-requests 3+4 would make a good 3.0.x release:
https://github.com/plone/plone.portlet.collection/pulls

best, johannes


On Wed, 2014-03-05 at 11:01 +0000, Anthony Gerrard wrote:
> Hi,
> 
> 
> It looks like the changes made to the master branch on
> plone.portlet.collection break backwards compatibility with plone
> 4.3.x.
> 
> 
> Shouldn't the releases be called 3.0.x and not 2.2.x? Do we have a
> versioning policy written down for plone packages?
> 
> 
> 
> Anthony
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works. 
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers

-- 
programmatic  web development
di(fh) johannes raggam / thet
python plone zope development
plone framework  team  member
mail: office-//[email protected]
web:  http://programmatic.pro
      http://bluedynamics.com

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEABECAAYFAlMXM+4ACgkQW4mNMQxDgAf45QCgmKV1L3LpSoJbxKraK1Z1vRm+
gyIAnRCkbbaTboJMvGfNXPgfpACK0mX+
=D2tf
-----END PGP SIGNATURE-----