Re: [ACS41] 4.1 branch moving to limited updates only after today
On Thu, Feb 28, 2013 at 10:56:05PM +0530, Chip Childers wrote: Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip +1 - Sorry I just saw this and made a fix without the aforementioned patch request. So I'll take it that this applies from Mar 1st 2013, in one's respective timezone. -- Prasanna.,
RE: [ACS41] 4.1 branch moving to limited updates only after today
Hi Chip, If there are doc defects to be fixed (we have the doc sprint going on, now!), do we need to merge them only to Master ? Or could we submit them as patches on the Review Board ? What is the best approach ? Thanks -Radhika -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Thursday, February 28, 2013 10:56 PM To: cloudstack-dev@incubator.apache.org Subject: [ACS41] 4.1 branch moving to limited updates only after today Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip
RE: [ACS41] 4.1 branch moving to limited updates only after today
Hey Chip, Perfectly alright with me. Packaging is now more or less stable on the centos rpm side, so I can continue work on master and supply patches for 4.1 Cheers, Hugo -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Thursday, February 28, 2013 10:56 PM To: cloudstack-dev@incubator.apache.org Subject: [ACS41] 4.1 branch moving to limited updates only after today Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip
Re: [ACS41] 4.1 branch moving to limited updates only after today
As long as the changes are limited to *just docs*, I don't have a concern with directly pushing then to the branch. On Mar 1, 2013, at 4:09 AM, Radhika Puthiyetath radhika.puthiyet...@citrix.com wrote: Hi Chip, If there are doc defects to be fixed (we have the doc sprint going on, now!), do we need to merge them only to Master ? Or could we submit them as patches on the Review Board ? What is the best approach ? Thanks -Radhika -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Thursday, February 28, 2013 10:56 PM To: cloudstack-dev@incubator.apache.org Subject: [ACS41] 4.1 branch moving to limited updates only after today Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip
RE: [ACS41] 4.1 branch moving to limited updates only after today
Chip, Can anyone from IST or Europe time zone be given rights to approve patch / check in. We have sizable QA Team in IST Time zone. Builds are breaking quite frequently and blockers need to be resolved within hours like last night. Thanks /sudha -Original Message- From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of Prasanna Santhanam Sent: Friday, March 01, 2013 1:01 AM To: cloudstack-dev@incubator.apache.org Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Thu, Feb 28, 2013 at 10:56:05PM +0530, Chip Childers wrote: Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip +1 - Sorry I just saw this and made a fix without the aforementioned patch request. So I'll take it that this applies from Mar 1st 2013, in one's respective timezone. -- Prasanna.,
Re: [ACS41] 4.1 branch moving to limited updates only after today
On Mar 1, 2013, at 9:14 AM, Sudha Ponnaganti sudha.ponnaga...@citrix.com wrote: Chip, Can anyone from IST or Europe time zone be given rights to approve patch / check in. We have sizable QA Team in IST Time zone. Builds are breaking quite frequently and blockers need to be resolved within hours like last night. I was just thinking about the exact same thing! Any volunteer to be the 4.1 committer for my sleep hours? Thanks /sudha -Original Message- From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of Prasanna Santhanam Sent: Friday, March 01, 2013 1:01 AM To: cloudstack-dev@incubator.apache.org Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Thu, Feb 28, 2013 at 10:56:05PM +0530, Chip Childers wrote: Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip +1 - Sorry I just saw this and made a fix without the aforementioned patch request. So I'll take it that this applies from Mar 1st 2013, in one's respective timezone. -- Prasanna.,
RE: [ACS41] 4.1 branch moving to limited updates only after today
Just had a chat with Chip over this on the IRC . I can volunteer to apply the patches over this weekend in case there are any , provided they are fully tested and reviewed by someone , since the patches might not be form my area of expertise. And I'll let Abhi take over this on the weekdays (assuming he's not available on the weekends ) to facilitate the committing of the patches to 4.1 - Just my thoughts ! Regards, Pranav -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Friday, March 01, 2013 7:55 PM To: cloudstack-dev@incubator.apache.org Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Mar 1, 2013, at 9:14 AM, Sudha Ponnaganti sudha.ponnaga...@citrix.com wrote: Chip, Can anyone from IST or Europe time zone be given rights to approve patch / check in. We have sizable QA Team in IST Time zone. Builds are breaking quite frequently and blockers need to be resolved within hours like last night. I was just thinking about the exact same thing! Any volunteer to be the 4.1 committer for my sleep hours? Thanks /sudha -Original Message- From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of Prasanna Santhanam Sent: Friday, March 01, 2013 1:01 AM To: cloudstack-dev@incubator.apache.org Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Thu, Feb 28, 2013 at 10:56:05PM +0530, Chip Childers wrote: Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip +1 - Sorry I just saw this and made a fix without the aforementioned patch request. So I'll take it that this applies from Mar 1st 2013, in one's respective timezone. -- Prasanna.,
Re: [ACS41] 4.1 branch moving to limited updates only after today
On Fri, Mar 01, 2013 at 08:58:04PM +0530, Pranav Saxena wrote: Just had a chat with Chip over this on the IRC . I can volunteer to apply the patches over this weekend in case there are any , provided they are fully tested and reviewed by someone , since the patches might not be form my area of expertise. And I'll let Abhi take over this on the weekdays (assuming he's not available on the weekends ) to facilitate the committing of the patches to 4.1 - Just my thoughts ! Regards, Pranav Fantastic... so we'll limit code commits for the 4.1 branch to only coming from Abhi, Pranav and myself... with some great timezone and date coverage for the job! -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Friday, March 01, 2013 7:55 PM To: cloudstack-dev@incubator.apache.org Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Mar 1, 2013, at 9:14 AM, Sudha Ponnaganti sudha.ponnaga...@citrix.com wrote: Chip, Can anyone from IST or Europe time zone be given rights to approve patch / check in. We have sizable QA Team in IST Time zone. Builds are breaking quite frequently and blockers need to be resolved within hours like last night. I was just thinking about the exact same thing! Any volunteer to be the 4.1 committer for my sleep hours? Thanks /sudha -Original Message- From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of Prasanna Santhanam Sent: Friday, March 01, 2013 1:01 AM To: cloudstack-dev@incubator.apache.org Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Thu, Feb 28, 2013 at 10:56:05PM +0530, Chip Childers wrote: Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip +1 - Sorry I just saw this and made a fix without the aforementioned patch request. So I'll take it that this applies from Mar 1st 2013, in one's respective timezone. -- Prasanna.,
RE: [ACS41] 4.1 branch moving to limited updates only after today
Hi, No special treatment is expecting for Documentation: I am going to submit the Doc changes for 4.1 as patches on the Review Board. Please review them at the earliest , if you are one of the reviewer. Also, do respond to the queries posted on respective JIRA items corresponding to the features/ defects/enhancements. One set of such questions are posted at https://issues.apache.org/jira/browse/CLOUDSTACK-645. Thanks -Radhika -Original Message- From: Pranav Saxena [mailto:pranav.sax...@citrix.com] Sent: Friday, March 01, 2013 8:58 PM To: cloudstack-dev@incubator.apache.org Cc: Abhinandan Prateek Subject: RE: [ACS41] 4.1 branch moving to limited updates only after today Just had a chat with Chip over this on the IRC . I can volunteer to apply the patches over this weekend in case there are any , provided they are fully tested and reviewed by someone , since the patches might not be form my area of expertise. And I'll let Abhi take over this on the weekdays (assuming he's not available on the weekends ) to facilitate the committing of the patches to 4.1 - Just my thoughts ! Regards, Pranav -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Friday, March 01, 2013 7:55 PM To: cloudstack-dev@incubator.apache.org Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Mar 1, 2013, at 9:14 AM, Sudha Ponnaganti sudha.ponnaga...@citrix.com wrote: Chip, Can anyone from IST or Europe time zone be given rights to approve patch / check in. We have sizable QA Team in IST Time zone. Builds are breaking quite frequently and blockers need to be resolved within hours like last night. I was just thinking about the exact same thing! Any volunteer to be the 4.1 committer for my sleep hours? Thanks /sudha -Original Message- From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of Prasanna Santhanam Sent: Friday, March 01, 2013 1:01 AM To: cloudstack-dev@incubator.apache.org Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Thu, Feb 28, 2013 at 10:56:05PM +0530, Chip Childers wrote: Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip +1 - Sorry I just saw this and made a fix without the aforementioned patch request. So I'll take it that this applies from Mar 1st 2013, in one's respective timezone. -- Prasanna.,
RE: [ACS41] 4.1 branch moving to limited updates only after today
Thanks Chip, but I do have questions. If somebody can answer them, I can make necessary changes and push them a.s.a.p. Else, I will post them on Review Board. -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Friday, March 01, 2013 9:12 PM To: cloudstack-dev@incubator.apache.org Cc: Jessica Tomechak Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Fri, Mar 01, 2013 at 09:08:46PM +0530, Radhika Puthiyetath wrote: Hi, No special treatment is expecting for Documentation: I am going to submit the Doc changes for 4.1 as patches on the Review Board. Please review them at the earliest , if you are one of the reviewer. I think that today's doc sprint deserves the right to push changes as they are made... so let's keep committing docs directly to 4.1 to catch that part of the release up. Joe's been busy with that this morning already!
Re: [ACS41] 4.1 branch moving to limited updates only after today
On Thu, Feb 28, 2013, at 11:26 AM, Chip Childers wrote: I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). *snip* So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? In general I'm +1 to this, but can we get an explicit exception for docs? We shouldn't cause any breakage by continuing to commit patches to docs, and it's already a known issue that we will still be working on finalizing them... Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/
Re: [ACS41] 4.1 branch moving to limited updates only after today
On Fri, Mar 1, 2013, at 07:12 AM, Chip Childers wrote: As long as the changes are limited to *just docs*, I don't have a concern with directly pushing then to the branch. Thanks. (Just saw this, apologies for the additional noise with my prior note...) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/
Re: [ACS41] 4.1 branch moving to limited updates only after today
On Fri, Mar 01, 2013 at 09:19:58PM +0530, Radhika Puthiyetath wrote: Thanks Chip, but I do have questions. If somebody can answer them, I can make necessary changes and push them a.s.a.p. Else, I will post them on Review Board. That's a great approach... and even if you get the answer you need via another mechanism, you can always discard the reviewboard posting and commit. -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Friday, March 01, 2013 9:12 PM To: cloudstack-dev@incubator.apache.org Cc: Jessica Tomechak Subject: Re: [ACS41] 4.1 branch moving to limited updates only after today On Fri, Mar 01, 2013 at 09:08:46PM +0530, Radhika Puthiyetath wrote: Hi, No special treatment is expecting for Documentation: I am going to submit the Doc changes for 4.1 as patches on the Review Board. Please review them at the earliest , if you are one of the reviewer. I think that today's doc sprint deserves the right to push changes as they are made... so let's keep committing docs directly to 4.1 to catch that part of the release up. Joe's been busy with that this morning already!
Re: [ACS41] 4.1 branch moving to limited updates only after today
On Fri, Mar 01, 2013 at 09:52:43AM -0600, Joe Brockmeier wrote: On Thu, Feb 28, 2013, at 11:26 AM, Chip Childers wrote: I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). *snip* So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? In general I'm +1 to this, but can we get an explicit exception for docs? We shouldn't cause any breakage by continuing to commit patches to docs, and it's already a known issue that we will still be working on finalizing them... Already discussed earlier in this thread. Go for it (or, more accurately, keep doing what you've been doing this morning). Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/
Re: [ACS41] 4.1 branch moving to limited updates only after today
On Mar 1, 2013, at 10:41 AM, Chip Childers chip.child...@sungard.com wrote: On Fri, Mar 01, 2013 at 09:08:46PM +0530, Radhika Puthiyetath wrote: Hi, No special treatment is expecting for Documentation: I am going to submit the Doc changes for 4.1 as patches on the Review Board. Please review them at the earliest , if you are one of the reviewer. I think that today's doc sprint deserves the right to push changes as they are made... so let's keep committing docs directly to 4.1 to catch that part of the release up. Can folks make sure to also apply to master docs, otherwise they will get out of sync. -sebastien Joe's been busy with that this morning already!
RE: [ACS41] 4.1 branch moving to limited updates only after today
+1 . I can definitely help to verify if the patch meant for 4.1 applies cleanly . Thanks, Pranav -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Thursday, February 28, 2013 10:56 PM To: cloudstack-dev@incubator.apache.org Subject: [ACS41] 4.1 branch moving to limited updates only after today Everyone should know this by now, but our schedule has us shifting to a model where we limit the commits going into the 4.1 branch to a very few. Now we have some serious bugs still outstanding, which is challenging to say the least. That being said, I'd suggest that we don't change the plan. Stabilizing the 4.1 branch should be our focus, and that means that we have to be very selective about what commits go into it moving forward. I'll ask that, as of the end of the day today, anyone with a commit that they want cherry-picked into 4.1 (or a patch, if conflicts are expected) please send an email to the list with the following tags: [ACS41][Patch Request] - Followed by a reasonable description (or the bug ID). I'll be watching the list and applying them as soon as I can. However - I'd suggest a couple of things: First, you need to *test* the fix. I'd actually ask that we take this a bit further than unit testing the fix. If there's a bug reporter, give them the patch and have them build from 4.1 with the patch applied... before asking to move it into the branch officially. This does effect the process that the Citrix QA team is used to following, but I think it's the best option for us as a community. Second, I need help ensuring that the commit to cherry-pick applies cleanly to the 4.1 branch. If you do the first thing, this should be easy... but I'll highlight this anyway. If it's going to have conflicts, then you should be providing a patch that already deals with the conflicts. Patches like this should be in the email itself, or in reviewboard. So this is what I'd *like* to see - starting tomorrow. Objections? Comments? Concerns? -chip
