Re: [Repoze-dev] repoze.who status

2011-02-02 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2011 11:48 AM, Carsten Senger wrote: > --On Mittwoch, Februar 02, 2011 11:31:04 -0500 Tres Seaver > wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 02/02/2011 09:33 AM, Wolfgang Schnerring wrote: >> >>> I see that ther

Re: [Repoze-dev] repoze.who status

2011-02-02 Thread Wolfgang Schnerring
* Tres Seaver [2011-02-02 17:31]: >> which version is recommended for general consumption, what the plans for >> finalizing 2.x are (and whether there's something the general public can >> do to help). > > The reason we aren't in beta yet is that we may still discover a missing > feature while imp

Re: [Repoze-dev] repoze.who status

2011-02-02 Thread Carsten Senger
--On Mittwoch, Februar 02, 2011 11:31:04 -0500 Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2011 09:33 AM, Wolfgang Schnerring wrote: I see that there's a 1.x and 2.x line of repoze.who (2.x being in alpha), but I can't seem to figure out what the main differene

Re: [Repoze-dev] repoze.who status

2011-02-02 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2011 09:33 AM, Wolfgang Schnerring wrote: > I see that there's a 1.x and 2.x line of repoze.who (2.x being in > alpha), but I can't seem to figure out what the main differenences are, The major effort for 2.0 was to factor out the plugin set

[Repoze-dev] repoze.who status

2011-02-02 Thread Wolfgang Schnerring
Hello, I see that there's a 1.x and 2.x line of repoze.who (2.x being in alpha), but I can't seem to figure out what the main differenences are, which version is recommended for general consumption, what the plans for finalizing 2.x are (and whether there's something the general public can do to h