Dinesh Premalal wrote: > I think this procedure is a good one. Because using RTC for branches > will reduce the room for errors. Furthermore it will make sure both > major releases and minor releases are in sync with respect to > improvements. While review time devs can decide whether a patch should > go into both releases (major and minor) or one.Whereas, I think we > should follow CTR for trunk development otherwise it will slowdown the > development process very much. Hope you mean it too.
Yes, I think trunk should definitely be CTR. I like the way RTC for branches works, myself, but it does mean a sometimes *slow* process of getting patches into branches and then into releases. I was just describing what I've learned from other groups and don't have a specific, fixed idea about about how Axis2/C should work with respect to maintained branches. Chris. -- GPG Key ID: 366A375B GPG Key Fingerprint: 485E 5041 17E1 E2BB C263 E4DE C8E3 FA36 366A 375B --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
