> -----Original Message----- > From: Alex Huang [mailto:alex.hu...@citrix.com] > Sent: Tuesday, July 30, 2013 2:06 PM > To: dev@cloudstack.apache.org > Subject: RE: [ACS42] Release Status Update: After Code Freeze Next Steps > > > The best type of commit for keeping things clean is a cherry-pick. > > Merging into the release branch is messy to track as the RM. > > > > That should be a rule for release branches after code freeze. > > --Alex [Animesh>] Thanks for clarifying, we will follow that for 4.2
- [ACS42] Release Status Update: After Code Freeze Next ... Animesh Chaturvedi
- Re: [ACS42] Release Status Update: After Code Fre... Chip Childers
- RE: [ACS42] Release Status Update: After Code... Alex Huang
- RE: [ACS42] Release Status Update: After ... Animesh Chaturvedi
- Re: [ACS42] Release Status Update: Af... Prasanna Santhanam
- Re: [ACS42] Release Status Updat... Chip Childers
- Re: [ACS42] Release Status U... Go Chiba
- Re: [ACS42] Release Stat... Chip Childers
- RE: [ACS42] Release Stat... Animesh Chaturvedi
- Re: [ACS42] Release Stat... Go Chiba
- RE: [ACS42] Release Stat... Radhika Puthiyetath
- Re: [ACS42] Release Stat... Dave Cahill
- Re: [ACS42] Release Stat... Wido den Hollander
- Re: [ACS42] Release Stat... Jessica Tomechak