Hi Michael, Thank you for the supportive reply. I must admit it was disheartening to see 6 small patches go for over a week without any comments from anyone. It's also been a little embarrassing telling colleagues looking at my application code that to run it they not only need to pull a fresh subversion tree but they also need to manually patch it as well.
I can understand longer delays between feature based releases, but it would be great if there was at least a way to streamline getting corrective fixes into subversion. Thanks, Steve On Mar 26, 8:09 am, Michael Sparks <spark...@gmail.com> wrote: > Hi Steve, > > I'm reviewing these and I'm also considering how to make it easier for any > future code contribution (from yourself or others). The key issue I have at > the moment is some of our processes were set up when we all had more time, > and now we have far less, which means some things will need changing. > > In the meantime though, very many thanks for these patches, I'll post > feedback ASAP :-) > > My plan btw will be to make a branch in svn for these patches (maybe one > per patch), apply the patches and then assuming they're in good shape > merge onto trunk. > > Incidentally I really appreciate the short descriptions/format of this mail, > it's really useful: :-) > > Regards, > > Michael > --http://yeoldeclue.com/bloghttp://twitter.com/kamaelianhttp://www.kamaelia.org/Home --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "kamaelia" group. To post to this group, send email to kamaelia@googlegroups.com To unsubscribe from this group, send email to kamaelia+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/kamaelia?hl=en -~----------~----~----~----~------~----~------~--~---
