release

If you haven't tried it already, check out the latest release from GetPaid and join 600 others!

Also, please note that we will have remote sprints this month! This Friday and the following one and then 2 days (Aug 21-22). Read more or see the sprint information wiki (includes svn refactoring proposal).

A while ago, we created the release branch for GetPaid's second major release, 0.6. However, we didn't officially release it (with packaged code etc), and in the meantime, several fixes and changes came in. So, we are now releasing 2 versions.

0.6.0: This is the originally branched code. Works well and preserves "backwards" compatibility for those using customized GetPaid code.

0.6.1: This is a final release. Includes API refactoring and unicode fixes. May break your customized GetPaid code but not too much :)

Both of these work on Plone 2.5 and 3.0, and apparently on Plone 3.1 also (though we currently aren't providing a buildout for 3.1).

To check out the changelogs, see http://groups.google.com/group/getpaid-changes 

As of earlier today, we had 258 tests passing on 2 versions of Plone (2.5 and 3.0) - yippeee!

So, with much joy, we are moving the trunk to the 0.6 branch for this release.

Next we will tag a 0.6.0 release candidate.

This release got a new directory of documentation as well as a lot of work on new features for shipping, fulfillment and reporting. Have a look at the latest buildout!

Ricardo has been helping us to clean up issues and we are down to 10 listed in the tracker, with several of those actually falling into the "continuous enhancement" category, as opposed to blockers or priority items for this release.

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 :)

GetPaid's second major release, this one provides complete fulfillment and shipping functionality as well as several enhancements to the base product, such as address book, warehouse and inventory management, reports, and UPS shipping calculator integration. This version supports Plone 2.5 and Plone 3.0. Hopefully it will also get the Discount product included as well.

Where are we today?

Lots of changes have been going on (see the older blog posts for a summary) and great new features, especially around fulfillment and shipping.  Basically, to the solid framework established in the Red Ochre release (0.3), we have built out fulfillment functionality quite extensively.

Ohloh reports us as having over 10,000 lines of code now!

What next?

Next week, probably, we will make our release branch of the code. There will be some complexity around making tarballs that work, so expect them a while later.

We still have several issues that are targeted at this release.

We also need a catchy code name for this release :)

One thing to note...this will be our last release supporting Plone 2.5, unless someone new steps up to do the maintenance on that part of the code. The future release (0.9) will probably be lots of cleaning and UI improvements, plus the new features people think up to include :)

Haven't checkout out the release candidate yet? Get it here. If you prefer buildout, start here.

A look at out code

Ohloh finally updated our code, given us a better idea where we are and how people have participated. By the numbers, we have:

• 7,627 Lines of Code (not counting the pesky white spaces) representing about 2 person years of work!

Ohloh likes to assign a value to that (and gives you a calculator to do it yourself), and claims that our product is worth about $92,000.

The ability to leverage investments in the code base to generate additional community participation is another awesome aspect of the social sourcing model. We kickstarted something that is becoming more self-organizing, self-sustaining. Read more on our report at Ohloh.

Taking a look at our top contributors (by number of checkins), our top 10 are:

• Kapil, with 205 commits!
  
• Maurits
• Eric Steele
• JPG
• Javier Mansilla
• John Lenton
• Brian Gershon
• Ricardo Alves
• Lucie Lejard
  
• Fabio Corneti

Release Code Prep

Code preparation continues and now we have a tagged release for the 0.3. Those wishing to point their buildouts to the stable tag, can now do so.

Still to do is: update the anonymous buildout, finalize the duplicate checkout protection work, update declined payment handling in authnet.

Latest Changes

Since the tag got made after some fixes went into the product, I figured I would make a quick update on the changelog:

• Dutch and French translations were updated
• Testing processor was improved to include the "LAST_FOUR" handling, as in the other processors, for better testing.
  
• Cart item handling was improved so that when a quantity becomes zero, the item is removed from the cart. Tests around this were also included.
  

At last we have reduced the issues in the tracker, given the code some polish, fixed typos and added some improvements. Red Ochre has gone a ways beyond what we originally set out to do...providing additional features like Plone 3.0 compatibility, optional anonymous checkout, 2 additional payment processors, lots of languages and i18n work, and some example implementations. Supporting all these extra features has taken extra effort to get the release polished, but also been a great way to involve a much broader community of developers and integrators.

We made it to the release candidate thanks to some dedicated effort from Maurits over this past week to squash some remaining bugs and clean up the product. Then, Lucie swooped in at the last minute to take care of the remainder of issues yesterday! Wow, great work you all!! Thanks for helping get this ready!

Update on status:

• All tests are passing!
  
• Release Candidate tarball uploaded: Download it now! (484kb)
  
• Issue tracker: main thing left to do is prepare the code base (tags etc) for the release
  
• Our Ohloh reports seem to be broken, so I can't get new updates from there (request for updating made today). 
• There are a great many things to work on going forward, which have been organized in a page of proposals here. 
• If you find any issues with the current Release Candidate, please report them in the issue tracker and share any ideas, news, etc on our mailing list.
  

Latest changes in product:

• Put back on the last checkout page a check to see if the person is anonymous, and if the person is, we don't give a link to the order
• Added a check on the order view page to allow only manager and owner of the order to see the order, refs #157
  

And that's a wrap for today!

Please use the product and let us know how it goes! If you launch a site with GetPaid, please contact us so we can advertise it on our Sites that Use GetPaid page.

Thanks so much to  all those who helped make this possible - all our developers and supporters. Special thanks to our sponsors, who have contributed so much support to helping this become a reality:

ObjectRealms | ifPeople | One/Northwest | Contextual Corporation | Trees for Life | Totsie.com

Updated at 1:30pm, at rev1124...after some Lucie-bug-fixin' magic...a new tarball has been posted after her fixes.

Overview:

• Product tarball size, 486KB (get it here)
  
• Outstanding issues for release: 4 total. All have been worked on and are being tested or completed.
  
• Documentation: 22 items. 2 tutorials, 9 FAQs, 6 Howtos, 5 error references. Find it here. 
• Release date: December 15, 2007
• Tests passing:
  
• getpaid.core: 125/125
• PloneGetPaid: 85/85
  

From the changelog at rev 1124:

• The "payable" tab is back for Plone 3! Maurits fixed this one and in the process introduced some utility to the page. Read more.
  
• Buildouts were updated to use the latest versions of Plone
  
• Lots of work has gone on trying to make the "state" field in checkout more flexible. Outside the US, this field is often not required or handled with a dropdown. Additionally the dropdown was being loaded with some js.  It seems to be working, though should be reviewed for possible ways to improve.
  
• Some translations were updated with the latest text, including French and Dutch
  
• Typos corrected, pyflakes cleanup
• Using no-hash in the msgfmt call, which saves some space (a tip from Hanno)
• Make customer and merchant notification choices TitledVocabularies.
• i18n was rebuilt. Domain for translations updated to plonegetpaid, partly fixing an issue with the translations. Chinese translation added, and files organized in proper place.
  
• Paymentech module was added! Includes some tests required by their certification. 
• A new page at the end of checkout was added in the case where payment is declined. updated the getNextURL method to go to the declined/cancelled page
  when it is needed instead of doing nothing. Removed the restriction for anonymous users to see order.
  

We have been plugging away in Naples and now at the end of our sprint.

We got good progress today, but the list kept growing even as we got things done. We mostly focused on tests, and also got some minor improvements in the system. Today included UI, issues, translations, and functional and unit tests. More tests needed, as we didn't know how all the pieces were supposed to function (ie not tested).

Would be great to have people start testing and file issues if you find anything (http://code.google.com/p/getpaid/issues/list ). I suspect a RC tarball will be available late this week or early next week.

Status:

• Content catalog work nearly done. One test still failing, so Jean is branching getpaid.core to continue working on it (with Kapil).
• Functional tests from yesterday and the checkout ones made today are now failing in one place. So we had to do some
• Cart and cart portlet tweaked to show number of total items (as opposed to number of types of items, ie 2 shoes and 4 hats = 6 items vs 2).
• plonegetpaid.com updated with information about Red Ochre release
• Issue 124 is fixed, though ideally it still needs to write the error to the exception log for reference
• A German translation got committed.
• You can see the two earlier updates here: http://plonegetpaid.com/updates/archive/2007/10/
  

Things on the list not yet done:

• testing the new features manually (duplicate processing protection, mail notification fix)
• documentation on making a payment processor and development practices/conventions
• migrating more documentation from the wiki to plone.org
• document dev conventions: update and run tests before commit. capitalizations.

Thanks for your support and following the project. Thanks especially to Jean, John, Ricardo, Florino, Reed, Andreas, Davide, and Guissepe. And especially thanks to Kapil, whose engineering has been a great way to interest and involve more developers, and who has done so much of the product we have today.