Re: Welcome to our new committers
Hi Jaques, yes, it's weird and feels a little strange. But anyway, thank you and the others for the welcome. I'm looking forward to a good collaboration. Thanks and regards, Michael Brohl ecomify GmbH www.ecomify.de Am 19.05.15 um 08:52 schrieb Jacques Le Roux: Hi, I find weird to welcome new committers before it's officially announced but since we have already a commit and a lot of comments, I think it's time to congratulates you new committer, welcome on board :) Jacques smime.p7s Description: S/MIME Cryptographic Signature
Re: How should new committers handle backporting?
Le 19/05/2015 07:22, Jacopo Cappellato a écrit : Hi Christian, On May 19, 2015, at 3:37 AM, Christian Carlow christian.car...@gmail.com wrote: Should committers download the entire ofbiz repository to help with backporting? it is easier if you keep the trunk and the release branches in different svn folders (i.e. different checkouts); for example: mkdir ofbiz cd ofbiz svn co https://svn.apache.org/repos/asf/ofbiz/trunk trunk svn co https://svn.apache.org/repos/asf/ofbiz/branches/release14.12 release14.12 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release13.07 release13.07 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release12.04 release12.04 svn co https://svn.apache.org/repos/asf/ofbiz/site/ website you will end up with the following folder layout: ofbiz/ ofbiz/trunk ofbiz/release14.12 ofbiz/release13.07 ofbiz/release12.04 ofbiz/website Then you can setup, with your favorite IDE, one project for each. Is there a standard procedure new committers should follow for backporting? Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 1) commit the fix to trunk and note down the commit id; e.g. rev 12345 2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12 3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345 4) run the tests with: ./tools/mergefromtrunk.sh/bat test 5) it is also a good idea to start the instance and test manually 6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort 6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit I was going to test my new committer privilege by applying my OFBIZ-6387.patch. Should I apply it to the release branches also? That is probably not a bug but it is a small change and could be a good chance to practice with the above process, so please do if you like. Note that in a very simple case like this which has only an impact on the UI I don't run the tests. They would not help as we have no UI tests (Selenium and alike) Jacques Regards, Jacopo
Welcome to our new committers
Hi, I find weird to welcome new committers before it's officially announced but since we have already a commit and a lot of comments, I think it's time to congratulates you new committer, welcome on board :) Jacques
Re: Welcome to our new committers
In the 8 years that I have been contributing to this project I have - as far as I can tell, but I may have overlook a few emails - never seen an announcement of new committers and new PMC Members in the user ML by the PMC, except for 1 (Sharan). Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, May 19, 2015 at 9:50 AM, Michael Brohl michael.br...@ecomify.de wrote: Hi Jaques, yes, it's weird and feels a little strange. But anyway, thank you and the others for the welcome. I'm looking forward to a good collaboration. Thanks and regards, Michael Brohl ecomify GmbH www.ecomify.de Am 19.05.15 um 08:52 schrieb Jacques Le Roux: Hi, I find weird to welcome new committers before it's officially announced but since we have already a commit and a lot of comments, I think it's time to congratulates you new committer, welcome on board :) Jacques
Re: Welcome to our new committers
On May 19, 2015, at 10:00 AM, Pierre Smits pierre.sm...@gmail.com wrote: In the 8 years that I have been contributing to this project I have - as far as I can tell, but I may have overlook a few emails - never seen an announcement of new committers and new PMC Members in the user ML In fact the dev list is more appropriate for this kind of announcements. Or even better, we should start considering to merge the two list into one for all human communications and then create a separate list for automated notifications (Jira, commits, builds etc...). Jacopo
Re: Welcome to our new committers
Le 19/05/2015 11:21, Jacopo Cappellato a écrit : On May 19, 2015, at 10:00 AM, Pierre Smits pierre.sm...@gmail.com wrote: In the 8 years that I have been contributing to this project I have - as far as I can tell, but I may have overlook a few emails - never seen an announcement of new committers and new PMC Members in the user ML In fact the dev list is more appropriate for this kind of announcements. Or even better, we should start considering to merge the two list into one for all human communications and then create a separate list for automated notifications (Jira, commits, builds etc...). Jacopo I'm not against having a separated list for automated notifications, though for now I simply filter them in my email client, et voilà. I'd not go as far as merging the 2 lists (dev + user) because this separation seems logical to me and it would be difficult to create email clients filters to separate the 2 flux. As for announcing rather on user ML I'm on the same page than Pierre, the larger the audience the better. Those announcements are sufficiently rare, they will not bloat the user ML. Jacques
Re: Welcome to our new committers
On May 19, 2015, at 11:37 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: As for announcing rather on user ML I'm on the same page than Pierre, the larger the audience the better. Those announcements are sufficiently rare, they will not bloat the user ML. user list: where users of the Apache OFBiz product can discuss about it dev list: where developers of the Apache OFBiz product can discuss about their work Based on the above, it seems more appropriate to me to announce new committers in the dev list; but it is a minor topic. Jacopo
Re: Welcome to our new committers
Thanks Jacopo for the official announcement email. Congrats to all the new committers!!! :-) -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997 http://www.hotwaxsystems.com/ On Tue, May 19, 2015 at 11:02 PM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: On May 19, 2015, at 8:52 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi, I find weird to welcome new committers before it's officially announced but since we have already a commit and a lot of comments, I think it's time to congratulates you new committer, welcome on board :) Jacques I know that at this time it is not a news but, now that the list is complete, I would like second Jacques in welcoming our new committers: Arun Patidar Christian Carlow Divesh Dutta, Julien Nicolas Michael Brohl Shi Jinghai Taher Alkhateeb welcome onboard guys! This is the first time we invite so many persons in one shot and I am aware this could be a surprise to some and a concern to others. I am aware that onboarding 8 new persons is a challenge and that extra effort will have to be spent by our senior committers to guide and help them, but I am sure that we will succeed is we work together and are nice with each other. To the senior committers and PMC members: please be kind, patient, and supportive with the new committer; we should all keep in mind that our primary goal is to build an amazing and nice community, and our secondary goal is to build a great software. To the new committers: please do your best to commit code you are sure about, and ask for advices before committing code you are not sure; and please help each other by reviewing other's work and helping to improve it; now that I read these notes I realize that they apply to all committers old and new :-) Jacopo
Re: How should new committers handle backporting?
+1, very helpful, just trying it out. Maybe https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices would be a better place, or we would add a link to one of the pages. Michael Brohl ecomify GmbH www.ecomify.de Am 19.05.15 um 15:38 schrieb Jacques Le Roux: Maybe we should add it at https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities ? Jacques Le 19/05/2015 14:19, Pranay Pandey a écrit : Thanks Jacopo, its a good OFBiz Committers Guide. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ skype: pranay.pandey cell: +91 982.603.5576 On Tue, May 19, 2015 at 10:52 AM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: Hi Christian, On May 19, 2015, at 3:37 AM, Christian Carlow christian.car...@gmail.com wrote: Should committers download the entire ofbiz repository to help with backporting? it is easier if you keep the trunk and the release branches in different svn folders (i.e. different checkouts); for example: mkdir ofbiz cd ofbiz svn co https://svn.apache.org/repos/asf/ofbiz/trunk trunk svn co https://svn.apache.org/repos/asf/ofbiz/branches/release14.12 release14.12 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release13.07 release13.07 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release12.04 release12.04 svn co https://svn.apache.org/repos/asf/ofbiz/site/ website you will end up with the following folder layout: ofbiz/ ofbiz/trunk ofbiz/release14.12 ofbiz/release13.07 ofbiz/release12.04 ofbiz/website Then you can setup, with your favorite IDE, one project for each. Is there a standard procedure new committers should follow for backporting? Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 1) commit the fix to trunk and note down the commit id; e.g. rev 12345 2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12 3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345 4) run the tests with: ./tools/mergefromtrunk.sh/bat test 5) it is also a good idea to start the instance and test manually 6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort 6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit I was going to test my new committer privilege by applying my OFBIZ-6387.patch. Should I apply it to the release branches also? That is probably not a bug but it is a small change and could be a good chance to practice with the above process, so please do if you like. Regards, Jacopo smime.p7s Description: S/MIME Cryptographic Signature
Re: How should new committers handle backporting?
+1, I didn't know about the scripts, very interesting, its a good place to have these info stored and shared. Gil On 19/05/2015 15:38, Jacques Le Roux wrote: Maybe we should add it at https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities ? Jacques Le 19/05/2015 14:19, Pranay Pandey a écrit : Thanks Jacopo, its a good OFBiz Committers Guide. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ skype: pranay.pandey cell: +91 982.603.5576 On Tue, May 19, 2015 at 10:52 AM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: Hi Christian, On May 19, 2015, at 3:37 AM, Christian Carlow christian.car...@gmail.com wrote: Should committers download the entire ofbiz repository to help with backporting? it is easier if you keep the trunk and the release branches in different svn folders (i.e. different checkouts); for example: mkdir ofbiz cd ofbiz svn co https://svn.apache.org/repos/asf/ofbiz/trunk trunk svn co https://svn.apache.org/repos/asf/ofbiz/branches/release14.12 release14.12 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release13.07 release13.07 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release12.04 release12.04 svn co https://svn.apache.org/repos/asf/ofbiz/site/ website you will end up with the following folder layout: ofbiz/ ofbiz/trunk ofbiz/release14.12 ofbiz/release13.07 ofbiz/release12.04 ofbiz/website Then you can setup, with your favorite IDE, one project for each. Is there a standard procedure new committers should follow for backporting? Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 1) commit the fix to trunk and note down the commit id; e.g. rev 12345 2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12 3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345 4) run the tests with: ./tools/mergefromtrunk.sh/bat test 5) it is also a good idea to start the instance and test manually 6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort 6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit I was going to test my new committer privilege by applying my OFBIZ-6387.patch. Should I apply it to the release branches also? That is probably not a bug but it is a small change and could be a good chance to practice with the above process, so please do if you like. Regards, Jacopo
Re: How should new committers handle backporting?
Thanks Jacopo, its a good OFBiz Committers Guide. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ skype: pranay.pandey cell: +91 982.603.5576 On Tue, May 19, 2015 at 10:52 AM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: Hi Christian, On May 19, 2015, at 3:37 AM, Christian Carlow christian.car...@gmail.com wrote: Should committers download the entire ofbiz repository to help with backporting? it is easier if you keep the trunk and the release branches in different svn folders (i.e. different checkouts); for example: mkdir ofbiz cd ofbiz svn co https://svn.apache.org/repos/asf/ofbiz/trunk trunk svn co https://svn.apache.org/repos/asf/ofbiz/branches/release14.12 release14.12 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release13.07 release13.07 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release12.04 release12.04 svn co https://svn.apache.org/repos/asf/ofbiz/site/ website you will end up with the following folder layout: ofbiz/ ofbiz/trunk ofbiz/release14.12 ofbiz/release13.07 ofbiz/release12.04 ofbiz/website Then you can setup, with your favorite IDE, one project for each. Is there a standard procedure new committers should follow for backporting? Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 1) commit the fix to trunk and note down the commit id; e.g. rev 12345 2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12 3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345 4) run the tests with: ./tools/mergefromtrunk.sh/bat test 5) it is also a good idea to start the instance and test manually 6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort 6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit I was going to test my new committer privilege by applying my OFBIZ-6387.patch. Should I apply it to the release branches also? That is probably not a bug but it is a small change and could be a good chance to practice with the above process, so please do if you like. Regards, Jacopo
Re: How should new committers handle backporting?
Maybe we should add it at https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities ? Jacques Le 19/05/2015 14:19, Pranay Pandey a écrit : Thanks Jacopo, its a good OFBiz Committers Guide. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ skype: pranay.pandey cell: +91 982.603.5576 On Tue, May 19, 2015 at 10:52 AM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: Hi Christian, On May 19, 2015, at 3:37 AM, Christian Carlow christian.car...@gmail.com wrote: Should committers download the entire ofbiz repository to help with backporting? it is easier if you keep the trunk and the release branches in different svn folders (i.e. different checkouts); for example: mkdir ofbiz cd ofbiz svn co https://svn.apache.org/repos/asf/ofbiz/trunk trunk svn co https://svn.apache.org/repos/asf/ofbiz/branches/release14.12 release14.12 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release13.07 release13.07 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release12.04 release12.04 svn co https://svn.apache.org/repos/asf/ofbiz/site/ website you will end up with the following folder layout: ofbiz/ ofbiz/trunk ofbiz/release14.12 ofbiz/release13.07 ofbiz/release12.04 ofbiz/website Then you can setup, with your favorite IDE, one project for each. Is there a standard procedure new committers should follow for backporting? Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 1) commit the fix to trunk and note down the commit id; e.g. rev 12345 2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12 3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345 4) run the tests with: ./tools/mergefromtrunk.sh/bat test 5) it is also a good idea to start the instance and test manually 6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort 6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit I was going to test my new committer privilege by applying my OFBIZ-6387.patch. Should I apply it to the release branches also? That is probably not a bug but it is a small change and could be a good chance to practice with the above process, so please do if you like. Regards, Jacopo
Re: Welcome to our new committers
Congratulations to all ! It's great to see so many new commiters in the community ! On 19/05/2015 19:32, Jacopo Cappellato wrote: On May 19, 2015, at 8:52 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi, I find weird to welcome new committers before it's officially announced but since we have already a commit and a lot of comments, I think it's time to congratulates you new committer, welcome on board :) Jacques I know that at this time it is not a news but, now that the list is complete, I would like second Jacques in welcoming our new committers: Arun Patidar Christian Carlow Divesh Dutta, Julien Nicolas Michael Brohl Shi Jinghai Taher Alkhateeb welcome onboard guys! This is the first time we invite so many persons in one shot and I am aware this could be a surprise to some and a concern to others. I am aware that onboarding 8 new persons is a challenge and that extra effort will have to be spent by our senior committers to guide and help them, but I am sure that we will succeed is we work together and are nice with each other. To the senior committers and PMC members: please be kind, patient, and supportive with the new committer; we should all keep in mind that our primary goal is to build an amazing and nice community, and our secondary goal is to build a great software. To the new committers: please do your best to commit code you are sure about, and ask for advices before committing code you are not sure; and please help each other by reviewing other's work and helping to improve it; now that I read these notes I realize that they apply to all committers old and new :-) Jacopo
Re: Welcome to our new committers
As an end-user of OFBiz, we are very excited to see the team grow to help improve this already amazing product. —Paul On May 19, 2015, at 1:44 PM, Gil portenseigne gil.portensei...@nereide.fr wrote: Congratulations to all ! It's great to see so many new commiters in the community ! On 19/05/2015 19:32, Jacopo Cappellato wrote: On May 19, 2015, at 8:52 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi, I find weird to welcome new committers before it's officially announced but since we have already a commit and a lot of comments, I think it's time to congratulates you new committer, welcome on board :) Jacques I know that at this time it is not a news but, now that the list is complete, I would like second Jacques in welcoming our new committers: Arun Patidar Christian Carlow Divesh Dutta, Julien Nicolas Michael Brohl Shi Jinghai Taher Alkhateeb welcome onboard guys! This is the first time we invite so many persons in one shot and I am aware this could be a surprise to some and a concern to others. I am aware that onboarding 8 new persons is a challenge and that extra effort will have to be spent by our senior committers to guide and help them, but I am sure that we will succeed is we work together and are nice with each other. To the senior committers and PMC members: please be kind, patient, and supportive with the new committer; we should all keep in mind that our primary goal is to build an amazing and nice community, and our secondary goal is to build a great software. To the new committers: please do your best to commit code you are sure about, and ask for advices before committing code you are not sure; and please help each other by reviewing other's work and helping to improve it; now that I read these notes I realize that they apply to all committers old and new :-) Jacopo
Re: Welcome to our new committers
On May 19, 2015, at 8:52 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi, I find weird to welcome new committers before it's officially announced but since we have already a commit and a lot of comments, I think it's time to congratulates you new committer, welcome on board :) Jacques I know that at this time it is not a news but, now that the list is complete, I would like second Jacques in welcoming our new committers: Arun Patidar Christian Carlow Divesh Dutta, Julien Nicolas Michael Brohl Shi Jinghai Taher Alkhateeb welcome onboard guys! This is the first time we invite so many persons in one shot and I am aware this could be a surprise to some and a concern to others. I am aware that onboarding 8 new persons is a challenge and that extra effort will have to be spent by our senior committers to guide and help them, but I am sure that we will succeed is we work together and are nice with each other. To the senior committers and PMC members: please be kind, patient, and supportive with the new committer; we should all keep in mind that our primary goal is to build an amazing and nice community, and our secondary goal is to build a great software. To the new committers: please do your best to commit code you are sure about, and ask for advices before committing code you are not sure; and please help each other by reviewing other's work and helping to improve it; now that I read these notes I realize that they apply to all committers old and new :-) Jacopo
Re: Welcome to our new committers
Congrats and welcome aboard! Adrian Crum Sandglass Software www.sandglass-software.com On 5/19/2015 10:32 AM, Jacopo Cappellato wrote: On May 19, 2015, at 8:52 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi, I find weird to welcome new committers before it's officially announced but since we have already a commit and a lot of comments, I think it's time to congratulates you new committer, welcome on board :) Jacques I know that at this time it is not a news but, now that the list is complete, I would like second Jacques in welcoming our new committers: Arun Patidar Christian Carlow Divesh Dutta, Julien Nicolas Michael Brohl Shi Jinghai Taher Alkhateeb welcome onboard guys! This is the first time we invite so many persons in one shot and I am aware this could be a surprise to some and a concern to others. I am aware that onboarding 8 new persons is a challenge and that extra effort will have to be spent by our senior committers to guide and help them, but I am sure that we will succeed is we work together and are nice with each other. To the senior committers and PMC members: please be kind, patient, and supportive with the new committer; we should all keep in mind that our primary goal is to build an amazing and nice community, and our secondary goal is to build a great software. To the new committers: please do your best to commit code you are sure about, and ask for advices before committing code you are not sure; and please help each other by reviewing other's work and helping to improve it; now that I read these notes I realize that they apply to all committers old and new :-) Jacopo
Re: Welcome to our new committers
Congratulations to all of the new committers :) -- View this message in context: http://ofbiz.135035.n4.nabble.com/Welcome-to-our-new-committers-tp4668563p4668698.html Sent from the OFBiz - User mailing list archive at Nabble.com.
