RE: Planning for Git

2012-11-26 Thread Gordon Smith
ex-dev@incubator.apache.org Subject: Planning for Git Since we can't indefinitely postpone the inevitable, I think we should start to plan for the move to Git. I think at least these points should be addressed (if they haven't already been, in which case they should be documented such that th

Re: Planning for Git

2012-11-26 Thread Carol Frampton
On 11/22/12 10 :46AM, "Erik de Bruin" wrote: >Since we can't indefinitely postpone the inevitable, I think we should >start to plan for the move to Git. I think at least these points >should be addressed (if they haven't already been, in which case they >should be documented such that they can

AW: Planning for Git

2012-11-22 Thread christofer.d...@c-ware.de
-Ursprüngliche Nachricht- Von: Erik de Bruin [mailto:e...@ixsoftware.nl] Gesendet: Donnerstag, 22. November 2012 19:26 An: flex-dev@incubator.apache.org Betreff: Re: Planning for Git >> 2) several committers are "on loan" from Adobe for a very specific >> goal (Peter and Gordon)

Re: Planning for Git

2012-11-22 Thread Alex Harui
On 11/22/12 10:26 AM, "Erik de Bruin" wrote: >>> 2) several committers are "on loan" from Adobe for a very specific >>> goal (Peter and Gordon). Are they comfortable working with Git, >>> willing and able (in that they have enough time available to do so) to >>> learn Git, or would moving to G

Re: Planning for Git

2012-11-22 Thread Omar Gonzalez
On Thursday, November 22, 2012, Erik de Bruin wrote: > > So, any questions that you might have regarding Git, GitHub, Git clients > > and workflows I would be happy to help you get through. I will do my best > > to either explain it to the best of my ability or direct you to some > > resources tha

Re: Planning for Git

2012-11-22 Thread Erik de Bruin
> So, any questions that you might have regarding Git, GitHub, Git clients > and workflows I would be happy to help you get through. I will do my best > to either explain it to the best of my ability or direct you to some > resources that will hopefully help you better understand Git. Thank you! I

Re: Planning for Git

2012-11-22 Thread Omar Gonzalez
On Thu, Nov 22, 2012 at 10:26 AM, Erik de Bruin wrote: > >> 2) several committers are "on loan" from Adobe for a very specific > >> goal (Peter and Gordon). Are they comfortable working with Git, > >> willing and able (in that they have enough time available to do so) to > >> learn Git, or would

Re: Planning for Git

2012-11-22 Thread Omar Gonzalez
On Thursday, November 22, 2012, Erik de Bruin wrote: > > just as long as the CI Server supports that particular Repo type. I > don't quite get what the "buildbot hooks" are needed for. > > The buildbot takes the content files and the templates for the website > and automatically applies one to the

Re: Planning for Git

2012-11-22 Thread Erik de Bruin
>> 2) several committers are "on loan" from Adobe for a very specific >> goal (Peter and Gordon). Are they comfortable working with Git, >> willing and able (in that they have enough time available to do so) to >> learn Git, or would moving to Git mean that they are no longer able to >> contribute?

Re: Planning for Git

2012-11-22 Thread Erik de Bruin
> just as long as the CI Server supports that particular Repo type. I don't > quite get what the "buildbot hooks" are needed for. The buildbot takes the content files and the templates for the website and automatically applies one to the other, uploading the resulting files to the staging site. T

AW: Planning for Git

2012-11-22 Thread christofer.d...@c-ware.de
...@gmail.com] Gesendet: Donnerstag, 22. November 2012 18:20 An: flex-dev@incubator.apache.org Betreff: Re: Planning for Git On Thu, Nov 22, 2012 at 7:46 AM, Erik de Bruin wrote: > Since we can't indefinitely postpone the inevitable, I think we should > start to plan for the move to Git. I

Re: Planning for Git

2012-11-22 Thread Omar Gonzalez
On Thu, Nov 22, 2012 at 7:46 AM, Erik de Bruin wrote: > Since we can't indefinitely postpone the inevitable, I think we should > start to plan for the move to Git. I think at least these points > should be addressed (if they haven't already been, in which case they > should be documented such tha

Re: Planning for Git

2012-11-22 Thread Carlos Rovira
Hi Erik 2012/11/22 Erik de Bruin > Since we can't indefinitely postpone the inevitable, I think we should > start to plan for the move to Git. I think at least these points > should be addressed (if they haven't already been, in which case they > should be documented such that they can be easily

Planning for Git

2012-11-22 Thread Erik de Bruin
Since we can't indefinitely postpone the inevitable, I think we should start to plan for the move to Git. I think at least these points should be addressed (if they haven't already been, in which case they should be documented such that they can be easily referenced, e.g. on the Wiki): 1) once Git