I do no know that either. I will rely on Yarko for guidance. It is also ok if you just upload a patch somewhere and submit a bug report about your patch.
My problem is not the process of integrating patches (actually email works fine in that respect). The problem is keeping track of what people propose and why (I get too many emails about all sort of stuff). Massimo On Nov 4, 7:26 am, "Yarko T" <[EMAIL PROTECTED]> wrote: > This assumes informally you have created a local branch on your private > machine where you do work, and keep it merged with the trunk (currently, > there is only Massimo's development branches; we will create a trunk to hold > released merges - including Massimo's work). > > When you have a new function idea, or think you've found a bug, ask Massimo > on the list. > > - If you have a new feature, register a blueprint on Launchpad and > describe what you're going to do. > - If you have found a bug, make a bug report on Launchpad. > - When you are ready to start work, create a branch (NOTE: once you > create a branch, there is no easy way to remove it). > > 1. sign up for an account on launchpad.net, > 2. go to the project and select "register branch" ( > https://code.launchpad.net/web2py/+addbranchor > https://code.launchpad.net/t2/+addbranch). Suggest you create a mirror > branch, you can work locally, and pull / push as you make progress (see > > http://doc.bazaar-vcs.org/latest/en/user-guide/index.html#organizing-...)<http://doc.bazaar-vcs.org/latest/en/user-guide/index.html#organizing-...> > 3. Once you have registered your branch launchpad will provide you with > instructions on how to pull and push to your personal development copy. > 4. Link your bug report or blueprint to your branch. > 5. Push your working copy to launchpad as your work is ready for others > to review, test; merge from your "parent" (trunk, massimo's main branch, > or > others you are working with) as needed. > 6. Once you are done making your changes in the branch, completed > testing, and are ready for the project team to inspect & test, please > select > "propose for merging" > 7. Somebody on the core team will make a test merge (it may include > merging with other patches). Once tests pass, and your branch is accepted, > it will be merged into the trunk. > > Once merged, you may repeat the process - make another branch and :-). > > On Tue, Nov 4, 2008 at 1:34 AM, billf <[EMAIL PROTECTED]> wrote: > > > Massimo > > > How does one do that? Do I register a branch and just upload the new/ > > changed files? Any particular conventions to be followed? > > > Bill > > > On Nov 4, 7:22 am, mdipierro <[EMAIL PROTECTED]> wrote: > > > From now on all patches longer than 3 lines MUST be posted to > > > launchpad otherwise I cannot keep track of them. > > > > Thanks. > > > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
