If you modify the getpaid core products, you can start in a branch and when you are ready, let people know so that they can test/review your branch. Then you'll be able to merge to the trunk.
If you are creating a new payment processor, you can just go ahead and create it, with a trunk/tags/branches folder in it. Let me know if you have more questions. Lucie -- S i x F e e t U p , I n c . | http://www.sixfeetup.com Phone: +1 (317) 861-5948 x605 ANNOUNCING the first Plone Immersive Training Experience | Sept. 10-11-12, 2009 http://www.sixfeetup.com/immerse On Mon, Apr 20, 2009 at 4:33 PM, Taito Horiuchi <[email protected]> wrote: > Hello, > > Two projects are planning to use getpaid for e-commerce. > Now that I'm integrating getpaid and developing new payment processor > package for those sites, > I would like to know the practice I need to be cautious with svn codes. > > Especially core codes like Products.PloneGetPaid, etc. > > For example, right now, Products.PloneGetPaid test doesn't pass on > Plone-3.3x > and when it's fixed, can I commit to trunk or should I commit to branch? > > Taito > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~---
