testing

Here's a quick look at progress towards the 0.6 release and an update on the release.

• We are over 620 downloads of the 0.3 release tarball! (plus buildout usage)
• A bug got fixed in the 0.3 buildout branch this past week
• Several bugs got fixed in the trunk, including restored Plone 2.5 compatibility for the buildout, report-related bugs, template changes, and more.  Also, a tool got added to extract email addresses from customer records. Check out the change logs to see more.
  
• We are down to 14 issues tagged for M2 (actually less once we verify closure...). See the issues and grab one to fix or test!
  
• The 0.6 release branch will be made later this week. If you have goodies to include or bugs to fix, please do them asap!
  

Thanks for tuning in. Grab an issue, test the tools, and let us know how it looks so we can make way for 0.6 :)

We discovered how few windows users are actually out there recently as we realized that for a long while the Plone 2.5 buildout has been broken for them because of the use of inquant.recipe.download, which itself is a wrapper around gocept.download. Basically difference between "/" and "\"...Read here for more info.

Thanks to Taun for pointing it out and thanks to the community for so quickly responding. We think we have it fixed (though we are relying on Windows users to actually test it out and see).

We also found there are some problems in the tarballs running on Windows. Most likely similar problem...but again we need help testing. So grab the latest tarball! Note: Plone 3.0 users do not need to install Five and CMFonFive from the tarball.

So...please check out the updated buildout for Plone 2.5. See here for more on getting it.

Naples Sprint

There's over a hundred people in the Naples Sprint, post Plone Conference. There are lots of topics and projects going on here. GetPaid's goal for this sprint is to get out a release candidate of the Red Ochre release.

GetPaid: Day 1

On the first day, we recruited a group of 8 to work on the project. We reviewed our task list and refined it some. Before delving into refactoring, we discovered that our product tests were in need of serious attention. Though work has gone on recently in building in tests in the getpaid.core (Zope 3 library) - in part to make to easier to upgrade to Plone 3.0 - the PloneGetPaid (Plone wrapper product) was desperately needing improvement. Some tests created during the Google sprint were completely outdated and needed removal, and large sections of the product needed tests. This quickly became a priority for considering a release. Reed also cleaned up some of the naming in the product to make it more consistent.

In this process, Jean Francois introduced a product into the buildout for making functional tests called Test Recorder. It allowed me (read "not a developer") to make functional doctests for the product! That was exciting, as I had no idea it could be so easy (ie literally just clicking through the site and adding some comments).

We also updating the Plone version to the latest release in the series (2.5.4) and updated the Five version to 1.4 to allow for browsertesting.

Davide also worked on getting us onto GenericSetup best practices. Things were removed from the install.py and cleaned up for GenericSetup.

Davide also made an example customization policy to ship with the product to demonstrate how to change settings. This complements the Zope 3 approach to customization discussed in documentation and in Martin's talk from the conference.

A small bug in the policy display was fixed.

Liam, sprinting remotely, also checked in several UPS integration files to the branch he is working on, which included tests.

On the internationalization front, Ricardo added a Portuguese (Portugal) translation, Giuseppe updated the Italian translation.

That's about it for day one! Looks better when I actually write it all down :)

Day 2

We are already under way for the day. Unit tests in PloneGetPaid are getting advanced, and the GenericSetup work is completed already!

More later...

If you have suggestions for things you would like to see, please send comments to our dev mailing list.

After a lot of design and development work at the sprint, Kapil is leading the charge to prepare the Red Ochre release!

Since the sprint, there has been a lot of refactoring. What does that mean? Well, for one, the product is getting a LOT better! But what that means that impacts you...is that we need your help testing.

The product is now available in a more traditional Plone product way - just download a tarball and stick in your Products directory, restart Zope and see how it goes! (for more on the issues with buildout see dev list message). Get the latest tarball from our Google Code downloads section (The Friday the 13th version is here).

You should be able to:

• Install it to your site
• Go to product config area and: Configure it for donations, shippable products, etc
• View order history, search them
• Note: to do this, you will probably want to generate test orders using the script included in the product.
  
• Go to content in your site and make it "buyable" or "a donation" from the actions menu
• Set the price etc
• Browse the site and when on buyable content, be able to add to cart
• Review your cart
• Checkout (fill out info for the order)
• View your order history
• Get Paid!