RE: Edit permission to wiki
To me too.. Thanks, Vaibhav -Original Message- From: Jayashree Ramamoorthy [mailto:jayashree.ramamoor...@citrix.com] Sent: 23 April 2015 16:03 To: dev@cloudstack.apache.org Subject: Edit permission to wiki Hi, Kindly give me edit permission to the wiki. Thanks, Jayashree
RE: [DISCUSS] merging vs. cherry-picking
+1 +1, also for the assembly of subscribers of the thought -one of those who hate cherry-picking. To voters of Cherry-pick - Merge and Cherry-pick are not even comparable when it comes to managing and fixing the issues in multiple branches. git branch --contains or git tag --contains give the right information about to which all branches/tags a particular fix is ported (unless someone deviated from default merging strategy of git). No other model would be that viable. cherry-pick should not be intended, rather should not be hacked to address this. Thanks, Vaibhav -Original Message- From: Rajani Karuturi [mailto:raj...@apache.org] Sent: 31 October 2014 12:35 To: dev@cloudstack.apache.org Subject: [DISCUSS] merging vs. cherry-picking I am one of those who hate cherry-picking. Though both have same conflicts and the same number of commits, merging has many advantages over cherry-picking. git cherry-pick creates two physically distinct commits and its very difficult to track it over time [1]. git branch --contains commit-id can give you what all branches(or releases) the commit is in. I personally feel this is very useful information to have. With merging in proper direction(tofu scale [2]) there wont be situations where a fix is in past release but doesn't exist in the current or future one. Please share your opinion on this. If everybody agrees, we can start using this from 4.5 (ie. merge from 4.5 to master for any fixes on 4.5). [1] http://www.draconianoverlord.com/2013/09/07/no-cherry-picking.html [2] page 4 @ http://www.perforce.com/sites/default/files/flow-change-wingerd.pdf ~Rajani
RE: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congratulations, Rajani!! Thanks, Vaibhav -Original Message- From: Suresh Sadhu [mailto:suresh.sa...@citrix.com] Sent: 17 October 2014 16:28 To: dev@cloudstack.apache.org Subject: RE: [ANNOUNCE] New PMC Member: Rajani Karuturi congrats rajani From: Devdeep Singh [devdeep.si...@citrix.com] Sent: Friday, October 17, 2014 4:18 PM To: dev@cloudstack.apache.org Subject: RE: [ANNOUNCE] New PMC Member: Rajani Karuturi Congrats Rajani. Regards, Devdeep -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: Friday, October 17, 2014 3:52 PM To: dev Subject: [ANNOUNCE] New PMC Member: Rajani Karuturi The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
RE: [ANNOUNCE] Saksham Srivastava as committer
Congratulations Saksham.. Thanks, Vaibhav -Original Message- From: Sanjay Tripathi [mailto:sanjay.tripa...@citrix.com] Sent: 29 May 2014 15:39 To: dev@cloudstack.apache.org Subject: RE: [ANNOUNCE] Saksham Srivastava as committer Congratulations Saksham. --Sanjay -Original Message- From: sebgoa [mailto:run...@gmail.com] Sent: Thursday, May 29, 2014 12:18 PM To: dev@cloudstack.apache.org Subject: [ANNOUNCE] Saksham Srivastava as committer The Project Management Committee (PMC) for Apache CloudStack has asked Saksham Srivastava to become a committer and we are pleased to announce that he has accepted. Being a committer allows many contributors to contribute more autonomously. For developers, it makes it easier to submit changes and eliminates the need to have contributions reviewed via the patch submission process. Whether contributions are development-related or otherwise, it is a recognition of a contributor's participation in the project and commitment to the project and the Apache Way. Please join me in congratulating Saksham, -Sebastien, on behalf of the CloudStack PMC
