Plone Survey 1.3 alpha

[Stefan Lange]

Hi,

I was looking for a survey tool for Plone 3.x and found Plone Survey
v1.3 alpha very useful. Most of my customer's requirements are met by
the product. I would like to use it in my project - but the statement
on the product's page says "Wait for the final".
So I was looking for the svn repository in order to get a grip on the
trunk and - if the code is not to hard to understand - offer some
coding support to the project to speed up development a bit.
Unfortunately I did find a 1.3 branch: all code seems to belong to
1.22 ... please correct me if this is wrong.
What do I have to do to get access to the 1.3 code (except downloading
the .tgz from) and provide bugfixes?

Best regards,

Stefan

[Davis, Michael]

Hi Stefan,

Just use trunk. 1.3 alpha is slightly behind trunk. Trunk should work ok
in Plone 3.0, but I've not fully tested it yet.

I want to get a 1.2.3 version out, which fixes some bugs and
functioanlity issues, for Plone 2.5, but conflicting priorites has made
that slip a lot. Any help would be appreciated. 1.3 will be aimed at
Plone 3.0 exclusively.

If you have any questions, let me know.
Cheers
Michael

[Stefan]

Hi Michael,

On 1 Sep, 14:38, "Davis, Michael" <m.r.da...@cranfield.ac.uk> wrote:
> Hi Stefan,
>
> Just use trunk. 1.3 alpha is slightly behind trunk. Trunk should work ok
> in Plone 3.0, but I've not fully tested it yet.

I only work in Plone 3. If my code runs in Plone 3 does not mean it
runs in Plone 2.5 ... is this a problem? Do I have to test all changes
in a separate Plone 2.5 instance? Do you test all your changes in
Plone 3?

Another question: How to proceed if I fixed a bug/added functionality?
I suppose the repository is read-only for people like me ;) Should I
send the changes via email?

Best regards,

Stefan

[Davis, Michael]

Hi Stefan,

If you work in Plone 3, don't worry about testing in Plone 2.5, that's
my problem. I will be testing my changes within Plone 3.

It's in the Plone Collective, if you don't have a login for that, you
can send me patches, and I can check them in. Better yet, get yourself a
collective login.