release

[frisi]

after merging (or closing) pr #1 , could you please make a release to the quaive egg servers?

i'll use the 2.x branch on my project directly so we can test if it works out well.

after a testing period we can then switch to the internal release in ploneintranet buildouts

[frisi]

used the group branch (see PR#3) since yesterday, and all syncs have run fine since then.
if there is nothing you want to add/fix in LdapUserFolder for now, i guess we are ready for a release on the quaive pypi servers with a version number that won't conflict with pypi (or should we consider to release to pypi as our fixes are relevant for other PlonePAS+LDAP users too?

[pilz]

Ok, sounds good. I would prefer a release to pypi.quaive because we can't know that we don't break things for others yet.

[frisi]

i see the point. however lots of people seem to use plone+pas+ldap and u guess most of them are maintaining their own version of ldapuserfolder as there seems to be no official repository for it.

we potentially get help/feedback of others if we put it into github.com/plone or github.com/zopefoundation. also jens vagelpohl is still around in the zope community and helping on zope4 iirc.

[pilz]

That's different. I don't have a problem with moving the repo on github to a different place like plone or zopefoundation. But at this point I would definitely not release it to pypi.python.org because it would suggest that this is a new supported version, which it is not. That is what you meant initially in the second comment, right?

[frisi]

yes - you are correct @pilz
internal release in quaive pypi is fine.
before starting the overhaul, we should consider to move the package into a public repo and announce our plans with it on the mailing list go get others chime in.