[jira] [Commented] (FLEX-33429) Bindable Metadata does not work in SubClass

[Bogdan Dinu (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602092#comment-13602092
 ] 

Bogdan Dinu commented on FLEX-33429:


Not true! You are declaring the getter of the parent to be [Bindable] : the 
correct way to declare a setter / getter as [Bindable] is to place it to the 
setter as following :
[Bindable]  
public function set value(value:String):void 
{ 
if (_value != value) 
{ 
_value = value; 
} 
}
This is not a bug.

> Bindable Metadata does not work in SubClass
> ---
>
> Key: FLEX-33429
> URL: https://issues.apache.org/jira/browse/FLEX-33429
> Project: Apache Flex
>  Issue Type: Bug
>  Components: .Unspecified - Compiler
>Affects Versions: Apache Flex 4.8 (parity release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: Japanese
>Reporter: hiroyuki kikuchi
>
> If Parent Class has defined a Bindable Metadata, it is not active in SubClass.
> It was working in Flex3.
> The following code demonstrates the problem. Bindable Metadata is not exist 
> in the Sub classes.
> Parent.as
> 
> public class Parent
> {
> private var _value:String;
> [Bindable]
> public function get value():String
> {
> return _value;
> }
> public function set value(value:String):void
> {
> if (_value != value)
> {
> _value = value;
> }
> }
> public function Parent()
> {
> super();
> }
> }
> 
> Sub.as
> 
> public class Sub extends Parent
> {
> override public function get value():String
> {
> return super.value;
> }
> public function Sub()
> {
> super();
> }
> }
> 
> Main.mxml
> 
> 
> http://ns.adobe.com/mxml/2009";
>xmlns:s="library://ns.adobe.com/flex/spark"
>xmlns:mx="library://ns.adobe.com/flex/mx"
>width="100%" height="100%">
> 
> 
> 
> 
> 
> 
> 
>  text="{describeType(parentClass).toString()}" />
>  text="{describeType(subClass).toString()}" />
> 
> 
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: FXG Extension for Photoshop CS5

[Om]

On Mar 13, 2013 8:49 PM, "Alex Harui"  wrote:
>
> I'll try to figure out who to ask, but there's a chance they pulled it
down
> because CS6 doesn't support it.
>

The effort is much appreciated!

Thanks,
Om

>
> On 3/13/13 8:42 PM, "Om"  wrote:
>
> > Yes, I am running CS6 - 64 Bit.
> >
> > Thanks,
> > Om
> >
> > On Wed, Mar 13, 2013 at 8:39 PM, Alex Harui  wrote:
> >
> >> Are you running PS CS5 or something later?
> >>
> >>
> >> On 3/13/13 8:22 PM, "Om"  wrote:
> >>
> >>> On Fri, Mar 8, 2013 at 12:59 AM, Sebastian Mohr
> >>> wrote:
> >>>
>  Hi,
> 
>  does anyone know where I can download the FXG Extension for
>  Photoshop CS5 that is mentioned here [1]? The Flash Catalyst site [2]
>  does not provide this link anymore. Could the Adobe folks on this
list
>  be able to provide a working link for that? When importing skins into
>  Apache Flex, that extension would be really helpful.
> 
>  Thank you!
> 
>  [1]
http://blogs.adobe.com/labs/archives/2010/04/adobe_flash_cat_1.html
>  [2] http://www.adobe.com/products/flashcatalyst.html
> 
> 
> >>> +1
> >>>
> >>> I wasn't able to find the Fireworks -> FXG exporter as well.  Adobe
> >> folks,
> >>> any chance the plugins can be made available?  This is a big missing
link
> >>> when it comes to skinning for Flex 4+ components.
> >>>
> >>> Thanks,
> >>> Om
> >>
> >> --
> >> Alex Harui
> >> Flex SDK Team
> >> Adobe Systems, Inc.
> >> http://blogs.adobe.com/aharui
> >>
> >>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>

Re: Git Migration Reset

[Om]

Update from David@Infra:

flex/sdk is currently read-only


[~bigosmallm]

I've started SDK migration. Because of the concerns raised about the
previous SDK migration I am working directly from SVN (as opposed to the
git mirror which is where the previous migration came from.) So /flex/sdk
is currently read only in SVN. The migration is still running and likely
will run a few more hours. I'll update the ticket as I have more
information.

-

Thanks,
Om
On Mar 13, 2013 10:40 AM, "Om"  wrote:

> In case you are not following the JIRA ticket, Infra has confirmed that
> they have opened SVN back up for read/write.  Also, they will be starting
> the move to Git this evening (GMT -5) again.
>
> *So, everyone please check-in all your changes into SVN asap.  *Sometime
> this evening, SVN will go read-only at which point the migration to Git
> will start.
>
> Here is David@Infra's note regarding this:
>
> I'll start from scratch this evening. I'll make a list of svn trees and
>> start down them one by one, though I'll likely get multiple done in a
>> single sitting. Typically it takes 20 minutes to a few dedicated hours
>> of time per svn tree > git migration.  I'll probably take asjs, external
>> and falcon tonight. Then the PMC needs to audit, and we can make it RW
>> when you are satisfied. If we find problems with a given migration, I've
>> had it take substantially longer, or be a quick fix, it depends. That
>> said, I can't give you a dedicated timeline for all of this - I am doing
>> this as a volunteer, and am travelling extensively this week, so I'll try
>> and take care of it as I have time available.
>
>
>
> And if you have any questions and suggestions do so quickly so I can
> clarify with David.  Please DO NOT post on the JIRA ticket.  I will be
> online for the 12 hours (at least)  I plan to help shepherd this process
> all the way to the end.
>
> Thanks,
> Om
>
> [1] https://issues.apache.org/jira/browse/INFRA-5549
>

[jira] [Created] (FLEX-33429) Bindable Metadata does not work in SubClass

[hiroyuki kikuchi (JIRA)]

hiroyuki kikuchi created FLEX-33429:
---

 Summary: Bindable Metadata does not work in SubClass
 Key: FLEX-33429
 URL: https://issues.apache.org/jira/browse/FLEX-33429
 Project: Apache Flex
  Issue Type: Bug
  Components: .Unspecified - Compiler
Affects Versions: Apache Flex 4.8 (parity release)
 Environment: Affected OS(s): All OS Platforms
Language Found: Japanese
Reporter: hiroyuki kikuchi


If Parent Class has defined a Bindable Metadata, it is not active in SubClass.
It was working in Flex3.

The following code demonstrates the problem. Bindable Metadata is not exist in 
the Sub classes.

Parent.as

public class Parent
{

private var _value:String;

[Bindable]
public function get value():String
{
return _value;
}

public function set value(value:String):void
{
if (_value != value)
{
_value = value;
}
}

public function Parent()
{
super();
}
}



Sub.as

public class Sub extends Parent
{

override public function get value():String
{
return super.value;
}

public function Sub()
{
super();
}
}



Main.mxml


http://ns.adobe.com/mxml/2009";
   xmlns:s="library://ns.adobe.com/flex/spark"
   xmlns:mx="library://ns.adobe.com/flex/mx"
   width="100%" height="100%">















--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: FXG Extension for Photoshop CS5

[Alex Harui]

I'll try to figure out who to ask, but there's a chance they pulled it down
because CS6 doesn't support it.


On 3/13/13 8:42 PM, "Om"  wrote:

> Yes, I am running CS6 - 64 Bit.
> 
> Thanks,
> Om
> 
> On Wed, Mar 13, 2013 at 8:39 PM, Alex Harui  wrote:
> 
>> Are you running PS CS5 or something later?
>> 
>> 
>> On 3/13/13 8:22 PM, "Om"  wrote:
>> 
>>> On Fri, Mar 8, 2013 at 12:59 AM, Sebastian Mohr
>>> wrote:
>>> 
 Hi,
 
 does anyone know where I can download the FXG Extension for
 Photoshop CS5 that is mentioned here [1]? The Flash Catalyst site [2]
 does not provide this link anymore. Could the Adobe folks on this list
 be able to provide a working link for that? When importing skins into
 Apache Flex, that extension would be really helpful.
 
 Thank you!
 
 [1] http://blogs.adobe.com/labs/archives/2010/04/adobe_flash_cat_1.html
 [2] http://www.adobe.com/products/flashcatalyst.html
 
 
>>> +1
>>> 
>>> I wasn't able to find the Fireworks -> FXG exporter as well.  Adobe
>> folks,
>>> any chance the plugins can be made available?  This is a big missing link
>>> when it comes to skinning for Flex 4+ components.
>>> 
>>> Thanks,
>>> Om
>> 
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 
>> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: FXG Extension for Photoshop CS5

[Om]

Yes, I am running CS6 - 64 Bit.

Thanks,
Om

On Wed, Mar 13, 2013 at 8:39 PM, Alex Harui  wrote:

> Are you running PS CS5 or something later?
>
>
> On 3/13/13 8:22 PM, "Om"  wrote:
>
> > On Fri, Mar 8, 2013 at 12:59 AM, Sebastian Mohr
> > wrote:
> >
> >> Hi,
> >>
> >> does anyone know where I can download the FXG Extension for
> >> Photoshop CS5 that is mentioned here [1]? The Flash Catalyst site [2]
> >> does not provide this link anymore. Could the Adobe folks on this list
> >> be able to provide a working link for that? When importing skins into
> >> Apache Flex, that extension would be really helpful.
> >>
> >> Thank you!
> >>
> >> [1] http://blogs.adobe.com/labs/archives/2010/04/adobe_flash_cat_1.html
> >> [2] http://www.adobe.com/products/flashcatalyst.html
> >>
> >>
> > +1
> >
> > I wasn't able to find the Fireworks -> FXG exporter as well.  Adobe
> folks,
> > any chance the plugins can be made available?  This is a big missing link
> > when it comes to skinning for Flex 4+ components.
> >
> > Thanks,
> > Om
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>

Re: FXG Extension for Photoshop CS5

[Alex Harui]

Are you running PS CS5 or something later?


On 3/13/13 8:22 PM, "Om"  wrote:

> On Fri, Mar 8, 2013 at 12:59 AM, Sebastian Mohr
> wrote:
> 
>> Hi,
>> 
>> does anyone know where I can download the FXG Extension for
>> Photoshop CS5 that is mentioned here [1]? The Flash Catalyst site [2]
>> does not provide this link anymore. Could the Adobe folks on this list
>> be able to provide a working link for that? When importing skins into
>> Apache Flex, that extension would be really helpful.
>> 
>> Thank you!
>> 
>> [1] http://blogs.adobe.com/labs/archives/2010/04/adobe_flash_cat_1.html
>> [2] http://www.adobe.com/products/flashcatalyst.html
>> 
>> 
> +1
> 
> I wasn't able to find the Fireworks -> FXG exporter as well.  Adobe folks,
> any chance the plugins can be made available?  This is a big missing link
> when it comes to skinning for Flex 4+ components.
> 
> Thanks,
> Om

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: FXG Extension for Photoshop CS5

[Om]

On Fri, Mar 8, 2013 at 12:59 AM, Sebastian Mohr wrote:

> Hi,
>
> does anyone know where I can download the FXG Extension for
> Photoshop CS5 that is mentioned here [1]? The Flash Catalyst site [2]
> does not provide this link anymore. Could the Adobe folks on this list
> be able to provide a working link for that? When importing skins into
> Apache Flex, that extension would be really helpful.
>
> Thank you!
>
> [1] http://blogs.adobe.com/labs/archives/2010/04/adobe_flash_cat_1.html
> [2] http://www.adobe.com/products/flashcatalyst.html
>
>
+1

I wasn't able to find the Fireworks -> FXG exporter as well.  Adobe folks,
any chance the plugins can be made available?  This is a big missing link
when it comes to skinning for Flex 4+ components.

Thanks,
Om

Re: [DISCUSS] Apache Flex SDK Installer 2.5 RC1

[Om]

On Mar 13, 2013 6:06 PM, "Justin Mclean"  wrote:
>
> Hi,
>
> Installer error in the wild:
> https://twitter.com/Yavstr/status/311837235068694528/photo/1
>
> Someone want to reach out?
>
> Justin

Done!

Re: [DISCUSS] Apache Flex SDK Installer 2.5 RC1

[Justin Mclean]

Hi,

Installer error in the wild:
https://twitter.com/Yavstr/status/311837235068694528/photo/1

Someone want to reach out?

Justin

Re: [DISCUSS] Apache Flex SDK Installer 2.5 RC1

[Frédéric THOMAS]

Hi,

I just apply the change for INFO_TRACKING to "Anonymous usage statistics 
will be collected in accordance with our privacy policy" and point to the 
privacy policy url "http://flex.apache.org/about-privacy.html";.


It's translated for English and French, for other languages, it would be 
nice if people can add and do the translations for their own language.


I'll do a RC tomorrow afternoon GMT+1.

Thanks,
-Fred

-Message d'origine- 
From: Justin Mclean

Sent: Wednesday, March 13, 2013 11:21 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Apache Flex SDK Installer 2.5 RC1

Hi,


How about "Anonymous usage statistics will be collected in accordance with
our privacy policy" and have it link to the privacy policy we have on our
website.


+1 to this

Justin 

[jira] [Updated] (FLEX-33190) GridEvent.GRID_DOUBLE_CLICK is dispatched even when two different cells are clicked

[Mark Kessler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLEX-33190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Kessler updated FLEX-33190:


Attachment: DataGridModeTest.mxml

Short test application to show off the new double click mode.

> GridEvent.GRID_DOUBLE_CLICK is dispatched even when two different cells are 
> clicked
> ---
>
> Key: FLEX-33190
> URL: https://issues.apache.org/jira/browse/FLEX-33190
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: Grid
>Affects Versions: Apache Flex 4.8 (parity release)
>Reporter: Shigeru Nakagaki
> Attachments: 0002-Add-new-support-doubleClickMode.patch, 
> DataGridModeTest.mxml, DataGridTest.mxml
>
>
> In dispatchGridClickEvents method of "s:Grid" class, 
> GridEvent.GRID_DOUBLE_CLICK is dispatched. But there is no check of whether 
> the same cell was clicked.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLEX-33190) GridEvent.GRID_DOUBLE_CLICK is dispatched even when two different cells are clicked

[Mark Kessler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLEX-33190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Kessler updated FLEX-33190:


Attachment: 0002-Add-new-support-doubleClickMode.patch

Hope I got this patch file correct with all the confusion of the new GIT 
transition.

> GridEvent.GRID_DOUBLE_CLICK is dispatched even when two different cells are 
> clicked
> ---
>
> Key: FLEX-33190
> URL: https://issues.apache.org/jira/browse/FLEX-33190
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: Grid
>Affects Versions: Apache Flex 4.8 (parity release)
>Reporter: Shigeru Nakagaki
> Attachments: 0002-Add-new-support-doubleClickMode.patch, 
> DataGridTest.mxml
>
>
> In dispatchGridClickEvents method of "s:Grid" class, 
> GridEvent.GRID_DOUBLE_CLICK is dispatched. But there is no check of whether 
> the same cell was clicked.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Git Migration Reset

[Jose Barragan]

Hi Erik,

I guess you've many commits on you local "old" git repo, isn't it? 
Well, those commits are candidates for re-apply them into the new repo when you 
get access to it. 
The most simple way to that is attach the new repo as new remote for your 
actual local repo:

git remote add wip https://git-wip-us.apache.org/repos/asf/flex-sdk.git
git fetch --prune
git -c diff.mnemonicprefix=false -c core.quotepath=false branch -m develop 
develop-old 
git -c diff.mnemonicprefix=false -c core.quotepath=false checkout -b develop 
--track wip/develop
 
at this point, you'll move your commits from develop-old to develop via 
cherrypick, and then make a push over develop to new remote wip.

hopefully it's useful...

PD. Try SourceTree as UI client for Git, it's fully use for free.

Best,
--
Jose Barragan
Software Architect Chief 
Codeoscopic Madrid
C/. Infanta Mercedes, 92. 
Planta 5.  505.
28020 Madrid.
Tel.: +34 912 94 80 80

On Mar 13, 2013, at 9:08 PM, Frédéric THOMAS  wrote:

> Not the svn revision number but the git equivalent, I'm not sure but I 
> wonder, if the git history lenght change, the generated git equivalent (the 
> parent commit SHA1 ids) could change, that's the risk I'm talking about, 
> anyway, there're other ways to make the patches in case it doesn't work, a 
> bit more complicated but possible.
> 
> -Fred
> 
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 13, 2013 9:01 PM
> To: dev@flex.apache.org
> Subject: Re: Git Migration Reset
> 
> Mike and I have already agreed to not touch the code (other than
> locally) of FalconJx... How would the SVN revision change between
> yesterday and whenever the new git repo is created?
> 
> EdB
> 
> 
> 
> On Wed, Mar 13, 2013 at 8:57 PM, Frédéric THOMAS
>  wrote:
>> Great though the only thing that could scary me is if the parent commit of
>> your first commit (the svn revision number) change between the 2 git
>> version, I don't know if it will happen but because the history lenght will
>> change, I've got doubts.
>> 
>> As you said "Time will tell", cross fingers ;-)
>> 
>> 
>> -Fred
>> 
>> -Message d'origine- From: Erik de Bruin
>> Sent: Wednesday, March 13, 2013 8:48 PM
>> 
>> To: dev@flex.apache.org
>> Subject: Re: Git Migration Reset
>> 
>> I seem to be able (in my GUI client) to create a patch file for the
>> commit(s) I have lined up. All I need to do is make a copy of my
>> commit messages and use those while patching the new 'active'
>> branch... I think.
>> 
>> Time will tell, I guess ;-)
>> 
>> EdB
>> 
>> 
>> 
>> On Wed, Mar 13, 2013 at 8:21 PM, Frédéric THOMAS
>>  wrote:
>>> 
>>> Not 100% sure because I never did it before but I guess you can do, on
>>> your
>>> futur inactive project :  is the first commit you did.
>>> 
>>> git format-patch -1 
>>> 
>>> -Fred
>>> 
>>> 
>>> -Message d'origine- From: Erik de Bruin
>>> Sent: Wednesday, March 13, 2013 8:07 PM
>>> To: dev@flex.apache.org
>>> Subject: Re: Git Migration Reset
>>> 
>>> 
 If you moved it from SVN to Git - why cant you just checkin your svn
 changes?
>>> 
>>> 
>>> 
>>> Because git has a lot of minor changes in a lot of the same files that
>>> were already changed in SVN. I spent the afternoon yesterday putting
>>> the final touches to my contributions and this morning (before the
>>> excrement hit the ventilator) putting all of that into a whole bunch
>>> of nicely documented commits. If I were to say "f*ck it" and just
>>> overlay all the most recent files over my last SVN copy, I would loose
>>> all of that work.
>>> 
>>> Also, it's 8 PM over here and I've been at this since 8 AM this
>>> morning. My family is threatening to kick me and my laptop out if I
>>> don't have at least one conherent conversation with them today.
>>> 
 I meant you are on your own  in the sense that I (or anyone else) cannot
 get into your computer to fix things for you.  Of course I appreciate the
>>> 
>>> 
>>> 
>>> The way I understand it, it should be possible to clone the new repo
>>> INFRA will eventually create to my local machine and make that my
>>> "active project". I can then go into my current (by then "inactive")
>>> project and create patches for each of the commits I prepared there,
>>> and apply those patches to my active git project. Am I missing
>>> something, or does that sound like it should work?
>>> 
>>> EdB
>>> 
>>> 
>>> 
>>> --
>>> Ix Multimedia Software
>>> 
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>> 
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>> 
>> 
>> 
>> 
>> --
>> Ix Multimedia Software
>> 
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>> 
>> T. 06-51952295
>> I. www.ixsoftware.nl
> 
> 
> 
> --
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl 

Re: Flex content on the Adobe Developer Connection

[Reynolds, Brian J (Brian)]

There is a lot of good stuff on the devnet site.  If it does not get
donated, is it at risk of disappearing?  If the answer is yes or maybe,
then I'd prefer it be donated instead of lost.

Brian 



On 3/13/13 2:28 PM, "Michelle Yaiser"  wrote:

>Hi, Everyone.
>
>I just heard from legal about getting the approval to donate Flex content
>that was published on the Adobe Developer Connection to Apache.
>
>We can only donate the articles, tutorials, and examples - and the code
>in them - that are written by Adobe employees. That means we can't donate
>any of the content written by non-Adobe authors. All external authors
>select a Creative Commons license and sign a NELA (license agreement).
>Those licenses only give Adobe the right to post the content on Adobe
>sites.  Ownership of the content is retained by the author. The owner is
>the only one who can donate the content to Apache.
>
>There have been mixed opinions on what, if any, ADC Flex content would be
>useful for Apache Flex users. You can find most of the content on the ADC
>from one of the two links below.  If you tell me that getting all content
>written by Adobe or Adobe employees is helpful and what Apache Flex
>wants, I will start prepping it for donation.
>
>* http://www.adobe.com/devnet/flex.html
>
>* http://www.adobe.com/devnet/flex/article-index.html
>
>
>
>Related, we are almost done with all the prep work that needs to be done
>in order to donate the Flex documentation. If anyone has any familiarity
>with Framemaker and GEP, you'll know that getting content out of those
>systems into a useful format is not easy and is very time consuming.
>We'll be donating:
>
>* Using Flex:  http://help.adobe.com/en_US/flex/using/index.html
>
>* non-Flash Builder chapters of Accessing Data with
>Flex
>
>
>I'm happy to answer any questions.
>Cheers,
>Michelle
>--
>---
>Michelle Yaiser
>Instructional Designer  |  Creative Cloud Learning
>Adobe Systems  |  myai...@adobe.com  |  781-839-1697
>

Re: [DISCUSS] Apache Flex SDK Installer 2.5 RC1

[Justin Mclean]

Hi,

> How about "Anonymous usage statistics will be collected in accordance with
> our privacy policy" and have it link to the privacy policy we have on our
> website.

+1 to this

Justin

Re: [Git] Ignore files?

[Justin Mclean]

Hi,

> In the mean while, we can propose some rules that avoid proliferation un
> branches that will become useless. For example, a designated person could
> have the task of prune branches as a dictator or moderator based in its own
> decision (and people should have this into account).

-1 to any system that increases the workload, we're all volunteers, have 
limited time and it hard enough getting someone to be release manager without 
adding extra tasks and responsibilities. We want to make the job easier not 
harder.

Justin

RE: Flex content on the Adobe Developer Connection

[Michelle Yaiser]

Yes. As long as no one else can claim ownership of the content or code, the 
author can donate it to Apache whenever you would like. 

Michelle

-
Michelle Yaiser
Instructional Designer  |  Creative Cloud Learning
Adobe Systems  |  myai...@adobe.com  |  781-839-1697


-Original Message-
From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] 
Sent: Wednesday, March 13, 2013 5:08 PM
To: dev@flex.apache.org
Subject: Re: Flex content on the Adobe Developer Connection

For those of us who were authors and wouldn't mind our content being migrated 
over -- how do you think we should proceed?  Do we just have the rights to 
donate it to Apache?

-Nick

On Wed, Mar 13, 2013 at 4:28 PM, Michelle Yaiser  wrote:

> Hi, Everyone.
>
> I just heard from legal about getting the approval to donate Flex 
> content that was published on the Adobe Developer Connection to Apache.
>
> We can only donate the articles, tutorials, and examples - and the 
> code in them - that are written by Adobe employees. That means we 
> can't donate any of the content written by non-Adobe authors. All 
> external authors select a Creative Commons license and sign a NELA 
> (license agreement). Those licenses only give Adobe the right to post the 
> content on Adobe sites.
>  Ownership of the content is retained by the author. The owner is the 
> only one who can donate the content to Apache.
>
> There have been mixed opinions on what, if any, ADC Flex content would 
> be useful for Apache Flex users. You can find most of the content on 
> the ADC from one of the two links below.  If you tell me that getting 
> all content written by Adobe or Adobe employees is helpful and what 
> Apache Flex wants, I will start prepping it for donation.
>
> * http://www.adobe.com/devnet/flex.html
>
> * http://www.adobe.com/devnet/flex/article-index.html
>
>
>
> Related, we are almost done with all the prep work that needs to be 
> done in order to donate the Flex documentation. If anyone has any 
> familiarity with Framemaker and GEP, you'll know that getting content 
> out of those systems into a useful format is not easy and is very time 
> consuming.  We'll be donating:
>
> * Using Flex:  http://help.adobe.com/en_US/flex/using/index.html
>
> * non-Flash Builder chapters of Accessing Data with Flex<
> http://help.adobe.com/en_US/flex/accessingdata/index.html>
>
>
> I'm happy to answer any questions.
> Cheers,
> Michelle
>
> --
> ---
> Michelle Yaiser
> Instructional Designer  |  Creative Cloud Learning Adobe Systems  |  
> myai...@adobe.com  |  781-839-1697
>
>

Re: [DISCUSS] Apache Flex SDK Installer 2.5 RC1

[Frédéric THOMAS]

Actualy I like it, if it fits, I'll take it.

-Fred

-Message d'origine- 
From: Nicholas Kwiatkowski

Sent: Wednesday, March 13, 2013 10:12 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Apache Flex SDK Installer 2.5 RC1

How about "Anonymous usage statistics will be collected in accordance with
our privacy policy" and have it link to the privacy policy we have on our
website.

-Nick

On Wed, Mar 13, 2013 at 3:07 PM, Frédéric THOMAS 
wrote:



Evertthing on this list [1] has been resolved or found consensus, except
for:


- "Install Log" and "Close" buttons are grey, while they do have a
rollover someone may think they are disabled.

Does someone with better design skill than me could suggest something ?
otherwise I will let it like.


- Can we change "Information about use of this application is being
collected via HTTP requests" to something like "Anonymous/non identifying
information is collected to improve the quality of this installer"

If everybody is ok, I'll choose "This application will ping a server in
order to count the number of times the application is run."

-Fred

[1]

Some possible room for minor (some very minor) improvements:
- By default 11.1 and 11.4 player globals were downloaded, as they are
reasonably small why not download them all?
- "Install Log" and "Close" buttons are grey, while they do have a
rollover someone may think they are disabled.
- "Information about use of this application is being collected via HTTP
requests" sounds rather scary, there no was to opt out and there no
indication to what information is being collected or why it's being
collected. Think we need a link to short paragraph saying what is 
collected

and why.
- Can we change "Information about use of this application is being
collected via HTTP requests" to something like "Anonymous/non identifying
information is collected to improve the quality of this installer"
- Highlight in language drop down is cut off and doesn't extend to RHS of
drop down.
- "Information about use of this application is being collected via HTTP
requests"  locale missing in Spanish, Greek and Portuguese.
- Locale for "Log" button in Portuguese missing
- Looks like the Greek locale has issues - perhaps text not checked in as
UTF8? Black diamonds with "?" show up in text.

Re: [DISCUSS] Apache Flex SDK Installer 2.5 RC1

[Nicholas Kwiatkowski]

How about "Anonymous usage statistics will be collected in accordance with
our privacy policy" and have it link to the privacy policy we have on our
website.

-Nick

On Wed, Mar 13, 2013 at 3:07 PM, Frédéric THOMAS wrote:

> Evertthing on this list [1] has been resolved or found consensus, except
> for:
>
>
> - "Install Log" and "Close" buttons are grey, while they do have a
> rollover someone may think they are disabled.
>
> Does someone with better design skill than me could suggest something ?
> otherwise I will let it like.
>
>
> - Can we change "Information about use of this application is being
> collected via HTTP requests" to something like "Anonymous/non identifying
> information is collected to improve the quality of this installer"
>
> If everybody is ok, I'll choose "This application will ping a server in
> order to count the number of times the application is run."
>
> -Fred
>
> [1]
>
> Some possible room for minor (some very minor) improvements:
> - By default 11.1 and 11.4 player globals were downloaded, as they are
> reasonably small why not download them all?
> - "Install Log" and "Close" buttons are grey, while they do have a
> rollover someone may think they are disabled.
> - "Information about use of this application is being collected via HTTP
> requests" sounds rather scary, there no was to opt out and there no
> indication to what information is being collected or why it's being
> collected. Think we need a link to short paragraph saying what is collected
> and why.
> - Can we change "Information about use of this application is being
> collected via HTTP requests" to something like "Anonymous/non identifying
> information is collected to improve the quality of this installer"
> - Highlight in language drop down is cut off and doesn't extend to RHS of
> drop down.
> - "Information about use of this application is being collected via HTTP
> requests"  locale missing in Spanish, Greek and Portuguese.
> - Locale for "Log" button in Portuguese missing
> - Looks like the Greek locale has issues - perhaps text not checked in as
> UTF8? Black diamonds with "?" show up in text.
>

Re: Flex content on the Adobe Developer Connection

[Nicholas Kwiatkowski]

For those of us who were authors and wouldn't mind our content being
migrated over -- how do you think we should proceed?  Do we just have the
rights to donate it to Apache?

-Nick

On Wed, Mar 13, 2013 at 4:28 PM, Michelle Yaiser  wrote:

> Hi, Everyone.
>
> I just heard from legal about getting the approval to donate Flex content
> that was published on the Adobe Developer Connection to Apache.
>
> We can only donate the articles, tutorials, and examples - and the code in
> them - that are written by Adobe employees. That means we can't donate any
> of the content written by non-Adobe authors. All external authors select a
> Creative Commons license and sign a NELA (license agreement). Those
> licenses only give Adobe the right to post the content on Adobe sites.
>  Ownership of the content is retained by the author. The owner is the only
> one who can donate the content to Apache.
>
> There have been mixed opinions on what, if any, ADC Flex content would be
> useful for Apache Flex users. You can find most of the content on the ADC
> from one of the two links below.  If you tell me that getting all content
> written by Adobe or Adobe employees is helpful and what Apache Flex wants,
> I will start prepping it for donation.
>
> * http://www.adobe.com/devnet/flex.html
>
> * http://www.adobe.com/devnet/flex/article-index.html
>
>
>
> Related, we are almost done with all the prep work that needs to be done
> in order to donate the Flex documentation. If anyone has any familiarity
> with Framemaker and GEP, you'll know that getting content out of those
> systems into a useful format is not easy and is very time consuming.  We'll
> be donating:
>
> * Using Flex:  http://help.adobe.com/en_US/flex/using/index.html
>
> * non-Flash Builder chapters of Accessing Data with Flex<
> http://help.adobe.com/en_US/flex/accessingdata/index.html>
>
>
> I'm happy to answer any questions.
> Cheers,
> Michelle
>
> -
> Michelle Yaiser
> Instructional Designer  |  Creative Cloud Learning
> Adobe Systems  |  myai...@adobe.com  |  781-839-1697
>
>

Flex content on the Adobe Developer Connection

[Michelle Yaiser]

Hi, Everyone.

I just heard from legal about getting the approval to donate Flex content that 
was published on the Adobe Developer Connection to Apache.

We can only donate the articles, tutorials, and examples - and the code in them 
- that are written by Adobe employees. That means we can't donate any of the 
content written by non-Adobe authors. All external authors select a Creative 
Commons license and sign a NELA (license agreement). Those licenses only give 
Adobe the right to post the content on Adobe sites.  Ownership of the content 
is retained by the author. The owner is the only one who can donate the content 
to Apache.

There have been mixed opinions on what, if any, ADC Flex content would be 
useful for Apache Flex users. You can find most of the content on the ADC from 
one of the two links below.  If you tell me that getting all content written by 
Adobe or Adobe employees is helpful and what Apache Flex wants, I will start 
prepping it for donation.

* http://www.adobe.com/devnet/flex.html

* http://www.adobe.com/devnet/flex/article-index.html



Related, we are almost done with all the prep work that needs to be done in 
order to donate the Flex documentation. If anyone has any familiarity with 
Framemaker and GEP, you'll know that getting content out of those systems into 
a useful format is not easy and is very time consuming.  We'll be donating:

* Using Flex:  http://help.adobe.com/en_US/flex/using/index.html

* non-Flash Builder chapters of Accessing Data with 
Flex


I'm happy to answer any questions.
Cheers,
Michelle
-
Michelle Yaiser
Instructional Designer  |  Creative Cloud Learning
Adobe Systems  |  myai...@adobe.com  |  781-839-1697

Re: Git Migration Reset

[Frédéric THOMAS]

Not the svn revision number but the git equivalent, I'm not sure but I 
wonder, if the git history lenght change, the generated git equivalent (the 
parent commit SHA1 ids) could change, that's the risk I'm talking about, 
anyway, there're other ways to make the patches in case it doesn't work, a 
bit more complicated but possible.


-Fred

-Message d'origine- 
From: Erik de Bruin

Sent: Wednesday, March 13, 2013 9:01 PM
To: dev@flex.apache.org
Subject: Re: Git Migration Reset

Mike and I have already agreed to not touch the code (other than
locally) of FalconJx... How would the SVN revision change between
yesterday and whenever the new git repo is created?

EdB



On Wed, Mar 13, 2013 at 8:57 PM, Frédéric THOMAS
 wrote:

Great though the only thing that could scary me is if the parent commit of
your first commit (the svn revision number) change between the 2 git
version, I don't know if it will happen but because the history lenght 
will

change, I've got doubts.

As you said "Time will tell", cross fingers ;-)


-Fred

-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 8:48 PM

To: dev@flex.apache.org
Subject: Re: Git Migration Reset

I seem to be able (in my GUI client) to create a patch file for the
commit(s) I have lined up. All I need to do is make a copy of my
commit messages and use those while patching the new 'active'
branch... I think.

Time will tell, I guess ;-)

EdB



On Wed, Mar 13, 2013 at 8:21 PM, Frédéric THOMAS
 wrote:


Not 100% sure because I never did it before but I guess you can do, on
your
futur inactive project :  is the first commit you did.

git format-patch -1 

-Fred


-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 8:07 PM
To: dev@flex.apache.org
Subject: Re: Git Migration Reset



If you moved it from SVN to Git - why cant you just checkin your svn
changes?




Because git has a lot of minor changes in a lot of the same files that
were already changed in SVN. I spent the afternoon yesterday putting
the final touches to my contributions and this morning (before the
excrement hit the ventilator) putting all of that into a whole bunch
of nicely documented commits. If I were to say "f*ck it" and just
overlay all the most recent files over my last SVN copy, I would loose
all of that work.

Also, it's 8 PM over here and I've been at this since 8 AM this
morning. My family is threatening to kick me and my laptop out if I
don't have at least one conherent conversation with them today.


I meant you are on your own  in the sense that I (or anyone else) cannot
get into your computer to fix things for you.  Of course I appreciate 
the




The way I understand it, it should be possible to clone the new repo
INFRA will eventually create to my local machine and make that my
"active project". I can then go into my current (by then "inactive")
project and create patches for each of the commits I prepared there,
and apply those patches to my active git project. Am I missing
something, or does that sound like it should work?

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl





--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl 

Re: Git Migration Reset

[Erik de Bruin]

Mike and I have already agreed to not touch the code (other than
locally) of FalconJx... How would the SVN revision change between
yesterday and whenever the new git repo is created?

EdB



On Wed, Mar 13, 2013 at 8:57 PM, Frédéric THOMAS
 wrote:
> Great though the only thing that could scary me is if the parent commit of
> your first commit (the svn revision number) change between the 2 git
> version, I don't know if it will happen but because the history lenght will
> change, I've got doubts.
>
> As you said "Time will tell", cross fingers ;-)
>
>
> -Fred
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 13, 2013 8:48 PM
>
> To: dev@flex.apache.org
> Subject: Re: Git Migration Reset
>
> I seem to be able (in my GUI client) to create a patch file for the
> commit(s) I have lined up. All I need to do is make a copy of my
> commit messages and use those while patching the new 'active'
> branch... I think.
>
> Time will tell, I guess ;-)
>
> EdB
>
>
>
> On Wed, Mar 13, 2013 at 8:21 PM, Frédéric THOMAS
>  wrote:
>>
>> Not 100% sure because I never did it before but I guess you can do, on
>> your
>> futur inactive project :  is the first commit you did.
>>
>> git format-patch -1 
>>
>> -Fred
>>
>>
>> -Message d'origine- From: Erik de Bruin
>> Sent: Wednesday, March 13, 2013 8:07 PM
>> To: dev@flex.apache.org
>> Subject: Re: Git Migration Reset
>>
>>
>>> If you moved it from SVN to Git - why cant you just checkin your svn
>>> changes?
>>
>>
>>
>> Because git has a lot of minor changes in a lot of the same files that
>> were already changed in SVN. I spent the afternoon yesterday putting
>> the final touches to my contributions and this morning (before the
>> excrement hit the ventilator) putting all of that into a whole bunch
>> of nicely documented commits. If I were to say "f*ck it" and just
>> overlay all the most recent files over my last SVN copy, I would loose
>> all of that work.
>>
>> Also, it's 8 PM over here and I've been at this since 8 AM this
>> morning. My family is threatening to kick me and my laptop out if I
>> don't have at least one conherent conversation with them today.
>>
>>> I meant you are on your own  in the sense that I (or anyone else) cannot
>>> get into your computer to fix things for you.  Of course I appreciate the
>>
>>
>>
>> The way I understand it, it should be possible to clone the new repo
>> INFRA will eventually create to my local machine and make that my
>> "active project". I can then go into my current (by then "inactive")
>> project and create patches for each of the commits I prepared there,
>> and apply those patches to my active git project. Am I missing
>> something, or does that sound like it should work?
>>
>> EdB
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Git Migration Reset

[Frédéric THOMAS]

Great though the only thing that could scary me is if the parent commit of 
your first commit (the svn revision number) change between the 2 git 
version, I don't know if it will happen but because the history lenght will 
change, I've got doubts.


As you said "Time will tell", cross fingers ;-)

-Fred

-Message d'origine- 
From: Erik de Bruin

Sent: Wednesday, March 13, 2013 8:48 PM
To: dev@flex.apache.org
Subject: Re: Git Migration Reset

I seem to be able (in my GUI client) to create a patch file for the
commit(s) I have lined up. All I need to do is make a copy of my
commit messages and use those while patching the new 'active'
branch... I think.

Time will tell, I guess ;-)

EdB



On Wed, Mar 13, 2013 at 8:21 PM, Frédéric THOMAS
 wrote:
Not 100% sure because I never did it before but I guess you can do, on 
your

futur inactive project :  is the first commit you did.

git format-patch -1 

-Fred


-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 8:07 PM
To: dev@flex.apache.org
Subject: Re: Git Migration Reset



If you moved it from SVN to Git - why cant you just checkin your svn
changes?



Because git has a lot of minor changes in a lot of the same files that
were already changed in SVN. I spent the afternoon yesterday putting
the final touches to my contributions and this morning (before the
excrement hit the ventilator) putting all of that into a whole bunch
of nicely documented commits. If I were to say "f*ck it" and just
overlay all the most recent files over my last SVN copy, I would loose
all of that work.

Also, it's 8 PM over here and I've been at this since 8 AM this
morning. My family is threatening to kick me and my laptop out if I
don't have at least one conherent conversation with them today.


I meant you are on your own  in the sense that I (or anyone else) cannot
get into your computer to fix things for you.  Of course I appreciate the



The way I understand it, it should be possible to clone the new repo
INFRA will eventually create to my local machine and make that my
"active project". I can then go into my current (by then "inactive")
project and create patches for each of the commits I prepared there,
and apply those patches to my active git project. Am I missing
something, or does that sound like it should work?

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl 

Re: Git Migration Reset

[Erik de Bruin]

I seem to be able (in my GUI client) to create a patch file for the
commit(s) I have lined up. All I need to do is make a copy of my
commit messages and use those while patching the new 'active'
branch... I think.

Time will tell, I guess ;-)

EdB



On Wed, Mar 13, 2013 at 8:21 PM, Frédéric THOMAS
 wrote:
> Not 100% sure because I never did it before but I guess you can do, on your
> futur inactive project :  is the first commit you did.
>
> git format-patch -1 
>
> -Fred
>
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 13, 2013 8:07 PM
> To: dev@flex.apache.org
> Subject: Re: Git Migration Reset
>
>
>> If you moved it from SVN to Git - why cant you just checkin your svn
>> changes?
>
>
> Because git has a lot of minor changes in a lot of the same files that
> were already changed in SVN. I spent the afternoon yesterday putting
> the final touches to my contributions and this morning (before the
> excrement hit the ventilator) putting all of that into a whole bunch
> of nicely documented commits. If I were to say "f*ck it" and just
> overlay all the most recent files over my last SVN copy, I would loose
> all of that work.
>
> Also, it's 8 PM over here and I've been at this since 8 AM this
> morning. My family is threatening to kick me and my laptop out if I
> don't have at least one conherent conversation with them today.
>
>> I meant you are on your own  in the sense that I (or anyone else) cannot
>> get into your computer to fix things for you.  Of course I appreciate the
>
>
> The way I understand it, it should be possible to clone the new repo
> INFRA will eventually create to my local machine and make that my
> "active project". I can then go into my current (by then "inactive")
> project and create patches for each of the commits I prepared there,
> and apply those patches to my active git project. Am I missing
> something, or does that sound like it should work?
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Git Migration Reset

[Erik de Bruin]

> Ah, so you made changes to the supposedly read-only git repo in the
> meantime.  Why would you do something like that?  While at the same time
> you were asking for a do over.  Does not compute.  What did you expect?

There was nothing "read-only" about my local copy. The understanding
at the time was that write enableing of the the remote copy (branch?)
would be a matter of hours, subject only to a check by the PMC. Before
starting work, I did check the Falcon git repo, and it looked good. It
thing it was not unreasonable for me to expect the 'write' switch to
be throw with the same expediency with which INFRA moved at the start
of this episode.

On the point of the "do over": I don't recall asking for such a thing.
I understand no that the confusion might have come from the [DISCUSS]
thread I started - note: this was AFTER INFRA took their unilateral
action by removing the git repos and re-enabling SVN - was about
postponing the migration until INFRA had taken their 'git' support out
of beta and was ready to fully support it, presumably months if not
years in the future. That thread is not VOTE or LAZY but DISCUSS. I
specifically chose that subject so no action would be taken until a
discussion had taken place.

> Theoretically, that would work.  But given that you are not too familiar
> with Git, it would be a risky proposition.  It is up to you.

Well, "up to me" is not really the case, as I explained, but I
understand it's "out of your hands." I'll make a full backup of the
actual source files, just to make sure no code is lost when trying to
manage the move to git.

Now, before this gets out of hand, let me re-iterate: by now - by way
of a healthy serving of tutorials and some needed distraction on
/r/aww - I nearly understand the basics of git. I accept the project
is moving to git, unless a new consensus on the DISCUSS thread leads
to a new VOTE :-) I am doing my best to have my code ready for the
migration and by sharing my experiences and frustrations with the list
I try to smooth the way for others.

TL;DR: confusion all over the place, but really there's nothing to see
here, we're moving forward to a 'git' future.

EdB



> Thanks,
> Om
>
>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Git Migration Reset

[Frédéric THOMAS]

Not 100% sure because I never did it before but I guess you can do, on your 
futur inactive project :  is the first commit you did.


git format-patch -1 

-Fred


-Message d'origine- 
From: Erik de Bruin

Sent: Wednesday, March 13, 2013 8:07 PM
To: dev@flex.apache.org
Subject: Re: Git Migration Reset


If you moved it from SVN to Git - why cant you just checkin your svn
changes?


Because git has a lot of minor changes in a lot of the same files that
were already changed in SVN. I spent the afternoon yesterday putting
the final touches to my contributions and this morning (before the
excrement hit the ventilator) putting all of that into a whole bunch
of nicely documented commits. If I were to say "f*ck it" and just
overlay all the most recent files over my last SVN copy, I would loose
all of that work.

Also, it's 8 PM over here and I've been at this since 8 AM this
morning. My family is threatening to kick me and my laptop out if I
don't have at least one conherent conversation with them today.


I meant you are on your own  in the sense that I (or anyone else) cannot
get into your computer to fix things for you.  Of course I appreciate the


The way I understand it, it should be possible to clone the new repo
INFRA will eventually create to my local machine and make that my
"active project". I can then go into my current (by then "inactive")
project and create patches for each of the commits I prepared there,
and apply those patches to my active git project. Am I missing
something, or does that sound like it should work?

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl 

Re: Git Migration Reset

[Om]

On Wed, Mar 13, 2013 at 12:07 PM, Erik de Bruin  wrote:

> > If you moved it from SVN to Git - why cant you just checkin your svn
> > changes?
>
> Because git has a lot of minor changes in a lot of the same files that
> were already changed in SVN. I spent the afternoon yesterday putting
> the final touches to my contributions and this morning (before the
> excrement hit the ventilator) putting all of that into a whole bunch
> of nicely documented commits. If I were to say "f*ck it" and just
> overlay all the most recent files over my last SVN copy, I would loose
> all of that work.
>

Ah, so you made changes to the supposedly read-only git repo in the
meantime.  Why would you do something like that?  While at the same time
you were asking for a do over.  Does not compute.  What did you expect?


>
> Also, it's 8 PM over here and I've been at this since 8 AM this
> morning. My family is threatening to kick me and my laptop out if I
> don't have at least one conherent conversation with them today.
>
> > I meant you are on your own  in the sense that I (or anyone else) cannot
> > get into your computer to fix things for you.  Of course I appreciate the
>
> The way I understand it, it should be possible to clone the new repo
> INFRA will eventually create to my local machine and make that my
> "active project". I can then go into my current (by then "inactive")
> project and create patches for each of the commits I prepared there,
> and apply those patches to my active git project. Am I missing
> something, or does that sound like it should work?
>
> EdB
>
>
Theoretically, that would work.  But given that you are not too familiar
with Git, it would be a risky proposition.  It is up to you.

Thanks,
Om


>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

Re: Git Migration Reset

[Erik de Bruin]

> If you moved it from SVN to Git - why cant you just checkin your svn
> changes?

Because git has a lot of minor changes in a lot of the same files that
were already changed in SVN. I spent the afternoon yesterday putting
the final touches to my contributions and this morning (before the
excrement hit the ventilator) putting all of that into a whole bunch
of nicely documented commits. If I were to say "f*ck it" and just
overlay all the most recent files over my last SVN copy, I would loose
all of that work.

Also, it's 8 PM over here and I've been at this since 8 AM this
morning. My family is threatening to kick me and my laptop out if I
don't have at least one conherent conversation with them today.

> I meant you are on your own  in the sense that I (or anyone else) cannot
> get into your computer to fix things for you.  Of course I appreciate the

The way I understand it, it should be possible to clone the new repo
INFRA will eventually create to my local machine and make that my
"active project". I can then go into my current (by then "inactive")
project and create patches for each of the commits I prepared there,
and apply those patches to my active git project. Am I missing
something, or does that sound like it should work?

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [DISCUSS] Apache Flex SDK Installer 2.5 RC1

[Frédéric THOMAS]

Evertthing on this list [1] has been resolved or found consensus, except 
for:


- "Install Log" and "Close" buttons are grey, while they do have a rollover 
someone may think they are disabled.


Does someone with better design skill than me could suggest something ? 
otherwise I will let it like.


- Can we change "Information about use of this application is being 
collected via HTTP requests" to something like "Anonymous/non identifying 
information is collected to improve the quality of this installer"


If everybody is ok, I'll choose "This application will ping a server in 
order to count the number of times the application is run."


-Fred

[1]
Some possible room for minor (some very minor) improvements:
- By default 11.1 and 11.4 player globals were downloaded, as they are 
reasonably small why not download them all?
- "Install Log" and "Close" buttons are grey, while they do have a rollover 
someone may think they are disabled.
- "Information about use of this application is being collected via HTTP 
requests" sounds rather scary, there no was to opt out and there no 
indication to what information is being collected or why it's being 
collected. Think we need a link to short paragraph saying what is collected 
and why.
- Can we change "Information about use of this application is being 
collected via HTTP requests" to something like "Anonymous/non identifying 
information is collected to improve the quality of this installer"
- Highlight in language drop down is cut off and doesn't extend to RHS of 
drop down.
- "Information about use of this application is being collected via HTTP 
requests"  locale missing in Spanish, Greek and Portuguese.

- Locale for "Log" button in Portuguese missing
- Looks like the Greek locale has issues - perhaps text not checked in as 
UTF8? Black diamonds with "?" show up in text. 

Re: Git Migration Reset

[Om]

On Wed, Mar 13, 2013 at 11:51 AM, Erik de Bruin  wrote:

> Om, I understand you're trying to help and I appreciate it. If I have
> somehow implied that you were somehow the one to "blaim", I'm sorry.
> All I'm saying is that it took me a day and a half to get everything
> from SVN to git and I don't have the time tonight to reverse the
> process in a way that will allow me to be accurate and on time


If you moved it from SVN to Git - why cant you just checkin your svn
changes?


> (and no
> amout of kittens would keep me from ranting if I switched back and
> INFRA had made SVN read-only again).
>
>
Which is why I am urging you to check everything into SVN asap.  The
internet is running out of kittens as we speak.


> EdB
>
> PS. "You're on your own" is not really constructive... The code I'm
> trying to save will be (I humbly think) important to the project and I
> think it's worth a bit of team effort to make sure it'll get where it
> needs going.
>
>
I meant you are on your own  in the sense that I (or anyone else) cannot
get into your computer to fix things for you.  Of course I appreciate the
work you are doing.  I wont be responding to your emails if I dint :-)

Thanks,
Om



> On Wed, Mar 13, 2013 at 7:44 PM, Om  wrote:
> > On Wed, Mar 13, 2013 at 11:34 AM, Erik de Bruin 
> wrote:
> >
> >> Won't work, I'm not on SVN anymore (didn't want to risk having both
> >> .git and .svn in the same project). I understood that moving from SVN
> >> to git meant get a new clone from the git origin (i.e. create a new
> >> working copy on my machine) and apply the changes that were in SVN to
> >> that clone, in as atomic commits as possible. That is what I did. I
> >> also finished the code, the changes for which I also committed to git.
> >>
> >> Now I don't see any way to get the stuff from my git repo back into my
> >> SVN repo, especially since I don't have much time left today :-(
> >>
> >> Frustration level rising again... back to viewing kittens (of the
> >> feline persuasion, to be sure)!
> >>
> >> EdB
> >>
> >>
> > I am sorry Erik, but you asked to do this from scratch.  We complained to
> > Infra that both SVN and Git are read-only and hence they opened up SVN.
> >  Which means that we have to live it now.
> >
> > I strongly suggest you to check in your changes into SVN soon.  If not,
> you
> > are on your own.  I am trying to help you here.
> >
> > Thanks,
> > Om
> >
> >
> >
> >>
> >>
> >>
> >>
> >> On Wed, Mar 13, 2013 at 7:28 PM, Om  wrote:
> >> > On Wed, Mar 13, 2013 at 11:05 AM, Erik de Bruin 
> >> wrote:
> >> >
> >> >> Carlos,
> >> >>
> >> >> I have since yesterday moved all my changes to git. They are in total
> >> >> 14 commits to my local clone. Do I do a patch or copy for each of
> >> >> those commits separately, or is there a way of "exporting" the whole
> >> >> set of commits which I then import into the new clone? It would be a
> >> >> hassle to have dozens of files that are changed in one long list in
> >> >> the new clone and to have to reconstruct my commits one by one...
> >> >>
> >> >> EdB
> >> >>
> >> >>
> >> > Just check it into SVN.  But do it quickly.  Any commit you made to
> Git
> >> is
> >> > invalid now.  Please dont complicate things for yourself anymore.
> >> >
> >> > Thanks,
> >> > Om
> >> >
> >> >
> >> >>
> >> >> On Wed, Mar 13, 2013 at 6:59 PM, Carlos Rovira
> >> >>  wrote:
> >> >> > Hi,
> >> >> >
> >> >> > it seems svn changes not in GIT are a source of problems for many
> of
> >> us.
> >> >> > Only want to let you know that really it's not. All of you with a
> >> delta
> >> >> set
> >> >> > of changes can extract a patch or even copy de structure of files
> over
> >> >> your
> >> >> > git clone (maybe more easy). Then you will see the same changes
> that
> >> you
> >> >> > had in SVN and you are able to continue working locally.
> >> >> >
> >> >> > Then when GIT repo has RW open...you can pull to remote.
> >> >> >
> >> >> > Things are moving now with Davids effort and he will done it from
> >> >> scratch,
> >> >> > but only want to share this info to let you know that maybe you are
> >> >> seeing
> >> >> > a problem where there is none.
> >> >> >
> >> >> > Hope that helps.
> >> >> >
> >> >> > Best,
> >> >> >
> >> >> > Carlos
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > 2013/3/13 Om 
> >> >> >
> >> >> >> In case you are not following the JIRA ticket, Infra has confirmed
> >> that
> >> >> >> they have opened SVN back up for read/write.  Also, they will be
> >> >> starting
> >> >> >> the move to Git this evening (GMT -5) again.
> >> >> >>
> >> >> >> *So, everyone please check-in all your changes into SVN asap.
> >>  *Sometime
> >> >> >> this evening, SVN will go read-only at which point the migration
> to
> >> Git
> >> >> >> will start.
> >> >> >>
> >> >> >> Here is David@Infra's note regarding this:
> >> >> >>
> >> >> >> I'll start from scratch this evening. I'll make a list of svn
> trees
> >> and
> >> >> >> > start down them one by one, though I'll likely get

Re: Git Migration Reset

[Erik de Bruin]

Om, I understand you're trying to help and I appreciate it. If I have
somehow implied that you were somehow the one to "blaim", I'm sorry.
All I'm saying is that it took me a day and a half to get everything
from SVN to git and I don't have the time tonight to reverse the
process in a way that will allow me to be accurate and on time (and no
amout of kittens would keep me from ranting if I switched back and
INFRA had made SVN read-only again).

EdB

PS. "You're on your own" is not really constructive... The code I'm
trying to save will be (I humbly think) important to the project and I
think it's worth a bit of team effort to make sure it'll get where it
needs going.

On Wed, Mar 13, 2013 at 7:44 PM, Om  wrote:
> On Wed, Mar 13, 2013 at 11:34 AM, Erik de Bruin  wrote:
>
>> Won't work, I'm not on SVN anymore (didn't want to risk having both
>> .git and .svn in the same project). I understood that moving from SVN
>> to git meant get a new clone from the git origin (i.e. create a new
>> working copy on my machine) and apply the changes that were in SVN to
>> that clone, in as atomic commits as possible. That is what I did. I
>> also finished the code, the changes for which I also committed to git.
>>
>> Now I don't see any way to get the stuff from my git repo back into my
>> SVN repo, especially since I don't have much time left today :-(
>>
>> Frustration level rising again... back to viewing kittens (of the
>> feline persuasion, to be sure)!
>>
>> EdB
>>
>>
> I am sorry Erik, but you asked to do this from scratch.  We complained to
> Infra that both SVN and Git are read-only and hence they opened up SVN.
>  Which means that we have to live it now.
>
> I strongly suggest you to check in your changes into SVN soon.  If not, you
> are on your own.  I am trying to help you here.
>
> Thanks,
> Om
>
>
>
>>
>>
>>
>>
>> On Wed, Mar 13, 2013 at 7:28 PM, Om  wrote:
>> > On Wed, Mar 13, 2013 at 11:05 AM, Erik de Bruin 
>> wrote:
>> >
>> >> Carlos,
>> >>
>> >> I have since yesterday moved all my changes to git. They are in total
>> >> 14 commits to my local clone. Do I do a patch or copy for each of
>> >> those commits separately, or is there a way of "exporting" the whole
>> >> set of commits which I then import into the new clone? It would be a
>> >> hassle to have dozens of files that are changed in one long list in
>> >> the new clone and to have to reconstruct my commits one by one...
>> >>
>> >> EdB
>> >>
>> >>
>> > Just check it into SVN.  But do it quickly.  Any commit you made to Git
>> is
>> > invalid now.  Please dont complicate things for yourself anymore.
>> >
>> > Thanks,
>> > Om
>> >
>> >
>> >>
>> >> On Wed, Mar 13, 2013 at 6:59 PM, Carlos Rovira
>> >>  wrote:
>> >> > Hi,
>> >> >
>> >> > it seems svn changes not in GIT are a source of problems for many of
>> us.
>> >> > Only want to let you know that really it's not. All of you with a
>> delta
>> >> set
>> >> > of changes can extract a patch or even copy de structure of files over
>> >> your
>> >> > git clone (maybe more easy). Then you will see the same changes that
>> you
>> >> > had in SVN and you are able to continue working locally.
>> >> >
>> >> > Then when GIT repo has RW open...you can pull to remote.
>> >> >
>> >> > Things are moving now with Davids effort and he will done it from
>> >> scratch,
>> >> > but only want to share this info to let you know that maybe you are
>> >> seeing
>> >> > a problem where there is none.
>> >> >
>> >> > Hope that helps.
>> >> >
>> >> > Best,
>> >> >
>> >> > Carlos
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > 2013/3/13 Om 
>> >> >
>> >> >> In case you are not following the JIRA ticket, Infra has confirmed
>> that
>> >> >> they have opened SVN back up for read/write.  Also, they will be
>> >> starting
>> >> >> the move to Git this evening (GMT -5) again.
>> >> >>
>> >> >> *So, everyone please check-in all your changes into SVN asap.
>>  *Sometime
>> >> >> this evening, SVN will go read-only at which point the migration to
>> Git
>> >> >> will start.
>> >> >>
>> >> >> Here is David@Infra's note regarding this:
>> >> >>
>> >> >> I'll start from scratch this evening. I'll make a list of svn trees
>> and
>> >> >> > start down them one by one, though I'll likely get multiple done
>> in a
>> >> >> > single sitting. Typically it takes 20 minutes to a few dedicated
>> >> hours of
>> >> >> > time per svn tree > git migration.  I'll probably take asjs,
>> external
>> >> and
>> >> >> > falcon tonight. Then the PMC needs to audit, and we can make it RW
>> >> when
>> >> >> > you are satisfied. If we find problems with a given migration, I've
>> >> had
>> >> >> it
>> >> >> > take substantially longer, or be a quick fix, it depends. That
>> said, I
>> >> >> > can't give you a dedicated timeline for all of this - I am doing
>> this
>> >> as
>> >> >> a
>> >> >> > volunteer, and am travelling extensively this week, so I'll try and
>> >> take
>> >> >> > care of it as I have time available.
>> >> >>
>> >> >>
>> >> >>
>> >> >> And

Re: Git Migration Reset

[Om]

On Wed, Mar 13, 2013 at 11:34 AM, Erik de Bruin  wrote:

> Won't work, I'm not on SVN anymore (didn't want to risk having both
> .git and .svn in the same project). I understood that moving from SVN
> to git meant get a new clone from the git origin (i.e. create a new
> working copy on my machine) and apply the changes that were in SVN to
> that clone, in as atomic commits as possible. That is what I did. I
> also finished the code, the changes for which I also committed to git.
>
> Now I don't see any way to get the stuff from my git repo back into my
> SVN repo, especially since I don't have much time left today :-(
>
> Frustration level rising again... back to viewing kittens (of the
> feline persuasion, to be sure)!
>
> EdB
>
>
I am sorry Erik, but you asked to do this from scratch.  We complained to
Infra that both SVN and Git are read-only and hence they opened up SVN.
 Which means that we have to live it now.

I strongly suggest you to check in your changes into SVN soon.  If not, you
are on your own.  I am trying to help you here.

Thanks,
Om



>
>
>
>
> On Wed, Mar 13, 2013 at 7:28 PM, Om  wrote:
> > On Wed, Mar 13, 2013 at 11:05 AM, Erik de Bruin 
> wrote:
> >
> >> Carlos,
> >>
> >> I have since yesterday moved all my changes to git. They are in total
> >> 14 commits to my local clone. Do I do a patch or copy for each of
> >> those commits separately, or is there a way of "exporting" the whole
> >> set of commits which I then import into the new clone? It would be a
> >> hassle to have dozens of files that are changed in one long list in
> >> the new clone and to have to reconstruct my commits one by one...
> >>
> >> EdB
> >>
> >>
> > Just check it into SVN.  But do it quickly.  Any commit you made to Git
> is
> > invalid now.  Please dont complicate things for yourself anymore.
> >
> > Thanks,
> > Om
> >
> >
> >>
> >> On Wed, Mar 13, 2013 at 6:59 PM, Carlos Rovira
> >>  wrote:
> >> > Hi,
> >> >
> >> > it seems svn changes not in GIT are a source of problems for many of
> us.
> >> > Only want to let you know that really it's not. All of you with a
> delta
> >> set
> >> > of changes can extract a patch or even copy de structure of files over
> >> your
> >> > git clone (maybe more easy). Then you will see the same changes that
> you
> >> > had in SVN and you are able to continue working locally.
> >> >
> >> > Then when GIT repo has RW open...you can pull to remote.
> >> >
> >> > Things are moving now with Davids effort and he will done it from
> >> scratch,
> >> > but only want to share this info to let you know that maybe you are
> >> seeing
> >> > a problem where there is none.
> >> >
> >> > Hope that helps.
> >> >
> >> > Best,
> >> >
> >> > Carlos
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > 2013/3/13 Om 
> >> >
> >> >> In case you are not following the JIRA ticket, Infra has confirmed
> that
> >> >> they have opened SVN back up for read/write.  Also, they will be
> >> starting
> >> >> the move to Git this evening (GMT -5) again.
> >> >>
> >> >> *So, everyone please check-in all your changes into SVN asap.
>  *Sometime
> >> >> this evening, SVN will go read-only at which point the migration to
> Git
> >> >> will start.
> >> >>
> >> >> Here is David@Infra's note regarding this:
> >> >>
> >> >> I'll start from scratch this evening. I'll make a list of svn trees
> and
> >> >> > start down them one by one, though I'll likely get multiple done
> in a
> >> >> > single sitting. Typically it takes 20 minutes to a few dedicated
> >> hours of
> >> >> > time per svn tree > git migration.  I'll probably take asjs,
> external
> >> and
> >> >> > falcon tonight. Then the PMC needs to audit, and we can make it RW
> >> when
> >> >> > you are satisfied. If we find problems with a given migration, I've
> >> had
> >> >> it
> >> >> > take substantially longer, or be a quick fix, it depends. That
> said, I
> >> >> > can't give you a dedicated timeline for all of this - I am doing
> this
> >> as
> >> >> a
> >> >> > volunteer, and am travelling extensively this week, so I'll try and
> >> take
> >> >> > care of it as I have time available.
> >> >>
> >> >>
> >> >>
> >> >> And if you have any questions and suggestions do so quickly so I can
> >> >> clarify with David.  Please DO NOT post on the JIRA ticket.  I will
> be
> >> >> online for the 12 hours (at least)  I plan to help shepherd this
> process
> >> >> all the way to the end.
> >> >>
> >> >> Thanks,
> >> >> Om
> >> >>
> >> >> [1] https://issues.apache.org/jira/browse/INFRA-5549
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Carlos Rovira
> >> > Director de Tecnología
> >> > M: +34 607 22 60 05
> >> > F:  +34 912 94 80 80
> >> > http://www.codeoscopic.com
> >> > http://www.directwriter.es
> >> > http://www.avant2.es
> >>
> >>
> >>
> >> --
> >> Ix Multimedia Software
> >>
> >> Jan Luykenstraat 27
> >> 3521 VB Utrecht
> >>
> >> T. 06-51952295
> >> I. www.ixsoftware.nl
> >>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> 

Re: Git Migration Reset

[Erik de Bruin]

Won't work, I'm not on SVN anymore (didn't want to risk having both
.git and .svn in the same project). I understood that moving from SVN
to git meant get a new clone from the git origin (i.e. create a new
working copy on my machine) and apply the changes that were in SVN to
that clone, in as atomic commits as possible. That is what I did. I
also finished the code, the changes for which I also committed to git.

Now I don't see any way to get the stuff from my git repo back into my
SVN repo, especially since I don't have much time left today :-(

Frustration level rising again... back to viewing kittens (of the
feline persuasion, to be sure)!

EdB





On Wed, Mar 13, 2013 at 7:28 PM, Om  wrote:
> On Wed, Mar 13, 2013 at 11:05 AM, Erik de Bruin  wrote:
>
>> Carlos,
>>
>> I have since yesterday moved all my changes to git. They are in total
>> 14 commits to my local clone. Do I do a patch or copy for each of
>> those commits separately, or is there a way of "exporting" the whole
>> set of commits which I then import into the new clone? It would be a
>> hassle to have dozens of files that are changed in one long list in
>> the new clone and to have to reconstruct my commits one by one...
>>
>> EdB
>>
>>
> Just check it into SVN.  But do it quickly.  Any commit you made to Git is
> invalid now.  Please dont complicate things for yourself anymore.
>
> Thanks,
> Om
>
>
>>
>> On Wed, Mar 13, 2013 at 6:59 PM, Carlos Rovira
>>  wrote:
>> > Hi,
>> >
>> > it seems svn changes not in GIT are a source of problems for many of us.
>> > Only want to let you know that really it's not. All of you with a delta
>> set
>> > of changes can extract a patch or even copy de structure of files over
>> your
>> > git clone (maybe more easy). Then you will see the same changes that you
>> > had in SVN and you are able to continue working locally.
>> >
>> > Then when GIT repo has RW open...you can pull to remote.
>> >
>> > Things are moving now with Davids effort and he will done it from
>> scratch,
>> > but only want to share this info to let you know that maybe you are
>> seeing
>> > a problem where there is none.
>> >
>> > Hope that helps.
>> >
>> > Best,
>> >
>> > Carlos
>> >
>> >
>> >
>> >
>> >
>> > 2013/3/13 Om 
>> >
>> >> In case you are not following the JIRA ticket, Infra has confirmed that
>> >> they have opened SVN back up for read/write.  Also, they will be
>> starting
>> >> the move to Git this evening (GMT -5) again.
>> >>
>> >> *So, everyone please check-in all your changes into SVN asap.  *Sometime
>> >> this evening, SVN will go read-only at which point the migration to Git
>> >> will start.
>> >>
>> >> Here is David@Infra's note regarding this:
>> >>
>> >> I'll start from scratch this evening. I'll make a list of svn trees and
>> >> > start down them one by one, though I'll likely get multiple done in a
>> >> > single sitting. Typically it takes 20 minutes to a few dedicated
>> hours of
>> >> > time per svn tree > git migration.  I'll probably take asjs, external
>> and
>> >> > falcon tonight. Then the PMC needs to audit, and we can make it RW
>> when
>> >> > you are satisfied. If we find problems with a given migration, I've
>> had
>> >> it
>> >> > take substantially longer, or be a quick fix, it depends. That said, I
>> >> > can't give you a dedicated timeline for all of this - I am doing this
>> as
>> >> a
>> >> > volunteer, and am travelling extensively this week, so I'll try and
>> take
>> >> > care of it as I have time available.
>> >>
>> >>
>> >>
>> >> And if you have any questions and suggestions do so quickly so I can
>> >> clarify with David.  Please DO NOT post on the JIRA ticket.  I will be
>> >> online for the 12 hours (at least)  I plan to help shepherd this process
>> >> all the way to the end.
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >> [1] https://issues.apache.org/jira/browse/INFRA-5549
>> >>
>> >
>> >
>> >
>> > --
>> > Carlos Rovira
>> > Director de Tecnología
>> > M: +34 607 22 60 05
>> > F:  +34 912 94 80 80
>> > http://www.codeoscopic.com
>> > http://www.directwriter.es
>> > http://www.avant2.es
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Git Migration Reset

[Om]

On Wed, Mar 13, 2013 at 11:05 AM, Erik de Bruin  wrote:

> Carlos,
>
> I have since yesterday moved all my changes to git. They are in total
> 14 commits to my local clone. Do I do a patch or copy for each of
> those commits separately, or is there a way of "exporting" the whole
> set of commits which I then import into the new clone? It would be a
> hassle to have dozens of files that are changed in one long list in
> the new clone and to have to reconstruct my commits one by one...
>
> EdB
>
>
Just check it into SVN.  But do it quickly.  Any commit you made to Git is
invalid now.  Please dont complicate things for yourself anymore.

Thanks,
Om


>
> On Wed, Mar 13, 2013 at 6:59 PM, Carlos Rovira
>  wrote:
> > Hi,
> >
> > it seems svn changes not in GIT are a source of problems for many of us.
> > Only want to let you know that really it's not. All of you with a delta
> set
> > of changes can extract a patch or even copy de structure of files over
> your
> > git clone (maybe more easy). Then you will see the same changes that you
> > had in SVN and you are able to continue working locally.
> >
> > Then when GIT repo has RW open...you can pull to remote.
> >
> > Things are moving now with Davids effort and he will done it from
> scratch,
> > but only want to share this info to let you know that maybe you are
> seeing
> > a problem where there is none.
> >
> > Hope that helps.
> >
> > Best,
> >
> > Carlos
> >
> >
> >
> >
> >
> > 2013/3/13 Om 
> >
> >> In case you are not following the JIRA ticket, Infra has confirmed that
> >> they have opened SVN back up for read/write.  Also, they will be
> starting
> >> the move to Git this evening (GMT -5) again.
> >>
> >> *So, everyone please check-in all your changes into SVN asap.  *Sometime
> >> this evening, SVN will go read-only at which point the migration to Git
> >> will start.
> >>
> >> Here is David@Infra's note regarding this:
> >>
> >> I'll start from scratch this evening. I'll make a list of svn trees and
> >> > start down them one by one, though I'll likely get multiple done in a
> >> > single sitting. Typically it takes 20 minutes to a few dedicated
> hours of
> >> > time per svn tree > git migration.  I'll probably take asjs, external
> and
> >> > falcon tonight. Then the PMC needs to audit, and we can make it RW
> when
> >> > you are satisfied. If we find problems with a given migration, I've
> had
> >> it
> >> > take substantially longer, or be a quick fix, it depends. That said, I
> >> > can't give you a dedicated timeline for all of this - I am doing this
> as
> >> a
> >> > volunteer, and am travelling extensively this week, so I'll try and
> take
> >> > care of it as I have time available.
> >>
> >>
> >>
> >> And if you have any questions and suggestions do so quickly so I can
> >> clarify with David.  Please DO NOT post on the JIRA ticket.  I will be
> >> online for the 12 hours (at least)  I plan to help shepherd this process
> >> all the way to the end.
> >>
> >> Thanks,
> >> Om
> >>
> >> [1] https://issues.apache.org/jira/browse/INFRA-5549
> >>
> >
> >
> >
> > --
> > Carlos Rovira
> > Director de Tecnología
> > M: +34 607 22 60 05
> > F:  +34 912 94 80 80
> > http://www.codeoscopic.com
> > http://www.directwriter.es
> > http://www.avant2.es
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

Re: Git Migration Reset

[Erik de Bruin]

Carlos,

I have since yesterday moved all my changes to git. They are in total
14 commits to my local clone. Do I do a patch or copy for each of
those commits separately, or is there a way of "exporting" the whole
set of commits which I then import into the new clone? It would be a
hassle to have dozens of files that are changed in one long list in
the new clone and to have to reconstruct my commits one by one...

EdB


On Wed, Mar 13, 2013 at 6:59 PM, Carlos Rovira
 wrote:
> Hi,
>
> it seems svn changes not in GIT are a source of problems for many of us.
> Only want to let you know that really it's not. All of you with a delta set
> of changes can extract a patch or even copy de structure of files over your
> git clone (maybe more easy). Then you will see the same changes that you
> had in SVN and you are able to continue working locally.
>
> Then when GIT repo has RW open...you can pull to remote.
>
> Things are moving now with Davids effort and he will done it from scratch,
> but only want to share this info to let you know that maybe you are seeing
> a problem where there is none.
>
> Hope that helps.
>
> Best,
>
> Carlos
>
>
>
>
>
> 2013/3/13 Om 
>
>> In case you are not following the JIRA ticket, Infra has confirmed that
>> they have opened SVN back up for read/write.  Also, they will be starting
>> the move to Git this evening (GMT -5) again.
>>
>> *So, everyone please check-in all your changes into SVN asap.  *Sometime
>> this evening, SVN will go read-only at which point the migration to Git
>> will start.
>>
>> Here is David@Infra's note regarding this:
>>
>> I'll start from scratch this evening. I'll make a list of svn trees and
>> > start down them one by one, though I'll likely get multiple done in a
>> > single sitting. Typically it takes 20 minutes to a few dedicated hours of
>> > time per svn tree > git migration.  I'll probably take asjs, external and
>> > falcon tonight. Then the PMC needs to audit, and we can make it RW when
>> > you are satisfied. If we find problems with a given migration, I've had
>> it
>> > take substantially longer, or be a quick fix, it depends. That said, I
>> > can't give you a dedicated timeline for all of this - I am doing this as
>> a
>> > volunteer, and am travelling extensively this week, so I'll try and take
>> > care of it as I have time available.
>>
>>
>>
>> And if you have any questions and suggestions do so quickly so I can
>> clarify with David.  Please DO NOT post on the JIRA ticket.  I will be
>> online for the 12 hours (at least)  I plan to help shepherd this process
>> all the way to the end.
>>
>> Thanks,
>> Om
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-5549
>>
>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> M: +34 607 22 60 05
> F:  +34 912 94 80 80
> http://www.codeoscopic.com
> http://www.directwriter.es
> http://www.avant2.es



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Git Migration Reset

[Carlos Rovira]

Hi,

it seems svn changes not in GIT are a source of problems for many of us.
Only want to let you know that really it's not. All of you with a delta set
of changes can extract a patch or even copy de structure of files over your
git clone (maybe more easy). Then you will see the same changes that you
had in SVN and you are able to continue working locally.

Then when GIT repo has RW open...you can pull to remote.

Things are moving now with Davids effort and he will done it from scratch,
but only want to share this info to let you know that maybe you are seeing
a problem where there is none.

Hope that helps.

Best,

Carlos





2013/3/13 Om 

> In case you are not following the JIRA ticket, Infra has confirmed that
> they have opened SVN back up for read/write.  Also, they will be starting
> the move to Git this evening (GMT -5) again.
>
> *So, everyone please check-in all your changes into SVN asap.  *Sometime
> this evening, SVN will go read-only at which point the migration to Git
> will start.
>
> Here is David@Infra's note regarding this:
>
> I'll start from scratch this evening. I'll make a list of svn trees and
> > start down them one by one, though I'll likely get multiple done in a
> > single sitting. Typically it takes 20 minutes to a few dedicated hours of
> > time per svn tree > git migration.  I'll probably take asjs, external and
> > falcon tonight. Then the PMC needs to audit, and we can make it RW when
> > you are satisfied. If we find problems with a given migration, I've had
> it
> > take substantially longer, or be a quick fix, it depends. That said, I
> > can't give you a dedicated timeline for all of this - I am doing this as
> a
> > volunteer, and am travelling extensively this week, so I'll try and take
> > care of it as I have time available.
>
>
>
> And if you have any questions and suggestions do so quickly so I can
> clarify with David.  Please DO NOT post on the JIRA ticket.  I will be
> online for the 12 hours (at least)  I plan to help shepherd this process
> all the way to the end.
>
> Thanks,
> Om
>
> [1] https://issues.apache.org/jira/browse/INFRA-5549
>



-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

Re: Git Migration Reset

[Erik de Bruin]

Thank you, Om! Confidence restored... somewhat ;-)

EdB



On Wed, Mar 13, 2013 at 6:40 PM, Om  wrote:
> In case you are not following the JIRA ticket, Infra has confirmed that
> they have opened SVN back up for read/write.  Also, they will be starting
> the move to Git this evening (GMT -5) again.
>
> *So, everyone please check-in all your changes into SVN asap.  *Sometime
> this evening, SVN will go read-only at which point the migration to Git
> will start.
>
> Here is David@Infra's note regarding this:
>
> I'll start from scratch this evening. I'll make a list of svn trees and
>> start down them one by one, though I'll likely get multiple done in a
>> single sitting. Typically it takes 20 minutes to a few dedicated hours of
>> time per svn tree > git migration.  I'll probably take asjs, external and
>> falcon tonight. Then the PMC needs to audit, and we can make it RW when
>> you are satisfied. If we find problems with a given migration, I've had it
>> take substantially longer, or be a quick fix, it depends. That said, I
>> can't give you a dedicated timeline for all of this - I am doing this as a
>> volunteer, and am travelling extensively this week, so I'll try and take
>> care of it as I have time available.
>
>
>
> And if you have any questions and suggestions do so quickly so I can
> clarify with David.  Please DO NOT post on the JIRA ticket.  I will be
> online for the 12 hours (at least)  I plan to help shepherd this process
> all the way to the end.
>
> Thanks,
> Om
>
> [1] https://issues.apache.org/jira/browse/INFRA-5549



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Git Migration Reset

[Om]

In case you are not following the JIRA ticket, Infra has confirmed that
they have opened SVN back up for read/write.  Also, they will be starting
the move to Git this evening (GMT -5) again.

*So, everyone please check-in all your changes into SVN asap.  *Sometime
this evening, SVN will go read-only at which point the migration to Git
will start.

Here is David@Infra's note regarding this:

I'll start from scratch this evening. I'll make a list of svn trees and
> start down them one by one, though I'll likely get multiple done in a
> single sitting. Typically it takes 20 minutes to a few dedicated hours of
> time per svn tree > git migration.  I'll probably take asjs, external and
> falcon tonight. Then the PMC needs to audit, and we can make it RW when
> you are satisfied. If we find problems with a given migration, I've had it
> take substantially longer, or be a quick fix, it depends. That said, I
> can't give you a dedicated timeline for all of this - I am doing this as a
> volunteer, and am travelling extensively this week, so I'll try and take
> care of it as I have time available.



And if you have any questions and suggestions do so quickly so I can
clarify with David.  Please DO NOT post on the JIRA ticket.  I will be
online for the 12 hours (at least)  I plan to help shepherd this process
all the way to the end.

Thanks,
Om

[1] https://issues.apache.org/jira/browse/INFRA-5549

[jira] [Commented] (FLEX-33428) CLONE - mx:Text with htmlText attribute compiled for FTETextField displays no text

[Chuck Mastrandrea (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601390#comment-13601390
 ] 

Chuck Mastrandrea commented on FLEX-33428:
--

This problem was originally reported in FLEX-22589, and it is marked fixed 
there (Confirmed in 4.0.0 (build 13467)), but I don't see the fix in 
FTETextField.composeHTMLText in any of the subsequent Flex releases, and the 
problem still persists in Apache Flex 4.9.1.

I applied a fix as described in the original bug report (see attached file). 
This consists of adding:
textField.clearFlag(FTETextField.FLAG_HTML_TEXT_SET);
when htmlText = null (in composeHTMLText), which also requires opening up 
access to function clearFlag and static property FLAG_HTML_TEXT_SET. This fixes 
the problem from my testing.


> CLONE - mx:Text with htmlText attribute compiled for FTETextField displays no 
> text
> --
>
> Key: FLEX-33428
> URL: https://issues.apache.org/jira/browse/FLEX-33428
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: FTETextField
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Chuck Mastrandrea
>Assignee: Adobe JIRA
> Fix For: Adobe Flex SDK Previous
>
> Attachments: FTETextField.as
>
>
> Steps to reproduce:
> 1. Compile app (bugfile from SDK-15246) with "Use FTE in MX Components" 
> checked in FlashBuilder Compiler Options panel
> 2.
> 3.
>  
>  Actual Results:
>  
> no text is displayed
>  
>  Expected Results:
>  
> text displayed - it should look roughly like it does when the "Use FTE" 
> option isn't being used
>  
>  Workaround (if any):

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLEX-33428) CLONE - mx:Text with htmlText attribute compiled for FTETextField displays no text

[Chuck Mastrandrea (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLEX-33428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chuck Mastrandrea updated FLEX-33428:
-

Attachment: FTETextField.as

> CLONE - mx:Text with htmlText attribute compiled for FTETextField displays no 
> text
> --
>
> Key: FLEX-33428
> URL: https://issues.apache.org/jira/browse/FLEX-33428
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: FTETextField
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Chuck Mastrandrea
>Assignee: Adobe JIRA
> Fix For: Adobe Flex SDK Previous
>
> Attachments: FTETextField.as
>
>
> Steps to reproduce:
> 1. Compile app (bugfile from SDK-15246) with "Use FTE in MX Components" 
> checked in FlashBuilder Compiler Options panel
> 2.
> 3.
>  
>  Actual Results:
>  
> no text is displayed
>  
>  Expected Results:
>  
> text displayed - it should look roughly like it does when the "Use FTE" 
> option isn't being used
>  
>  Workaround (if any):

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FLEX-33428) CLONE - mx:Text with htmlText attribute compiled for FTETextField displays no text

[Chuck Mastrandrea (JIRA)]

Chuck Mastrandrea created FLEX-33428:


 Summary: CLONE - mx:Text with htmlText attribute compiled for 
FTETextField displays no text
 Key: FLEX-33428
 URL: https://issues.apache.org/jira/browse/FLEX-33428
 Project: Apache Flex
  Issue Type: Bug
  Components: Spark: FTETextField
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): All OS Platforms
Language Found: English
Reporter: Chuck Mastrandrea
Assignee: Adobe JIRA
 Fix For: Adobe Flex SDK Previous


Steps to reproduce:
1. Compile app (bugfile from SDK-15246) with "Use FTE in MX Components" checked 
in FlashBuilder Compiler Options panel
2.
3.
 
 Actual Results:
 
no text is displayed
 
 Expected Results:
 
text displayed - it should look roughly like it does when the "Use FTE" option 
isn't being used
 
 Workaround (if any):

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [FalconJS/Jx] error when trying to compile MXML file

[Erik de Bruin]

It is working, but only when using the test runner.

I seem to have some time to figure out what to do to Jx to make MXML
work through MXMLJSC before git will open ;-)

EdB



On Wed, Mar 13, 2013 at 5:26 PM, Alex Harui  wrote:
> IMO, once Git is open, you should check in what you have for MXML even if it
> isn't working, as long as it doesn't break any AS compilation.
>
>
> On 3/13/13 9:16 AM, "Erik de Bruin"  wrote:
>
>> Mike,
>>
>> The file handlers look like a good place to start looking.
>>
>> The test runners are all sharing the 'compile' code, so "my" test
>> runners use the same thing as the AS/JS runners. But I vaguely
>> remember setting up a file handler for MXML when I started, I'll look
>> into it.
>>
>> I'm still going strong on my local code. Right now I have time to work
>> on this, but pretty soon that will diminish a bit to the evening
>> hours, as my regular work demands attention. I'll keep going in my
>> local git clone/branch/repo and trust that whatever happens, the
>> "patch compatibility" between SVN and within git will allow me to get
>> all the code I have prepared into a central/feature/develop branch
>> when all is said and done (or back in the SVN repo, if my fears become
>> reality).
>>
>> EdB
>>
>>
>>
>> On Wed, Mar 13, 2013 at 5:06 PM, Michael Schmalle
>>  wrote:
>>> That means it can find a definition for that reference.
>>>
>>> I assume you are calling the Main file FlexJSTest.mxml?
>>>
>>> If I remember correctly, the compiler might not have an mxml handler added
>>> to its file handlers, this means that mxml file are not getting
>>> parsed(handled) in the compilers dependency search.
>>>
>>> I don't know though, was your test runners testing filenodes or the real
>>> compiler?
>>>
>>> There is a simple answer for this but I just need to know.
>>>
>>> BTW, I'm not doing anything code wise until this migration is at a stable
>>> point.
>>>
>>> Mike
>>>
>>>
>>> Quoting Erik de Bruin :
>>>
 Hi,

 While trying to get the FalconJx mxmlc to compile MXML files (up till
 now I used the test runner for this), I ran into the following error:

 "No externally-visible definition with the name 'FlexJSTest' was found."

 Before I dive into the code (which scares me, there's so much of it
 ;-), I thought I'd ask if anyone has seen this error before and
 remembers how to tweak MXMLJSC to NOT give me this error?

 Thanks,

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl

>>>
>>> --
>>> Michael Schmalle - Teoti Graphix, LLC
>>> http://www.teotigraphix.com
>>> http://blog.teotigraphix.com
>>>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [FalconJS/Jx] error when trying to compile MXML file

[Alex Harui]

IMO, once Git is open, you should check in what you have for MXML even if it
isn't working, as long as it doesn't break any AS compilation.


On 3/13/13 9:16 AM, "Erik de Bruin"  wrote:

> Mike,
> 
> The file handlers look like a good place to start looking.
> 
> The test runners are all sharing the 'compile' code, so "my" test
> runners use the same thing as the AS/JS runners. But I vaguely
> remember setting up a file handler for MXML when I started, I'll look
> into it.
> 
> I'm still going strong on my local code. Right now I have time to work
> on this, but pretty soon that will diminish a bit to the evening
> hours, as my regular work demands attention. I'll keep going in my
> local git clone/branch/repo and trust that whatever happens, the
> "patch compatibility" between SVN and within git will allow me to get
> all the code I have prepared into a central/feature/develop branch
> when all is said and done (or back in the SVN repo, if my fears become
> reality).
> 
> EdB
> 
> 
> 
> On Wed, Mar 13, 2013 at 5:06 PM, Michael Schmalle
>  wrote:
>> That means it can find a definition for that reference.
>> 
>> I assume you are calling the Main file FlexJSTest.mxml?
>> 
>> If I remember correctly, the compiler might not have an mxml handler added
>> to its file handlers, this means that mxml file are not getting
>> parsed(handled) in the compilers dependency search.
>> 
>> I don't know though, was your test runners testing filenodes or the real
>> compiler?
>> 
>> There is a simple answer for this but I just need to know.
>> 
>> BTW, I'm not doing anything code wise until this migration is at a stable
>> point.
>> 
>> Mike
>> 
>> 
>> Quoting Erik de Bruin :
>> 
>>> Hi,
>>> 
>>> While trying to get the FalconJx mxmlc to compile MXML files (up till
>>> now I used the test runner for this), I ran into the following error:
>>> 
>>> "No externally-visible definition with the name 'FlexJSTest' was found."
>>> 
>>> Before I dive into the code (which scares me, there's so much of it
>>> ;-), I thought I'd ask if anyone has seen this error before and
>>> remembers how to tweak MXMLJSC to NOT give me this error?
>>> 
>>> Thanks,
>>> 
>>> EdB
>>> 
>>> 
>>> 
>>> --
>>> Ix Multimedia Software
>>> 
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>> 
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>> 
>> 
>> --
>> Michael Schmalle - Teoti Graphix, LLC
>> http://www.teotigraphix.com
>> http://blog.teotigraphix.com
>> 
> 
> 
> 
> --
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: [FalconJS/Jx] error when trying to compile MXML file

[Alex Harui]

It seems familiar but it has been a while.  If you look at the history of
checkins to compiler.js I added a new project type and some other stuff in
order to pick up MXML compilation units.

On 3/13/13 9:17 AM, "Erik de Bruin"  wrote:

> No, the error is from FalconJx. I just thought you might have seen it
> when setting up FalconJS.
> 
> EdB
> 
> 
> 
> On Wed, Mar 13, 2013 at 5:03 PM, Alex Harui  wrote:
>> Are you saying FalconJS said the same thing?
>> 
>> 
>> On 3/13/13 8:58 AM, "Erik de Bruin"  wrote:
>> 
>>> Hi,
>>> 
>>> While trying to get the FalconJx mxmlc to compile MXML files (up till
>>> now I used the test runner for this), I ran into the following error:
>>> 
>>> "No externally-visible definition with the name 'FlexJSTest' was found."
>>> 
>>> Before I dive into the code (which scares me, there's so much of it
>>> ;-), I thought I'd ask if anyone has seen this error before and
>>> remembers how to tweak MXMLJSC to NOT give me this error?
>>> 
>>> Thanks,
>>> 
>>> EdB
>>> 
>>> 
>>> 
>>> --
>>> Ix Multimedia Software
>>> 
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>> 
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>> 
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 
> 
> 
> 
> --
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: [FalconJS/Jx] error when trying to compile MXML file

[Michael Schmalle]

BTW,

If worse came to worse, haha I would just copy my whole falcon.jx  
directory and paste into onto the newly checked out version when  
everything is stable, screw patches, I like the hammer approach.


Mike


Quoting Erik de Bruin :


Mike,

The file handlers look like a good place to start looking.

The test runners are all sharing the 'compile' code, so "my" test
runners use the same thing as the AS/JS runners. But I vaguely
remember setting up a file handler for MXML when I started, I'll look
into it.

I'm still going strong on my local code. Right now I have time to work
on this, but pretty soon that will diminish a bit to the evening
hours, as my regular work demands attention. I'll keep going in my
local git clone/branch/repo and trust that whatever happens, the
"patch compatibility" between SVN and within git will allow me to get
all the code I have prepared into a central/feature/develop branch
when all is said and done (or back in the SVN repo, if my fears become
reality).

EdB



On Wed, Mar 13, 2013 at 5:06 PM, Michael Schmalle
 wrote:

That means it can find a definition for that reference.

I assume you are calling the Main file FlexJSTest.mxml?

If I remember correctly, the compiler might not have an mxml handler added
to its file handlers, this means that mxml file are not getting
parsed(handled) in the compilers dependency search.

I don't know though, was your test runners testing filenodes or the real
compiler?

There is a simple answer for this but I just need to know.

BTW, I'm not doing anything code wise until this migration is at a stable
point.

Mike


Quoting Erik de Bruin :


Hi,

While trying to get the FalconJx mxmlc to compile MXML files (up till
now I used the test runner for this), I ran into the following error:

"No externally-visible definition with the name 'FlexJSTest' was found."

Before I dive into the code (which scares me, there's so much of it
;-), I thought I'd ask if anyone has seen this error before and
remembers how to tweak MXMLJSC to NOT give me this error?

Thanks,

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl



--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com





--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl



--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com

Re: [FalconJS/Jx] error when trying to compile MXML file

[Erik de Bruin]

No, the error is from FalconJx. I just thought you might have seen it
when setting up FalconJS.

EdB



On Wed, Mar 13, 2013 at 5:03 PM, Alex Harui  wrote:
> Are you saying FalconJS said the same thing?
>
>
> On 3/13/13 8:58 AM, "Erik de Bruin"  wrote:
>
>> Hi,
>>
>> While trying to get the FalconJx mxmlc to compile MXML files (up till
>> now I used the test runner for this), I ran into the following error:
>>
>> "No externally-visible definition with the name 'FlexJSTest' was found."
>>
>> Before I dive into the code (which scares me, there's so much of it
>> ;-), I thought I'd ask if anyone has seen this error before and
>> remembers how to tweak MXMLJSC to NOT give me this error?
>>
>> Thanks,
>>
>> EdB
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [FalconJS/Jx] error when trying to compile MXML file

[Erik de Bruin]

Mike,

The file handlers look like a good place to start looking.

The test runners are all sharing the 'compile' code, so "my" test
runners use the same thing as the AS/JS runners. But I vaguely
remember setting up a file handler for MXML when I started, I'll look
into it.

I'm still going strong on my local code. Right now I have time to work
on this, but pretty soon that will diminish a bit to the evening
hours, as my regular work demands attention. I'll keep going in my
local git clone/branch/repo and trust that whatever happens, the
"patch compatibility" between SVN and within git will allow me to get
all the code I have prepared into a central/feature/develop branch
when all is said and done (or back in the SVN repo, if my fears become
reality).

EdB



On Wed, Mar 13, 2013 at 5:06 PM, Michael Schmalle
 wrote:
> That means it can find a definition for that reference.
>
> I assume you are calling the Main file FlexJSTest.mxml?
>
> If I remember correctly, the compiler might not have an mxml handler added
> to its file handlers, this means that mxml file are not getting
> parsed(handled) in the compilers dependency search.
>
> I don't know though, was your test runners testing filenodes or the real
> compiler?
>
> There is a simple answer for this but I just need to know.
>
> BTW, I'm not doing anything code wise until this migration is at a stable
> point.
>
> Mike
>
>
> Quoting Erik de Bruin :
>
>> Hi,
>>
>> While trying to get the FalconJx mxmlc to compile MXML files (up till
>> now I used the test runner for this), I ran into the following error:
>>
>> "No externally-visible definition with the name 'FlexJSTest' was found."
>>
>> Before I dive into the code (which scares me, there's so much of it
>> ;-), I thought I'd ask if anyone has seen this error before and
>> remembers how to tweak MXMLJSC to NOT give me this error?
>>
>> Thanks,
>>
>> EdB
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>
>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [FalconJS/Jx] error when trying to compile MXML file

[Michael Schmalle]

That means it can find a definition for that reference.

I assume you are calling the Main file FlexJSTest.mxml?

If I remember correctly, the compiler might not have an mxml handler  
added to its file handlers, this means that mxml file are not getting  
parsed(handled) in the compilers dependency search.


I don't know though, was your test runners testing filenodes or the  
real compiler?


There is a simple answer for this but I just need to know.

BTW, I'm not doing anything code wise until this migration is at a  
stable point.


Mike

Quoting Erik de Bruin :


Hi,

While trying to get the FalconJx mxmlc to compile MXML files (up till
now I used the test runner for this), I ran into the following error:

"No externally-visible definition with the name 'FlexJSTest' was found."

Before I dive into the code (which scares me, there's so much of it
;-), I thought I'd ask if anyone has seen this error before and
remembers how to tweak MXMLJSC to NOT give me this error?

Thanks,

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl



--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com

Re: [FalconJS/Jx] error when trying to compile MXML file

[Alex Harui]

Are you saying FalconJS said the same thing?


On 3/13/13 8:58 AM, "Erik de Bruin"  wrote:

> Hi,
> 
> While trying to get the FalconJx mxmlc to compile MXML files (up till
> now I used the test runner for this), I ran into the following error:
> 
> "No externally-visible definition with the name 'FlexJSTest' was found."
> 
> Before I dive into the code (which scares me, there's so much of it
> ;-), I thought I'd ask if anyone has seen this error before and
> remembers how to tweak MXMLJSC to NOT give me this error?
> 
> Thanks,
> 
> EdB
> 
> 
> 
> --
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

[FalconJS/Jx] error when trying to compile MXML file

[Erik de Bruin]

Hi,

While trying to get the FalconJx mxmlc to compile MXML files (up till
now I used the test runner for this), I ran into the following error:

"No externally-visible definition with the name 'FlexJSTest' was found."

Before I dive into the code (which scares me, there's so much of it
;-), I thought I'd ask if anyone has seen this error before and
remembers how to tweak MXMLJSC to NOT give me this error?

Thanks,

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Frédéric THOMAS]

Just for reporting what's happening with the infra for those haven't email 
notifications :


(Al is me; Daniel is David)

"Om et al:

Daniel's making SVN rw again seems reasonable if there are concerns about 
being blocked - especially given the reported problems with the git repos 
already in place. .


Because you have a number of different SVN trees that will be discrete git 
repos what I'll likely do (when we restart this) is to make one tree RO at a 
time, it will slow us down on overall migration but hopefully be less 
disruptive.)


My hope is to have some time this evening (GMT-5) to work on this, but given 
there are problems identified, I can't give you a decent timeline. "


-Fred

-Message d'origine- 
From: Frédéric THOMAS

Sent: Wednesday, March 13, 2013 4:03 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a 
proper job


Anyway, I let you manage with infra if you want as you write a better
english than mine.

-Fred

-Message d'origine- 
From: Frédéric THOMAS

Sent: Wednesday, March 13, 2013 3:55 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a
proper job

Ah yeah, totaly agree with that.
Don't you think David won't considerate my comment after reading yours btw ?

-Fred

-Message d'origine- 
From: Om

Sent: Wednesday, March 13, 2013 3:52 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a
proper job

On Mar 13, 2013 7:46 AM, "Frédéric THOMAS"  wrote:


Hi Om,



Fred, let us coordinate before commenting on the JIRA ticket going

forward.


Sure.

I guess it could go like that:

1- Infra locks svn the time it does a git version
2- Infra unlocks svn to let us commit while reviewing the git version
3- we repeat 1 until git is ok
4- Infra locks svn the time it does the git final git version

That would let us the possibility to continue to work.

What do you think ?

-Fred



The problem is, Infra has not told us that this is their plan.  I would
rather not guess their intentions.  Let's wait for Infra to get back to us
on the ticket before we start checking into SVN.

Thanks,
Om


-Message d'origine- From: Om
Sent: Wednesday, March 13, 2013 3:38 PM

To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a

proper job


On Mar 13, 2013 7:22 AM, "Frédéric THOMAS" 

wrote:



It would be very nice, I'm going to ask that to David right now.

Cheers,
-Fred

-Message d'origine- From: Bertrand Delacretaz
Sent: Wednesday, March 13, 2013 3:16 PM

To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a


proper job



On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
 wrote:



I'm saying that from how it is happening, infra can't make svn writable


(at


least, let us commit) while they are in process of migrating to git.




It's very probably possible for infra to briefly lock svn (if needed),
convert to Git, unlock svn and let you guys look at the Git export to
see if you're happy, while continuing to work in svn.

You can then repeat the process a few times if needed until you're
happy with the Git conversion, and then redo the conversion one last
time for good.

-Bertrand



From Infra's last comment on JIRA, if we continue to work in SVN, those
changes won't be applied to Git.  That is not an useful option for us.

I suggest that we don't check in anything into SVN until we get
clarification from Infra about this.

Fred, let us coordinate before commenting on the JIRA ticket going

forward.


Thanks,
Om

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Frédéric THOMAS]

Anyway, I let you manage with infra if you want as you write a better 
english than mine.


-Fred

-Message d'origine- 
From: Frédéric THOMAS

Sent: Wednesday, March 13, 2013 3:55 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a 
proper job


Ah yeah, totaly agree with that.
Don't you think David won't considerate my comment after reading yours btw ?

-Fred

-Message d'origine- 
From: Om

Sent: Wednesday, March 13, 2013 3:52 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a
proper job

On Mar 13, 2013 7:46 AM, "Frédéric THOMAS"  wrote:


Hi Om,



Fred, let us coordinate before commenting on the JIRA ticket going

forward.


Sure.

I guess it could go like that:

1- Infra locks svn the time it does a git version
2- Infra unlocks svn to let us commit while reviewing the git version
3- we repeat 1 until git is ok
4- Infra locks svn the time it does the git final git version

That would let us the possibility to continue to work.

What do you think ?

-Fred



The problem is, Infra has not told us that this is their plan.  I would
rather not guess their intentions.  Let's wait for Infra to get back to us
on the ticket before we start checking into SVN.

Thanks,
Om


-Message d'origine- From: Om
Sent: Wednesday, March 13, 2013 3:38 PM

To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a

proper job


On Mar 13, 2013 7:22 AM, "Frédéric THOMAS" 

wrote:



It would be very nice, I'm going to ask that to David right now.

Cheers,
-Fred

-Message d'origine- From: Bertrand Delacretaz
Sent: Wednesday, March 13, 2013 3:16 PM

To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a


proper job



On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
 wrote:



I'm saying that from how it is happening, infra can't make svn writable


(at


least, let us commit) while they are in process of migrating to git.




It's very probably possible for infra to briefly lock svn (if needed),
convert to Git, unlock svn and let you guys look at the Git export to
see if you're happy, while continuing to work in svn.

You can then repeat the process a few times if needed until you're
happy with the Git conversion, and then redo the conversion one last
time for good.

-Bertrand



From Infra's last comment on JIRA, if we continue to work in SVN, those
changes won't be applied to Git.  That is not an useful option for us.

I suggest that we don't check in anything into SVN until we get
clarification from Infra about this.

Fred, let us coordinate before commenting on the JIRA ticket going

forward.


Thanks,
Om

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Frédéric THOMAS]

Ah yeah, totaly agree with that.
Don't you think David won't considerate my comment after reading yours btw ?

-Fred

-Message d'origine- 
From: Om

Sent: Wednesday, March 13, 2013 3:52 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a 
proper job


On Mar 13, 2013 7:46 AM, "Frédéric THOMAS"  wrote:


Hi Om,



Fred, let us coordinate before commenting on the JIRA ticket going

forward.


Sure.

I guess it could go like that:

1- Infra locks svn the time it does a git version
2- Infra unlocks svn to let us commit while reviewing the git version
3- we repeat 1 until git is ok
4- Infra locks svn the time it does the git final git version

That would let us the possibility to continue to work.

What do you think ?

-Fred



The problem is, Infra has not told us that this is their plan.  I would
rather not guess their intentions.  Let's wait for Infra to get back to us
on the ticket before we start checking into SVN.

Thanks,
Om


-Message d'origine- From: Om
Sent: Wednesday, March 13, 2013 3:38 PM

To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a

proper job


On Mar 13, 2013 7:22 AM, "Frédéric THOMAS" 

wrote:



It would be very nice, I'm going to ask that to David right now.

Cheers,
-Fred

-Message d'origine- From: Bertrand Delacretaz
Sent: Wednesday, March 13, 2013 3:16 PM

To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a


proper job



On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
 wrote:



I'm saying that from how it is happening, infra can't make svn writable


(at


least, let us commit) while they are in process of migrating to git.




It's very probably possible for infra to briefly lock svn (if needed),
convert to Git, unlock svn and let you guys look at the Git export to
see if you're happy, while continuing to work in svn.

You can then repeat the process a few times if needed until you're
happy with the Git conversion, and then redo the conversion one last
time for good.

-Bertrand



From Infra's last comment on JIRA, if we continue to work in SVN, those
changes won't be applied to Git.  That is not an useful option for us.

I suggest that we don't check in anything into SVN until we get
clarification from Infra about this.

Fred, let us coordinate before commenting on the JIRA ticket going

forward.


Thanks,
Om 

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Om]

On Mar 13, 2013 7:46 AM, "Frédéric THOMAS"  wrote:
>
> Hi Om,
>
>
>> Fred, let us coordinate before commenting on the JIRA ticket going
forward.
>
> Sure.
>
> I guess it could go like that:
>
> 1- Infra locks svn the time it does a git version
> 2- Infra unlocks svn to let us commit while reviewing the git version
> 3- we repeat 1 until git is ok
> 4- Infra locks svn the time it does the git final git version
>
> That would let us the possibility to continue to work.
>
> What do you think ?
>
> -Fred
>

The problem is, Infra has not told us that this is their plan.  I would
rather not guess their intentions.  Let's wait for Infra to get back to us
on the ticket before we start checking into SVN.

Thanks,
Om

> -Message d'origine- From: Om
> Sent: Wednesday, March 13, 2013 3:38 PM
>
> To: dev@flex.apache.org
> Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a
proper job
>
> On Mar 13, 2013 7:22 AM, "Frédéric THOMAS" 
wrote:
>>
>>
>> It would be very nice, I'm going to ask that to David right now.
>>
>> Cheers,
>> -Fred
>>
>> -Message d'origine- From: Bertrand Delacretaz
>> Sent: Wednesday, March 13, 2013 3:16 PM
>>
>> To: dev@flex.apache.org
>> Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a
>
> proper job
>>
>>
>> On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
>>  wrote:
>>>
>>>
>>> I'm saying that from how it is happening, infra can't make svn writable
>
> (at
>>>
>>> least, let us commit) while they are in process of migrating to git.
>>
>>
>>
>> It's very probably possible for infra to briefly lock svn (if needed),
>> convert to Git, unlock svn and let you guys look at the Git export to
>> see if you're happy, while continuing to work in svn.
>>
>> You can then repeat the process a few times if needed until you're
>> happy with the Git conversion, and then redo the conversion one last
>> time for good.
>>
>> -Bertrand
>
>
> From Infra's last comment on JIRA, if we continue to work in SVN, those
> changes won't be applied to Git.  That is not an useful option for us.
>
> I suggest that we don't check in anything into SVN until we get
> clarification from Infra about this.
>
> Fred, let us coordinate before commenting on the JIRA ticket going
forward.
>
> Thanks,
> Om

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Frédéric THOMAS]

Sorry,

4- Infra locks svn definitly and does the final git version


-Message d'origine- 
From: Frédéric THOMAS

Sent: Wednesday, March 13, 2013 3:45 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a 
proper job


Hi Om,

Fred, let us coordinate before commenting on the JIRA ticket going 
forward.

Sure.

I guess it could go like that:

1- Infra locks svn the time it does a git version
2- Infra unlocks svn to let us commit while reviewing the git version
3- we repeat 1 until git is ok
4- Infra locks svn the time it does the git final git version

That would let us the possibility to continue to work.

What do you think ?

-Fred

-Message d'origine- 
From: Om

Sent: Wednesday, March 13, 2013 3:38 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a
proper job

On Mar 13, 2013 7:22 AM, "Frédéric THOMAS"  wrote:


It would be very nice, I'm going to ask that to David right now.

Cheers,
-Fred

-Message d'origine- From: Bertrand Delacretaz
Sent: Wednesday, March 13, 2013 3:16 PM

To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a

proper job


On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
 wrote:


I'm saying that from how it is happening, infra can't make svn writable

(at

least, let us commit) while they are in process of migrating to git.



It's very probably possible for infra to briefly lock svn (if needed),
convert to Git, unlock svn and let you guys look at the Git export to
see if you're happy, while continuing to work in svn.

You can then repeat the process a few times if needed until you're
happy with the Git conversion, and then redo the conversion one last
time for good.

-Bertrand



From Infra's last comment on JIRA, if we continue to work in SVN, those

changes won't be applied to Git.  That is not an useful option for us.

I suggest that we don't check in anything into SVN until we get
clarification from Infra about this.

Fred, let us coordinate before commenting on the JIRA ticket going forward.

Thanks,
Om

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Frédéric THOMAS]

Sorry,

4- Infra locks svn definitly and does the final git version


-Message d'origine- 
From: Frédéric THOMAS

Sent: Wednesday, March 13, 2013 3:45 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a 
proper job


Hi Om,

Fred, let us coordinate before commenting on the JIRA ticket going 
forward.

Sure.

I guess it could go like that:

1- Infra locks svn the time it does a git version
2- Infra unlocks svn to let us commit while reviewing the git version
3- we repeat 1 until git is ok
4- Infra locks svn the time it does the git final git version

That would let us the possibility to continue to work.

What do you think ?

-Fred

-Message d'origine- 
From: Om

Sent: Wednesday, March 13, 2013 3:38 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a
proper job

On Mar 13, 2013 7:22 AM, "Frédéric THOMAS"  wrote:


It would be very nice, I'm going to ask that to David right now.

Cheers,
-Fred

-Message d'origine- From: Bertrand Delacretaz
Sent: Wednesday, March 13, 2013 3:16 PM

To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a

proper job


On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
 wrote:


I'm saying that from how it is happening, infra can't make svn writable

(at

least, let us commit) while they are in process of migrating to git.



It's very probably possible for infra to briefly lock svn (if needed),
convert to Git, unlock svn and let you guys look at the Git export to
see if you're happy, while continuing to work in svn.

You can then repeat the process a few times if needed until you're
happy with the Git conversion, and then redo the conversion one last
time for good.

-Bertrand



From Infra's last comment on JIRA, if we continue to work in SVN, those

changes won't be applied to Git.  That is not an useful option for us.

I suggest that we don't check in anything into SVN until we get
clarification from Infra about this.

Fred, let us coordinate before commenting on the JIRA ticket going forward.

Thanks,
Om

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Frédéric THOMAS]

Hi Om,

Fred, let us coordinate before commenting on the JIRA ticket going 
forward.

Sure.

I guess it could go like that:

1- Infra locks svn the time it does a git version
2- Infra unlocks svn to let us commit while reviewing the git version
3- we repeat 1 until git is ok
4- Infra locks svn the time it does the git final git version

That would let us the possibility to continue to work.

What do you think ?

-Fred

-Message d'origine- 
From: Om

Sent: Wednesday, March 13, 2013 3:38 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a 
proper job


On Mar 13, 2013 7:22 AM, "Frédéric THOMAS"  wrote:


It would be very nice, I'm going to ask that to David right now.

Cheers,
-Fred

-Message d'origine- From: Bertrand Delacretaz
Sent: Wednesday, March 13, 2013 3:16 PM

To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a

proper job


On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
 wrote:


I'm saying that from how it is happening, infra can't make svn writable

(at

least, let us commit) while they are in process of migrating to git.



It's very probably possible for infra to briefly lock svn (if needed),
convert to Git, unlock svn and let you guys look at the Git export to
see if you're happy, while continuing to work in svn.

You can then repeat the process a few times if needed until you're
happy with the Git conversion, and then redo the conversion one last
time for good.

-Bertrand



From Infra's last comment on JIRA, if we continue to work in SVN, those

changes won't be applied to Git.  That is not an useful option for us.

I suggest that we don't check in anything into SVN until we get
clarification from Infra about this.

Fred, let us coordinate before commenting on the JIRA ticket going forward.

Thanks,
Om 

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Om]

On Mar 13, 2013 7:22 AM, "Frédéric THOMAS"  wrote:
>
> It would be very nice, I'm going to ask that to David right now.
>
> Cheers,
> -Fred
>
> -Message d'origine- From: Bertrand Delacretaz
> Sent: Wednesday, March 13, 2013 3:16 PM
>
> To: dev@flex.apache.org
> Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a
proper job
>
> On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
>  wrote:
>>
>> I'm saying that from how it is happening, infra can't make svn writable
(at
>> least, let us commit) while they are in process of migrating to git.
>
>
> It's very probably possible for infra to briefly lock svn (if needed),
> convert to Git, unlock svn and let you guys look at the Git export to
> see if you're happy, while continuing to work in svn.
>
> You can then repeat the process a few times if needed until you're
> happy with the Git conversion, and then redo the conversion one last
> time for good.
>
> -Bertrand

>From Infra's last comment on JIRA, if we continue to work in SVN, those
changes won't be applied to Git.  That is not an useful option for us.

I suggest that we don't check in anything into SVN until we get
clarification from Infra about this.

Fred, let us coordinate before commenting on the JIRA ticket going forward.

Thanks,
Om

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Frédéric THOMAS]

It would be very nice, I'm going to ask that to David right now.

Cheers,
-Fred

-Message d'origine- 
From: Bertrand Delacretaz

Sent: Wednesday, March 13, 2013 3:16 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a 
proper job


On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
 wrote:
I'm saying that from how it is happening, infra can't make svn writable 
(at

least, let us commit) while they are in process of migrating to git.


It's very probably possible for infra to briefly lock svn (if needed),
convert to Git, unlock svn and let you guys look at the Git export to
see if you're happy, while continuing to work in svn.

You can then repeat the process a few times if needed until you're
happy with the Git conversion, and then redo the conversion one last
time for good.

-Bertrand 

Re: SVN to Git migration in progress

[Erik de Bruin]

So I need to prepare patches for the commits that are currently ready
to go in my local repo/branch, which I can apply when all is said and
done and I have (again) cloned a new local copy and got that working?

And just FYI, I didn't START to code anything, I was actually very
close to committing what I had already written, which is why I was so
frustrated in the first place that INFRA (without notification) made
SVN read only...

EdB



On Wed, Mar 13, 2013 at 3:15 PM, Frédéric THOMAS
 wrote:
> I didn't start to code anything knowing we're in the middle of a migration
> process but no worries, normaly, even if they generate another git repo, the
> SHA1 of the git objects gonna be the same, it means, you can do a patch with
> your change and re-apply it later, when git will r/w.
>
>
> -Fred
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 13, 2013 3:03 PM
>
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
> I HAVE been learning git. I have been migrating from SVN to git and
> while ranting on the list I've been "learning on the job". I have git
> all set up and running and all the Falcon projects are 'checked out',
> set up and compiling again. I also moved all my uncommitted changes
> from SVN to git. There are now 8 major and 4 minor 'commits' ready to
> be 'pushed' to whatever branch they are intended to end up on
> (feature?, develop?, release?, master?). This has been a lot of
> work... And now you're telling me that without discussion or even
> notice, INFRA has decided to waste some more of my time by undoing the
> entire effort?
>
> Nice!
>
> EdB
>
>
>
> On Wed, Mar 13, 2013 at 2:49 PM, Frédéric THOMAS
>  wrote:
>>
>> It's not the best workflow I ever seen, for sure but given we're stuck on
>> it, it's better to let it continue 'till the end, it doesn't serve us to
>> slow it down at this point.
>>
>>
>>> Now, to be clear: we now can write to SVN again, and all commits
>>
>>
>> should go to SVN?
>>
>> NO or that's gonna be lost.
>> DON'T DO ANYTHING (learn git in between or watch kitten video).
>>
>>
>> -Fred
>>
>> -Message d'origine- From: Erik de Bruin
>> Sent: Wednesday, March 13, 2013 2:42 PM
>>
>> To: dev@flex.apache.org
>> Subject: Re: SVN to Git migration in progress
>>
>> Well, shouldn't there have been some kind of discussion first, before
>> such a drastic step as this is taken?
>>
>> We just learned from Bertrand that there are no Dictators in
>> Apache.org, but the way INFRA is behaving, it seems like he was wrong.
>>
>> I propose that from now on all major actions wrt. git are discussed on
>> the list first and then decided with either a [VOTE] or [LAZY].
>>
>> Now, to be clear: we now can write to SVN again, and all commits
>> should go to SVN?
>>
>> EdB
>>
>>
>>
>> On Wed, Mar 13, 2013 at 2:33 PM, Frédéric THOMAS
>>  wrote:
>>>
>>>
>>> There're some issues relative to the history of the develop branch of the
>>> flex-sdk git and the master of the utilities git, it can't be resolved
>>> w/o
>>> to do the all process again.
>>>
>>>
>>> -Fred
>>>
>>> -Message d'origine- From: Erik de Bruin
>>> Sent: Wednesday, March 13, 2013 2:27 PM
>>> To: dev@flex.apache.org
>>> Subject: Re: SVN to Git migration in progress
>>>
>>>
>>> Before I totally freak out, please explain to me what just happened?
>>> Why did INFRA abort the migration?
>>>
>>> EdB
>>>
>>>
>>>
>>> On Wed, Mar 13, 2013 at 2:25 PM, Frédéric THOMAS
>>>  wrote:



 Hi Erik,

 Yes, we're going to do the all process again until everything is ok.
 You shouldn't start working on git until this point (we're all locked at
 the
 moment), in between, you can do a patch, that should be easy to re-apply
 against the final version.


 -Fred

 -Message d'origine- From: Erik de Bruin
 Sent: Wednesday, March 13, 2013 2:18 PM
 To: dev@flex.apache.org
 Subject: Re: AW: SVN to Git migration in progress


 What does that mean? I have spent 2 days moving from SVN to git. Right
 now my entrire FlexJS MXML in FalconJx contribution is in git. Does
 this message mean that we go back to SVN? What does that mean for the
 work I already did in git, will I have to do the whole setup over
 again?

 If true, I'll go back to ranting... and no kittens will stop me this
 time!

 EdB



 On Wed, Mar 13, 2013 at 1:34 PM, Frédéric THOMAS
  wrote:
>
>
>
>
> Just an update from the infra [1] :
>
>  Fine, I've made your svn space rw again. That does mean
> we'll
> have to do the "make ro, create git repo, review it, make rw" dance
> from
> the
> start sometime later.
>
> I suppose we can't commit in between ?
>
>  The critical section is that the git repo must receive no
> commits while the PMC audits it. And that's usually accompanied by
> freezing
> svn (except site) to avoid a s

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Bertrand Delacretaz]

On Wed, Mar 13, 2013 at 3:11 PM, Frédéric THOMAS
 wrote:
> I'm saying that from how it is happening, infra can't make svn writable (at
> least, let us commit) while they are in process of migrating to git.

It's very probably possible for infra to briefly lock svn (if needed),
convert to Git, unlock svn and let you guys look at the Git export to
see if you're happy, while continuing to work in svn.

You can then repeat the process a few times if needed until you're
happy with the Git conversion, and then redo the conversion one last
time for good.

-Bertrand

Re: SVN to Git migration in progress

[Frédéric THOMAS]

I didn't start to code anything knowing we're in the middle of a migration 
process but no worries, normaly, even if they generate another git repo, the 
SHA1 of the git objects gonna be the same, it means, you can do a patch with 
your change and re-apply it later, when git will r/w.


-Fred

-Message d'origine- 
From: Erik de Bruin

Sent: Wednesday, March 13, 2013 3:03 PM
To: dev@flex.apache.org
Subject: Re: SVN to Git migration in progress

I HAVE been learning git. I have been migrating from SVN to git and
while ranting on the list I've been "learning on the job". I have git
all set up and running and all the Falcon projects are 'checked out',
set up and compiling again. I also moved all my uncommitted changes
from SVN to git. There are now 8 major and 4 minor 'commits' ready to
be 'pushed' to whatever branch they are intended to end up on
(feature?, develop?, release?, master?). This has been a lot of
work... And now you're telling me that without discussion or even
notice, INFRA has decided to waste some more of my time by undoing the
entire effort?

Nice!

EdB



On Wed, Mar 13, 2013 at 2:49 PM, Frédéric THOMAS
 wrote:

It's not the best workflow I ever seen, for sure but given we're stuck on
it, it's better to let it continue 'till the end, it doesn't serve us to
slow it down at this point.



Now, to be clear: we now can write to SVN again, and all commits


should go to SVN?

NO or that's gonna be lost.
DON'T DO ANYTHING (learn git in between or watch kitten video).


-Fred

-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 2:42 PM

To: dev@flex.apache.org
Subject: Re: SVN to Git migration in progress

Well, shouldn't there have been some kind of discussion first, before
such a drastic step as this is taken?

We just learned from Bertrand that there are no Dictators in
Apache.org, but the way INFRA is behaving, it seems like he was wrong.

I propose that from now on all major actions wrt. git are discussed on
the list first and then decided with either a [VOTE] or [LAZY].

Now, to be clear: we now can write to SVN again, and all commits
should go to SVN?

EdB



On Wed, Mar 13, 2013 at 2:33 PM, Frédéric THOMAS
 wrote:


There're some issues relative to the history of the develop branch of the
flex-sdk git and the master of the utilities git, it can't be resolved 
w/o

to do the all process again.


-Fred

-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 2:27 PM
To: dev@flex.apache.org
Subject: Re: SVN to Git migration in progress


Before I totally freak out, please explain to me what just happened?
Why did INFRA abort the migration?

EdB



On Wed, Mar 13, 2013 at 2:25 PM, Frédéric THOMAS
 wrote:



Hi Erik,

Yes, we're going to do the all process again until everything is ok.
You shouldn't start working on git until this point (we're all locked at
the
moment), in between, you can do a patch, that should be easy to re-apply
against the final version.


-Fred

-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 2:18 PM
To: dev@flex.apache.org
Subject: Re: AW: SVN to Git migration in progress


What does that mean? I have spent 2 days moving from SVN to git. Right
now my entrire FlexJS MXML in FalconJx contribution is in git. Does
this message mean that we go back to SVN? What does that mean for the
work I already did in git, will I have to do the whole setup over
again?

If true, I'll go back to ranting... and no kittens will stop me this
time!

EdB



On Wed, Mar 13, 2013 at 1:34 PM, Frédéric THOMAS
 wrote:




Just an update from the infra [1] :

 Fine, I've made your svn space rw again. That does mean
we'll
have to do the "make ro, create git repo, review it, make rw" dance 
from

the
start sometime later.

I suppose we can't commit in between ?

 The critical section is that the git repo must receive no
commits while the PMC audits it. And that's usually accompanied by
freezing
svn (except site) to avoid a split brain condition. IOW if you commit 
to

svn, git won't have those commits when made writable.

-Fred

[1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070

-Message d'origine- From: christofer.d...@c-ware.de
Sent: Wednesday, March 13, 2013 12:32 PM

To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

Well in our case this would simply could be any committer of the
project.
At
the time of me writing that article Velo was the only person with 
commit

rights to the central repo :-)


Von: Gordon Smith [gosm...@adobe.com]
Gesendet: Dienstag, 12. März 2013 18:32
An: dev@flex.apache.org
Betreff: RE: SVN to Git migration in progress


"What happens here is that you commit to a publically accessible
repository clone on GitHub that only you can commit to and then issue 
a

"Pull Request" to Velo. He can now review your changes and pull these
changes from your private fork at GitHub. If he likes what you did, he
wil

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Frédéric THOMAS]

I'm saying that from how it is happening, infra can't make svn writable (at 
least, let us commit) while they are in process of migrating to git.


-Fred

-Message d'origine- 
From: Erik de Bruin

Sent: Wednesday, March 13, 2013 3:04 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Abandon git migration until INFRA is ready to do a 
proper job


What are you saying? It isn't even possible to back? How can that be?

EdB



On Wed, Mar 13, 2013 at 3:01 PM, Frédéric THOMAS
 wrote:

Not sure, but I guess they can't do it w/o to make svn r/o during the
process.

-Fred

-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 2:53 PM
To: dev@flex.apache.org
Subject: [DISCUSS] Abandon git migration until INFRA is ready to do a 
proper

job


Hi,

Because the git migration has turned into a raging disaster, and INFRA
is now making major decisions without consulting the PMC first (like
the roll back they apparently did this afternoon), I have lost all
faith in their ability to properly handle this migration at this point
in time.

I propose this project abandons the migration before any more damage
is done or delay is caused and that we re-visit this issue when INFRA
indicates that they have ironed out all issues and are ready to fully
support git.

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl 

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Erik de Bruin]

What are you saying? It isn't even possible to back? How can that be?

EdB



On Wed, Mar 13, 2013 at 3:01 PM, Frédéric THOMAS
 wrote:
> Not sure, but I guess they can't do it w/o to make svn r/o during the
> process.
>
> -Fred
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 13, 2013 2:53 PM
> To: dev@flex.apache.org
> Subject: [DISCUSS] Abandon git migration until INFRA is ready to do a proper
> job
>
>
> Hi,
>
> Because the git migration has turned into a raging disaster, and INFRA
> is now making major decisions without consulting the PMC first (like
> the roll back they apparently did this afternoon), I have lost all
> faith in their ability to properly handle this migration at this point
> in time.
>
> I propose this project abandons the migration before any more damage
> is done or delay is caused and that we re-visit this issue when INFRA
> indicates that they have ironed out all issues and are ready to fully
> support git.
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: SVN to Git migration in progress

[Erik de Bruin]

I HAVE been learning git. I have been migrating from SVN to git and
while ranting on the list I've been "learning on the job". I have git
all set up and running and all the Falcon projects are 'checked out',
set up and compiling again. I also moved all my uncommitted changes
from SVN to git. There are now 8 major and 4 minor 'commits' ready to
be 'pushed' to whatever branch they are intended to end up on
(feature?, develop?, release?, master?). This has been a lot of
work... And now you're telling me that without discussion or even
notice, INFRA has decided to waste some more of my time by undoing the
entire effort?

Nice!

EdB



On Wed, Mar 13, 2013 at 2:49 PM, Frédéric THOMAS
 wrote:
> It's not the best workflow I ever seen, for sure but given we're stuck on
> it, it's better to let it continue 'till the end, it doesn't serve us to
> slow it down at this point.
>
>
>> Now, to be clear: we now can write to SVN again, and all commits
>
> should go to SVN?
>
> NO or that's gonna be lost.
> DON'T DO ANYTHING (learn git in between or watch kitten video).
>
>
> -Fred
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 13, 2013 2:42 PM
>
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
> Well, shouldn't there have been some kind of discussion first, before
> such a drastic step as this is taken?
>
> We just learned from Bertrand that there are no Dictators in
> Apache.org, but the way INFRA is behaving, it seems like he was wrong.
>
> I propose that from now on all major actions wrt. git are discussed on
> the list first and then decided with either a [VOTE] or [LAZY].
>
> Now, to be clear: we now can write to SVN again, and all commits
> should go to SVN?
>
> EdB
>
>
>
> On Wed, Mar 13, 2013 at 2:33 PM, Frédéric THOMAS
>  wrote:
>>
>> There're some issues relative to the history of the develop branch of the
>> flex-sdk git and the master of the utilities git, it can't be resolved w/o
>> to do the all process again.
>>
>>
>> -Fred
>>
>> -Message d'origine- From: Erik de Bruin
>> Sent: Wednesday, March 13, 2013 2:27 PM
>> To: dev@flex.apache.org
>> Subject: Re: SVN to Git migration in progress
>>
>>
>> Before I totally freak out, please explain to me what just happened?
>> Why did INFRA abort the migration?
>>
>> EdB
>>
>>
>>
>> On Wed, Mar 13, 2013 at 2:25 PM, Frédéric THOMAS
>>  wrote:
>>>
>>>
>>> Hi Erik,
>>>
>>> Yes, we're going to do the all process again until everything is ok.
>>> You shouldn't start working on git until this point (we're all locked at
>>> the
>>> moment), in between, you can do a patch, that should be easy to re-apply
>>> against the final version.
>>>
>>>
>>> -Fred
>>>
>>> -Message d'origine- From: Erik de Bruin
>>> Sent: Wednesday, March 13, 2013 2:18 PM
>>> To: dev@flex.apache.org
>>> Subject: Re: AW: SVN to Git migration in progress
>>>
>>>
>>> What does that mean? I have spent 2 days moving from SVN to git. Right
>>> now my entrire FlexJS MXML in FalconJx contribution is in git. Does
>>> this message mean that we go back to SVN? What does that mean for the
>>> work I already did in git, will I have to do the whole setup over
>>> again?
>>>
>>> If true, I'll go back to ranting... and no kittens will stop me this
>>> time!
>>>
>>> EdB
>>>
>>>
>>>
>>> On Wed, Mar 13, 2013 at 1:34 PM, Frédéric THOMAS
>>>  wrote:



 Just an update from the infra [1] :

  Fine, I've made your svn space rw again. That does mean
 we'll
 have to do the "make ro, create git repo, review it, make rw" dance from
 the
 start sometime later.

 I suppose we can't commit in between ?

  The critical section is that the git repo must receive no
 commits while the PMC audits it. And that's usually accompanied by
 freezing
 svn (except site) to avoid a split brain condition. IOW if you commit to
 svn, git won't have those commits when made writable.

 -Fred

 [1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070

 -Message d'origine- From: christofer.d...@c-ware.de
 Sent: Wednesday, March 13, 2013 12:32 PM

 To: dev@flex.apache.org
 Subject: AW: SVN to Git migration in progress

 Well in our case this would simply could be any committer of the
 project.
 At
 the time of me writing that article Velo was the only person with commit
 rights to the central repo :-)

 
 Von: Gordon Smith [gosm...@adobe.com]
 Gesendet: Dienstag, 12. März 2013 18:32
 An: dev@flex.apache.org
 Betreff: RE: SVN to Git migration in progress

> "What happens here is that you commit to a publically accessible
> repository clone on GitHub that only you can commit to and then issue a
> "Pull Request" to Velo. He can now review your changes and pull these
> changes from your private fork at GitHub. If he likes what you did, he
> will

Re: [DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Frédéric THOMAS]

Not sure, but I guess they can't do it w/o to make svn r/o during the 
process.


-Fred

-Message d'origine- 
From: Erik de Bruin

Sent: Wednesday, March 13, 2013 2:53 PM
To: dev@flex.apache.org
Subject: [DISCUSS] Abandon git migration until INFRA is ready to do a proper 
job


Hi,

Because the git migration has turned into a raging disaster, and INFRA
is now making major decisions without consulting the PMC first (like
the roll back they apparently did this afternoon), I have lost all
faith in their ability to properly handle this migration at this point
in time.

I propose this project abandons the migration before any more damage
is done or delay is caused and that we re-visit this issue when INFRA
indicates that they have ironed out all issues and are ready to fully
support git.

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl 

[DISCUSS] Abandon git migration until INFRA is ready to do a proper job

[Erik de Bruin]

Hi,

Because the git migration has turned into a raging disaster, and INFRA
is now making major decisions without consulting the PMC first (like
the roll back they apparently did this afternoon), I have lost all
faith in their ability to properly handle this migration at this point
in time.

I propose this project abandons the migration before any more damage
is done or delay is caused and that we re-visit this issue when INFRA
indicates that they have ironed out all issues and are ready to fully
support git.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: SVN to Git migration in progress

[Frédéric THOMAS]

It's not the best workflow I ever seen, for sure but given we're stuck on 
it, it's better to let it continue 'till the end, it doesn't serve us to 
slow it down at this point.



Now, to be clear: we now can write to SVN again, and all commits

should go to SVN?

NO or that's gonna be lost.
DON'T DO ANYTHING (learn git in between or watch kitten video).

-Fred

-Message d'origine- 
From: Erik de Bruin

Sent: Wednesday, March 13, 2013 2:42 PM
To: dev@flex.apache.org
Subject: Re: SVN to Git migration in progress

Well, shouldn't there have been some kind of discussion first, before
such a drastic step as this is taken?

We just learned from Bertrand that there are no Dictators in
Apache.org, but the way INFRA is behaving, it seems like he was wrong.

I propose that from now on all major actions wrt. git are discussed on
the list first and then decided with either a [VOTE] or [LAZY].

Now, to be clear: we now can write to SVN again, and all commits
should go to SVN?

EdB



On Wed, Mar 13, 2013 at 2:33 PM, Frédéric THOMAS
 wrote:

There're some issues relative to the history of the develop branch of the
flex-sdk git and the master of the utilities git, it can't be resolved w/o
to do the all process again.


-Fred

-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 2:27 PM
To: dev@flex.apache.org
Subject: Re: SVN to Git migration in progress


Before I totally freak out, please explain to me what just happened?
Why did INFRA abort the migration?

EdB



On Wed, Mar 13, 2013 at 2:25 PM, Frédéric THOMAS
 wrote:


Hi Erik,

Yes, we're going to do the all process again until everything is ok.
You shouldn't start working on git until this point (we're all locked at
the
moment), in between, you can do a patch, that should be easy to re-apply
against the final version.


-Fred

-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 2:18 PM
To: dev@flex.apache.org
Subject: Re: AW: SVN to Git migration in progress


What does that mean? I have spent 2 days moving from SVN to git. Right
now my entrire FlexJS MXML in FalconJx contribution is in git. Does
this message mean that we go back to SVN? What does that mean for the
work I already did in git, will I have to do the whole setup over
again?

If true, I'll go back to ranting... and no kittens will stop me this 
time!


EdB



On Wed, Mar 13, 2013 at 1:34 PM, Frédéric THOMAS
 wrote:



Just an update from the infra [1] :

 Fine, I've made your svn space rw again. That does mean 
we'll

have to do the "make ro, create git repo, review it, make rw" dance from
the
start sometime later.

I suppose we can't commit in between ?

 The critical section is that the git repo must receive no
commits while the PMC audits it. And that's usually accompanied by
freezing
svn (except site) to avoid a split brain condition. IOW if you commit to
svn, git won't have those commits when made writable.

-Fred

[1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070

-Message d'origine- From: christofer.d...@c-ware.de
Sent: Wednesday, March 13, 2013 12:32 PM

To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

Well in our case this would simply could be any committer of the 
project.

At
the time of me writing that article Velo was the only person with commit
rights to the central repo :-)


Von: Gordon Smith [gosm...@adobe.com]
Gesendet: Dienstag, 12. März 2013 18:32
An: dev@flex.apache.org
Betreff: RE: SVN to Git migration in progress


"What happens here is that you commit to a publically accessible
repository clone on GitHub that only you can commit to and then issue a
"Pull Request" to Velo. He can now review your changes and pull these
changes from your private fork at GitHub. If he likes what you did, he
will
apply your patches to the trunk and you're done."





Who is going to be the Velo for Apache Flex? That person is going to be
very
busy!

- Gordon


-Original Message-
From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Sent: Tuesday, March 12, 2013 9:00 AM
To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

I once wrote up the workflow of contributing to Flexmojos using Git ...
as
the workflow for Flex is now the same, perhaps it explains a little and
helps clear the confusion with git:
https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Dienstag, 12. März 2013 13:08
An: dev@flex.apache.org
Betreff: Re: SVN to Git migration in progress

What advantage is having a local repo to having a local working copy?
It seems to me that all it does is add an extra layer between me and my
co-contributors. I need to 'commit' to my local repo and then 'push' to
get
it out to the world, where before only a 'commit' was needed...

EdB



On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira
 wrote:

Re: SVN to Git migration in progress

[Erik de Bruin]

Well, shouldn't there have been some kind of discussion first, before
such a drastic step as this is taken?

We just learned from Bertrand that there are no Dictators in
Apache.org, but the way INFRA is behaving, it seems like he was wrong.

I propose that from now on all major actions wrt. git are discussed on
the list first and then decided with either a [VOTE] or [LAZY].

Now, to be clear: we now can write to SVN again, and all commits
should go to SVN?

EdB



On Wed, Mar 13, 2013 at 2:33 PM, Frédéric THOMAS
 wrote:
> There're some issues relative to the history of the develop branch of the
> flex-sdk git and the master of the utilities git, it can't be resolved w/o
> to do the all process again.
>
>
> -Fred
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 13, 2013 2:27 PM
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
>
> Before I totally freak out, please explain to me what just happened?
> Why did INFRA abort the migration?
>
> EdB
>
>
>
> On Wed, Mar 13, 2013 at 2:25 PM, Frédéric THOMAS
>  wrote:
>>
>> Hi Erik,
>>
>> Yes, we're going to do the all process again until everything is ok.
>> You shouldn't start working on git until this point (we're all locked at
>> the
>> moment), in between, you can do a patch, that should be easy to re-apply
>> against the final version.
>>
>>
>> -Fred
>>
>> -Message d'origine- From: Erik de Bruin
>> Sent: Wednesday, March 13, 2013 2:18 PM
>> To: dev@flex.apache.org
>> Subject: Re: AW: SVN to Git migration in progress
>>
>>
>> What does that mean? I have spent 2 days moving from SVN to git. Right
>> now my entrire FlexJS MXML in FalconJx contribution is in git. Does
>> this message mean that we go back to SVN? What does that mean for the
>> work I already did in git, will I have to do the whole setup over
>> again?
>>
>> If true, I'll go back to ranting... and no kittens will stop me this time!
>>
>> EdB
>>
>>
>>
>> On Wed, Mar 13, 2013 at 1:34 PM, Frédéric THOMAS
>>  wrote:
>>>
>>>
>>> Just an update from the infra [1] :
>>>
>>>  Fine, I've made your svn space rw again. That does mean we'll
>>> have to do the "make ro, create git repo, review it, make rw" dance from
>>> the
>>> start sometime later.
>>>
>>> I suppose we can't commit in between ?
>>>
>>>  The critical section is that the git repo must receive no
>>> commits while the PMC audits it. And that's usually accompanied by
>>> freezing
>>> svn (except site) to avoid a split brain condition. IOW if you commit to
>>> svn, git won't have those commits when made writable.
>>>
>>> -Fred
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070
>>>
>>> -Message d'origine- From: christofer.d...@c-ware.de
>>> Sent: Wednesday, March 13, 2013 12:32 PM
>>>
>>> To: dev@flex.apache.org
>>> Subject: AW: SVN to Git migration in progress
>>>
>>> Well in our case this would simply could be any committer of the project.
>>> At
>>> the time of me writing that article Velo was the only person with commit
>>> rights to the central repo :-)
>>>
>>> 
>>> Von: Gordon Smith [gosm...@adobe.com]
>>> Gesendet: Dienstag, 12. März 2013 18:32
>>> An: dev@flex.apache.org
>>> Betreff: RE: SVN to Git migration in progress
>>>
 "What happens here is that you commit to a publically accessible
 repository clone on GitHub that only you can commit to and then issue a
 "Pull Request" to Velo. He can now review your changes and pull these
 changes from your private fork at GitHub. If he likes what you did, he
 will
 apply your patches to the trunk and you're done."
>>>
>>>
>>>
>>>
>>> Who is going to be the Velo for Apache Flex? That person is going to be
>>> very
>>> busy!
>>>
>>> - Gordon
>>>
>>>
>>> -Original Message-
>>> From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
>>> Sent: Tuesday, March 12, 2013 9:00 AM
>>> To: dev@flex.apache.org
>>> Subject: AW: SVN to Git migration in progress
>>>
>>> I once wrote up the workflow of contributing to Flexmojos using Git ...
>>> as
>>> the workflow for Flex is now the same, perhaps it explains a little and
>>> helps clear the confusion with git:
>>> https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos
>>>
>>> Chris
>>>
>>> 
>>> Von: Erik de Bruin [e...@ixsoftware.nl]
>>> Gesendet: Dienstag, 12. März 2013 13:08
>>> An: dev@flex.apache.org
>>> Betreff: Re: SVN to Git migration in progress
>>>
>>> What advantage is having a local repo to having a local working copy?
>>> It seems to me that all it does is add an extra layer between me and my
>>> co-contributors. I need to 'commit' to my local repo and then 'push' to
>>> get
>>> it out to the world, where before only a 'commit' was needed...
>>>
>>> EdB
>>>
>>>
>>>
>>> On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira
>>>  wrote:



 commit is like SVN, you are making a commit in your *local* repo.

>>

Re: SVN to Git migration in progress

[Frédéric THOMAS]

There're some issues relative to the history of the develop branch of the 
flex-sdk git and the master of the utilities git, it can't be resolved w/o 
to do the all process again.


-Fred

-Message d'origine- 
From: Erik de Bruin

Sent: Wednesday, March 13, 2013 2:27 PM
To: dev@flex.apache.org
Subject: Re: SVN to Git migration in progress

Before I totally freak out, please explain to me what just happened?
Why did INFRA abort the migration?

EdB



On Wed, Mar 13, 2013 at 2:25 PM, Frédéric THOMAS
 wrote:

Hi Erik,

Yes, we're going to do the all process again until everything is ok.
You shouldn't start working on git until this point (we're all locked at 
the

moment), in between, you can do a patch, that should be easy to re-apply
against the final version.


-Fred

-Message d'origine- From: Erik de Bruin
Sent: Wednesday, March 13, 2013 2:18 PM
To: dev@flex.apache.org
Subject: Re: AW: SVN to Git migration in progress


What does that mean? I have spent 2 days moving from SVN to git. Right
now my entrire FlexJS MXML in FalconJx contribution is in git. Does
this message mean that we go back to SVN? What does that mean for the
work I already did in git, will I have to do the whole setup over
again?

If true, I'll go back to ranting... and no kittens will stop me this time!

EdB



On Wed, Mar 13, 2013 at 1:34 PM, Frédéric THOMAS
 wrote:


Just an update from the infra [1] :

 Fine, I've made your svn space rw again. That does mean we'll
have to do the "make ro, create git repo, review it, make rw" dance from
the
start sometime later.

I suppose we can't commit in between ?

 The critical section is that the git repo must receive no
commits while the PMC audits it. And that's usually accompanied by
freezing
svn (except site) to avoid a split brain condition. IOW if you commit to
svn, git won't have those commits when made writable.

-Fred

[1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070

-Message d'origine- From: christofer.d...@c-ware.de
Sent: Wednesday, March 13, 2013 12:32 PM

To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

Well in our case this would simply could be any committer of the project.
At
the time of me writing that article Velo was the only person with commit
rights to the central repo :-)


Von: Gordon Smith [gosm...@adobe.com]
Gesendet: Dienstag, 12. März 2013 18:32
An: dev@flex.apache.org
Betreff: RE: SVN to Git migration in progress


"What happens here is that you commit to a publically accessible
repository clone on GitHub that only you can commit to and then issue a
"Pull Request" to Velo. He can now review your changes and pull these
changes from your private fork at GitHub. If he likes what you did, he
will
apply your patches to the trunk and you're done."




Who is going to be the Velo for Apache Flex? That person is going to be
very
busy!

- Gordon


-Original Message-
From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Sent: Tuesday, March 12, 2013 9:00 AM
To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

I once wrote up the workflow of contributing to Flexmojos using Git ... 
as

the workflow for Flex is now the same, perhaps it explains a little and
helps clear the confusion with git:
https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Dienstag, 12. März 2013 13:08
An: dev@flex.apache.org
Betreff: Re: SVN to Git migration in progress

What advantage is having a local repo to having a local working copy?
It seems to me that all it does is add an extra layer between me and my
co-contributors. I need to 'commit' to my local repo and then 'push' to
get
it out to the world, where before only a 'commit' was needed...

EdB



On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira
 wrote:



commit is like SVN, you are making a commit in your *local* repo.

When GIT will became RW, you will be able to "push" to the remote repo
sharing your changes.

In Git you have a fully functional local repo, and there's a shared
one remotely while in SVN there's only one remotely...



2013/3/12 Erik de Bruin 


Joao,

Thank you... but that went right over my head. I'm still at the stage
where I'm trying to grok the difference between 'commit' and 'push'...
I'll get there, but I'm so not pleased with (the timing) of this move
that you all get to enjoy my wining about it until I have the
FalconJx stuff - which I had nicely lined up for a SVN commit -
working again in the new git repos I've been forced to make, and my
code is safely 'staged/committed/pushed' for all to enjoy.

EdB



On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
 wrote:
> Eric, If you want to learn the basics behind git you can try
> http://pcottle.github.com/learnGitBranching/ , it helped me.
>
>
> On 12 March 2013 09:14, Erik de Bruin  wrote:
>
>> Are you sure?
>>
>> I

Re: SVN to Git migration in progress

[Erik de Bruin]

Before I totally freak out, please explain to me what just happened?
Why did INFRA abort the migration?

EdB



On Wed, Mar 13, 2013 at 2:25 PM, Frédéric THOMAS
 wrote:
> Hi Erik,
>
> Yes, we're going to do the all process again until everything is ok.
> You shouldn't start working on git until this point (we're all locked at the
> moment), in between, you can do a patch, that should be easy to re-apply
> against the final version.
>
>
> -Fred
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 13, 2013 2:18 PM
> To: dev@flex.apache.org
> Subject: Re: AW: SVN to Git migration in progress
>
>
> What does that mean? I have spent 2 days moving from SVN to git. Right
> now my entrire FlexJS MXML in FalconJx contribution is in git. Does
> this message mean that we go back to SVN? What does that mean for the
> work I already did in git, will I have to do the whole setup over
> again?
>
> If true, I'll go back to ranting... and no kittens will stop me this time!
>
> EdB
>
>
>
> On Wed, Mar 13, 2013 at 1:34 PM, Frédéric THOMAS
>  wrote:
>>
>> Just an update from the infra [1] :
>>
>>  Fine, I've made your svn space rw again. That does mean we'll
>> have to do the "make ro, create git repo, review it, make rw" dance from
>> the
>> start sometime later.
>>
>> I suppose we can't commit in between ?
>>
>>  The critical section is that the git repo must receive no
>> commits while the PMC audits it. And that's usually accompanied by
>> freezing
>> svn (except site) to avoid a split brain condition. IOW if you commit to
>> svn, git won't have those commits when made writable.
>>
>> -Fred
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070
>>
>> -Message d'origine- From: christofer.d...@c-ware.de
>> Sent: Wednesday, March 13, 2013 12:32 PM
>>
>> To: dev@flex.apache.org
>> Subject: AW: SVN to Git migration in progress
>>
>> Well in our case this would simply could be any committer of the project.
>> At
>> the time of me writing that article Velo was the only person with commit
>> rights to the central repo :-)
>>
>> 
>> Von: Gordon Smith [gosm...@adobe.com]
>> Gesendet: Dienstag, 12. März 2013 18:32
>> An: dev@flex.apache.org
>> Betreff: RE: SVN to Git migration in progress
>>
>>> "What happens here is that you commit to a publically accessible
>>> repository clone on GitHub that only you can commit to and then issue a
>>> "Pull Request" to Velo. He can now review your changes and pull these
>>> changes from your private fork at GitHub. If he likes what you did, he
>>> will
>>> apply your patches to the trunk and you're done."
>>
>>
>>
>> Who is going to be the Velo for Apache Flex? That person is going to be
>> very
>> busy!
>>
>> - Gordon
>>
>>
>> -Original Message-
>> From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
>> Sent: Tuesday, March 12, 2013 9:00 AM
>> To: dev@flex.apache.org
>> Subject: AW: SVN to Git migration in progress
>>
>> I once wrote up the workflow of contributing to Flexmojos using Git ... as
>> the workflow for Flex is now the same, perhaps it explains a little and
>> helps clear the confusion with git:
>> https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos
>>
>> Chris
>>
>> 
>> Von: Erik de Bruin [e...@ixsoftware.nl]
>> Gesendet: Dienstag, 12. März 2013 13:08
>> An: dev@flex.apache.org
>> Betreff: Re: SVN to Git migration in progress
>>
>> What advantage is having a local repo to having a local working copy?
>> It seems to me that all it does is add an extra layer between me and my
>> co-contributors. I need to 'commit' to my local repo and then 'push' to
>> get
>> it out to the world, where before only a 'commit' was needed...
>>
>> EdB
>>
>>
>>
>> On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira
>>  wrote:
>>>
>>>
>>> commit is like SVN, you are making a commit in your *local* repo.
>>>
>>> When GIT will became RW, you will be able to "push" to the remote repo
>>> sharing your changes.
>>>
>>> In Git you have a fully functional local repo, and there's a shared
>>> one remotely while in SVN there's only one remotely...
>>>
>>>
>>>
>>> 2013/3/12 Erik de Bruin 
>>>
 Joao,

 Thank you... but that went right over my head. I'm still at the stage
 where I'm trying to grok the difference between 'commit' and 'push'...
 I'll get there, but I'm so not pleased with (the timing) of this move
 that you all get to enjoy my wining about it until I have the
 FalconJx stuff - which I had nicely lined up for a SVN commit -
 working again in the new git repos I've been forced to make, and my
 code is safely 'staged/committed/pushed' for all to enjoy.

 EdB



 On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
  wrote:
 > Eric, If you want to learn the basics behind git you can try
 > http://pcottle.github.com/learnGitBranching/ , it helped me.
 >
 >
 > On

Re: SVN to Git migration in progress

[Frédéric THOMAS]

Hi Erik,

Yes, we're going to do the all process again until everything is ok.
You shouldn't start working on git until this point (we're all locked at the 
moment), in between, you can do a patch, that should be easy to re-apply 
against the final version.


-Fred

-Message d'origine- 
From: Erik de Bruin

Sent: Wednesday, March 13, 2013 2:18 PM
To: dev@flex.apache.org
Subject: Re: AW: SVN to Git migration in progress

What does that mean? I have spent 2 days moving from SVN to git. Right
now my entrire FlexJS MXML in FalconJx contribution is in git. Does
this message mean that we go back to SVN? What does that mean for the
work I already did in git, will I have to do the whole setup over
again?

If true, I'll go back to ranting... and no kittens will stop me this time!

EdB



On Wed, Mar 13, 2013 at 1:34 PM, Frédéric THOMAS
 wrote:

Just an update from the infra [1] :

 Fine, I've made your svn space rw again. That does mean we'll
have to do the "make ro, create git repo, review it, make rw" dance from 
the

start sometime later.

I suppose we can't commit in between ?

 The critical section is that the git repo must receive no
commits while the PMC audits it. And that's usually accompanied by 
freezing

svn (except site) to avoid a split brain condition. IOW if you commit to
svn, git won't have those commits when made writable.

-Fred

[1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070

-Message d'origine- From: christofer.d...@c-ware.de
Sent: Wednesday, March 13, 2013 12:32 PM

To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

Well in our case this would simply could be any committer of the project. 
At

the time of me writing that article Velo was the only person with commit
rights to the central repo :-)


Von: Gordon Smith [gosm...@adobe.com]
Gesendet: Dienstag, 12. März 2013 18:32
An: dev@flex.apache.org
Betreff: RE: SVN to Git migration in progress


"What happens here is that you commit to a publically accessible
repository clone on GitHub that only you can commit to and then issue a
"Pull Request" to Velo. He can now review your changes and pull these
changes from your private fork at GitHub. If he likes what you did, he 
will

apply your patches to the trunk and you're done."



Who is going to be the Velo for Apache Flex? That person is going to be 
very

busy!

- Gordon


-Original Message-
From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Sent: Tuesday, March 12, 2013 9:00 AM
To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

I once wrote up the workflow of contributing to Flexmojos using Git ... as
the workflow for Flex is now the same, perhaps it explains a little and
helps clear the confusion with git:
https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Dienstag, 12. März 2013 13:08
An: dev@flex.apache.org
Betreff: Re: SVN to Git migration in progress

What advantage is having a local repo to having a local working copy?
It seems to me that all it does is add an extra layer between me and my
co-contributors. I need to 'commit' to my local repo and then 'push' to 
get

it out to the world, where before only a 'commit' was needed...

EdB



On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira
 wrote:


commit is like SVN, you are making a commit in your *local* repo.

When GIT will became RW, you will be able to "push" to the remote repo
sharing your changes.

In Git you have a fully functional local repo, and there's a shared
one remotely while in SVN there's only one remotely...



2013/3/12 Erik de Bruin 


Joao,

Thank you... but that went right over my head. I'm still at the stage
where I'm trying to grok the difference between 'commit' and 'push'...
I'll get there, but I'm so not pleased with (the timing) of this move
that you all get to enjoy my wining about it until I have the
FalconJx stuff - which I had nicely lined up for a SVN commit -
working again in the new git repos I've been forced to make, and my
code is safely 'staged/committed/pushed' for all to enjoy.

EdB



On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
 wrote:
> Eric, If you want to learn the basics behind git you can try
> http://pcottle.github.com/learnGitBranching/ , it helped me.
>
>
> On 12 March 2013 09:14, Erik de Bruin  wrote:
>
>> Are you sure?
>>
>> I did a 'git clone' and 'build.properties' shows:
>>
>> # flex-sdk-description values
>> release = Apache Flex 4.9.1
>> release.version = 4.9.1
>>
>> While the develop branch in SVN has:
>>
>> # flex-sdk-description values
>> release = Apache Flex 4.10.0
>> release.version = 4.10.0
>>
>> Oops?
>>
>> EdB
>>
>>
>> On Tue, Mar 12, 2013 at 10:04 AM, Frédéric THOMAS
>>  wrote:
>> > it contains a copy of the develop branch you should do: git
>> > clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git, it
>> >

Re: SVN to Git migration in progress

[Erik de Bruin]

WTF!

EdB


On Wed, Mar 13, 2013 at 2:20 PM, Frédéric THOMAS
 wrote:
>> Huh? Does that mean we're back to square one with the migration?
>
>
> Yep :P
>
> -Fred
>
> -Message d'origine- From: Harbs
> Sent: Wednesday, March 13, 2013 2:15 PM
>
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
> Huh? Does that mean we're back to square one with the migration?
>
> If yes, I'll do a svn checkout. I was waiting until this whole migration
> thing finishes to learn git…
>
> What a mess… ;-)
>
> On Mar 13, 2013, at 2:34 PM, Frédéric THOMAS wrote:
>
>> Just an update from the infra [1] :
>>
>>  Fine, I've made your svn space rw again. That does mean we'll
>> have to do the "make ro, create git repo, review it, make rw" dance from the
>> start sometime later.
>>
>> I suppose we can't commit in between ?
>>
>>  The critical section is that the git repo must receive no
>> commits while the PMC audits it. And that's usually accompanied by freezing
>> svn (except site) to avoid a split brain condition. IOW if you commit to
>> svn, git won't have those commits when made writable.
>>
>> -Fred
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070
>>
>> -Message d'origine- From: christofer.d...@c-ware.de
>> Sent: Wednesday, March 13, 2013 12:32 PM
>> To: dev@flex.apache.org
>> Subject: AW: SVN to Git migration in progress
>>
>> Well in our case this would simply could be any committer of the project.
>> At the time of me writing that article Velo was the only person with commit
>> rights to the central repo :-)
>>
>> 
>> Von: Gordon Smith [gosm...@adobe.com]
>> Gesendet: Dienstag, 12. März 2013 18:32
>> An: dev@flex.apache.org
>> Betreff: RE: SVN to Git migration in progress
>>
>>> "What happens here is that you commit to a publically accessible
>>> repository clone on GitHub that only you can commit to and then issue a
>>> "Pull Request" to Velo. He can now review your changes and pull these
>>> changes from your private fork at GitHub. If he likes what you did, he will
>>> apply your patches to the trunk and you're done."
>>
>>
>> Who is going to be the Velo for Apache Flex? That person is going to be
>> very busy!
>>
>> - Gordon
>>
>>
>> -Original Message-
>> From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
>> Sent: Tuesday, March 12, 2013 9:00 AM
>> To: dev@flex.apache.org
>> Subject: AW: SVN to Git migration in progress
>>
>> I once wrote up the workflow of contributing to Flexmojos using Git ... as
>> the workflow for Flex is now the same, perhaps it explains a little and
>> helps clear the confusion with git:
>> https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos
>>
>> Chris
>>
>> 
>> Von: Erik de Bruin [e...@ixsoftware.nl]
>> Gesendet: Dienstag, 12. März 2013 13:08
>> An: dev@flex.apache.org
>> Betreff: Re: SVN to Git migration in progress
>>
>> What advantage is having a local repo to having a local working copy?
>> It seems to me that all it does is add an extra layer between me and my
>> co-contributors. I need to 'commit' to my local repo and then 'push' to get
>> it out to the world, where before only a 'commit' was needed...
>>
>> EdB
>>
>>
>>
>> On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira
>>  wrote:
>>>
>>> commit is like SVN, you are making a commit in your *local* repo.
>>>
>>> When GIT will became RW, you will be able to "push" to the remote repo
>>> sharing your changes.
>>>
>>> In Git you have a fully functional local repo, and there's a shared
>>> one remotely while in SVN there's only one remotely...
>>>
>>>
>>>
>>> 2013/3/12 Erik de Bruin 
>>>
 Joao,

 Thank you... but that went right over my head. I'm still at the stage
 where I'm trying to grok the difference between 'commit' and 'push'...
 I'll get there, but I'm so not pleased with (the timing) of this move
 that you all get to enjoy my wining about it until I have the
 FalconJx stuff - which I had nicely lined up for a SVN commit -
 working again in the new git repos I've been forced to make, and my
 code is safely 'staged/committed/pushed' for all to enjoy.

 EdB



 On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
  wrote:
 > Eric, If you want to learn the basics behind git you can try
 > http://pcottle.github.com/learnGitBranching/ , it helped me.
 >
 >
 > On 12 March 2013 09:14, Erik de Bruin  wrote:
 >
 >> Are you sure?
 >>
 >> I did a 'git clone' and 'build.properties' shows:
 >>
 >> # flex-sdk-description values
 >> release = Apache Flex 4.9.1
 >> release.version = 4.9.1
 >>
 >> While the develop branch in SVN has:
 >>
 >> # flex-sdk-description values
 >> release = Apache Flex 4.10.0
 >> release.version = 4.10.0
 >>
 >> Oops?
 >>
 >> EdB
 >>
 >>
 >> On Tue, Mar 12, 2013 at 10:04 AM, Fr

Re: SVN to Git migration in progress

[Frédéric THOMAS]

Huh? Does that mean we're back to square one with the migration?


Yep :P

-Fred

-Message d'origine- 
From: Harbs

Sent: Wednesday, March 13, 2013 2:15 PM
To: dev@flex.apache.org
Subject: Re: SVN to Git migration in progress

Huh? Does that mean we're back to square one with the migration?

If yes, I'll do a svn checkout. I was waiting until this whole migration 
thing finishes to learn git…


What a mess… ;-)

On Mar 13, 2013, at 2:34 PM, Frédéric THOMAS wrote:


Just an update from the infra [1] :

 Fine, I've made your svn space rw again. That does mean we'll 
have to do the "make ro, create git repo, review it, make rw" dance from 
the start sometime later.


I suppose we can't commit in between ?

 The critical section is that the git repo must receive no 
commits while the PMC audits it. And that's usually accompanied by 
freezing svn (except site) to avoid a split brain condition. IOW if you 
commit to svn, git won't have those commits when made writable.


-Fred

[1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070

-Message d'origine- From: christofer.d...@c-ware.de
Sent: Wednesday, March 13, 2013 12:32 PM
To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

Well in our case this would simply could be any committer of the project. 
At the time of me writing that article Velo was the only person with 
commit rights to the central repo :-)



Von: Gordon Smith [gosm...@adobe.com]
Gesendet: Dienstag, 12. März 2013 18:32
An: dev@flex.apache.org
Betreff: RE: SVN to Git migration in progress

"What happens here is that you commit to a publically accessible 
repository clone on GitHub that only you can commit to and then issue a 
"Pull Request" to Velo. He can now review your changes and pull these 
changes from your private fork at GitHub. If he likes what you did, he 
will apply your patches to the trunk and you're done."


Who is going to be the Velo for Apache Flex? That person is going to be 
very busy!


- Gordon


-Original Message-
From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Sent: Tuesday, March 12, 2013 9:00 AM
To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

I once wrote up the workflow of contributing to Flexmojos using Git ... as 
the workflow for Flex is now the same, perhaps it explains a little and 
helps clear the confusion with git:

https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Dienstag, 12. März 2013 13:08
An: dev@flex.apache.org
Betreff: Re: SVN to Git migration in progress

What advantage is having a local repo to having a local working copy?
It seems to me that all it does is add an extra layer between me and my 
co-contributors. I need to 'commit' to my local repo and then 'push' to 
get it out to the world, where before only a 'commit' was needed...


EdB



On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira 
 wrote:

commit is like SVN, you are making a commit in your *local* repo.

When GIT will became RW, you will be able to "push" to the remote repo
sharing your changes.

In Git you have a fully functional local repo, and there's a shared
one remotely while in SVN there's only one remotely...



2013/3/12 Erik de Bruin 


Joao,

Thank you... but that went right over my head. I'm still at the stage
where I'm trying to grok the difference between 'commit' and 'push'...
I'll get there, but I'm so not pleased with (the timing) of this move
that you all get to enjoy my wining about it until I have the
FalconJx stuff - which I had nicely lined up for a SVN commit -
working again in the new git repos I've been forced to make, and my
code is safely 'staged/committed/pushed' for all to enjoy.

EdB



On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
 wrote:
> Eric, If you want to learn the basics behind git you can try
> http://pcottle.github.com/learnGitBranching/ , it helped me.
>
>
> On 12 March 2013 09:14, Erik de Bruin  wrote:
>
>> Are you sure?
>>
>> I did a 'git clone' and 'build.properties' shows:
>>
>> # flex-sdk-description values
>> release = Apache Flex 4.9.1
>> release.version = 4.9.1
>>
>> While the develop branch in SVN has:
>>
>> # flex-sdk-description values
>> release = Apache Flex 4.10.0
>> release.version = 4.10.0
>>
>> Oops?
>>
>> EdB
>>
>>
>> On Tue, Mar 12, 2013 at 10:04 AM, Frédéric THOMAS
>>  wrote:
>> > it contains a copy of the develop branch you should do: git
>> > clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git, it
>> > will create
a
>> new
>> > directory called flex-sdk, if you prefer 'develop' append ' 
>> > develop'

to
>> the
>> > clone command
>> >
>> > -Fred
>> >
>> > -Message d'origine- From: Erik de Bruin
>> > Sent: Tuesday, March 12, 2013 9:40 AM
>> >
>> > To: dev@flex.apache.org
>> > Subject: Re: SVN to Git migration in progress
>> >
>> > Just trying to understand w

Re: AW: SVN to Git migration in progress

[Erik de Bruin]

What does that mean? I have spent 2 days moving from SVN to git. Right
now my entrire FlexJS MXML in FalconJx contribution is in git. Does
this message mean that we go back to SVN? What does that mean for the
work I already did in git, will I have to do the whole setup over
again?

If true, I'll go back to ranting... and no kittens will stop me this time!

EdB



On Wed, Mar 13, 2013 at 1:34 PM, Frédéric THOMAS
 wrote:
> Just an update from the infra [1] :
>
>  Fine, I've made your svn space rw again. That does mean we'll
> have to do the "make ro, create git repo, review it, make rw" dance from the
> start sometime later.
>
> I suppose we can't commit in between ?
>
>  The critical section is that the git repo must receive no
> commits while the PMC audits it. And that's usually accompanied by freezing
> svn (except site) to avoid a split brain condition. IOW if you commit to
> svn, git won't have those commits when made writable.
>
> -Fred
>
> [1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070
>
> -Message d'origine- From: christofer.d...@c-ware.de
> Sent: Wednesday, March 13, 2013 12:32 PM
>
> To: dev@flex.apache.org
> Subject: AW: SVN to Git migration in progress
>
> Well in our case this would simply could be any committer of the project. At
> the time of me writing that article Velo was the only person with commit
> rights to the central repo :-)
>
> 
> Von: Gordon Smith [gosm...@adobe.com]
> Gesendet: Dienstag, 12. März 2013 18:32
> An: dev@flex.apache.org
> Betreff: RE: SVN to Git migration in progress
>
>> "What happens here is that you commit to a publically accessible
>> repository clone on GitHub that only you can commit to and then issue a
>> "Pull Request" to Velo. He can now review your changes and pull these
>> changes from your private fork at GitHub. If he likes what you did, he will
>> apply your patches to the trunk and you're done."
>
>
> Who is going to be the Velo for Apache Flex? That person is going to be very
> busy!
>
> - Gordon
>
>
> -Original Message-
> From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
> Sent: Tuesday, March 12, 2013 9:00 AM
> To: dev@flex.apache.org
> Subject: AW: SVN to Git migration in progress
>
> I once wrote up the workflow of contributing to Flexmojos using Git ... as
> the workflow for Flex is now the same, perhaps it explains a little and
> helps clear the confusion with git:
> https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos
>
> Chris
>
> 
> Von: Erik de Bruin [e...@ixsoftware.nl]
> Gesendet: Dienstag, 12. März 2013 13:08
> An: dev@flex.apache.org
> Betreff: Re: SVN to Git migration in progress
>
> What advantage is having a local repo to having a local working copy?
> It seems to me that all it does is add an extra layer between me and my
> co-contributors. I need to 'commit' to my local repo and then 'push' to get
> it out to the world, where before only a 'commit' was needed...
>
> EdB
>
>
>
> On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira
>  wrote:
>>
>> commit is like SVN, you are making a commit in your *local* repo.
>>
>> When GIT will became RW, you will be able to "push" to the remote repo
>> sharing your changes.
>>
>> In Git you have a fully functional local repo, and there's a shared
>> one remotely while in SVN there's only one remotely...
>>
>>
>>
>> 2013/3/12 Erik de Bruin 
>>
>>> Joao,
>>>
>>> Thank you... but that went right over my head. I'm still at the stage
>>> where I'm trying to grok the difference between 'commit' and 'push'...
>>> I'll get there, but I'm so not pleased with (the timing) of this move
>>> that you all get to enjoy my wining about it until I have the
>>> FalconJx stuff - which I had nicely lined up for a SVN commit -
>>> working again in the new git repos I've been forced to make, and my
>>> code is safely 'staged/committed/pushed' for all to enjoy.
>>>
>>> EdB
>>>
>>>
>>>
>>> On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
>>>  wrote:
>>> > Eric, If you want to learn the basics behind git you can try
>>> > http://pcottle.github.com/learnGitBranching/ , it helped me.
>>> >
>>> >
>>> > On 12 March 2013 09:14, Erik de Bruin  wrote:
>>> >
>>> >> Are you sure?
>>> >>
>>> >> I did a 'git clone' and 'build.properties' shows:
>>> >>
>>> >> # flex-sdk-description values
>>> >> release = Apache Flex 4.9.1
>>> >> release.version = 4.9.1
>>> >>
>>> >> While the develop branch in SVN has:
>>> >>
>>> >> # flex-sdk-description values
>>> >> release = Apache Flex 4.10.0
>>> >> release.version = 4.10.0
>>> >>
>>> >> Oops?
>>> >>
>>> >> EdB
>>> >>
>>> >>
>>> >> On Tue, Mar 12, 2013 at 10:04 AM, Frédéric THOMAS
>>> >>  wrote:
>>> >> > it contains a copy of the develop branch you should do: git
>>> >> > clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git, it
>>> >> > will create
>>> a
>>> >> new
>>> >> > directory called flex-sdk, if you prefer 'develop' append ' develo

Re: SVN to Git migration in progress

[Harbs]

Huh? Does that mean we're back to square one with the migration?

If yes, I'll do a svn checkout. I was waiting until this whole migration thing 
finishes to learn git…

What a mess… ;-)

On Mar 13, 2013, at 2:34 PM, Frédéric THOMAS wrote:

> Just an update from the infra [1] :
> 
>  Fine, I've made your svn space rw again. That does mean we'll 
> have to do the "make ro, create git repo, review it, make rw" dance from the 
> start sometime later.
> 
> I suppose we can't commit in between ?
> 
>  The critical section is that the git repo must receive no commits 
> while the PMC audits it. And that's usually accompanied by freezing svn 
> (except site) to avoid a split brain condition. IOW if you commit to svn, git 
> won't have those commits when made writable.
> 
> -Fred
> 
> [1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070
> 
> -Message d'origine- From: christofer.d...@c-ware.de
> Sent: Wednesday, March 13, 2013 12:32 PM
> To: dev@flex.apache.org
> Subject: AW: SVN to Git migration in progress
> 
> Well in our case this would simply could be any committer of the project. At 
> the time of me writing that article Velo was the only person with commit 
> rights to the central repo :-)
> 
> 
> Von: Gordon Smith [gosm...@adobe.com]
> Gesendet: Dienstag, 12. März 2013 18:32
> An: dev@flex.apache.org
> Betreff: RE: SVN to Git migration in progress
> 
>> "What happens here is that you commit to a publically accessible repository 
>> clone on GitHub that only you can commit to and then issue a "Pull Request" 
>> to Velo. He can now review your changes and pull these changes from your 
>> private fork at GitHub. If he likes what you did, he will apply your patches 
>> to the trunk and you're done."
> 
> Who is going to be the Velo for Apache Flex? That person is going to be very 
> busy!
> 
> - Gordon
> 
> 
> -Original Message-
> From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
> Sent: Tuesday, March 12, 2013 9:00 AM
> To: dev@flex.apache.org
> Subject: AW: SVN to Git migration in progress
> 
> I once wrote up the workflow of contributing to Flexmojos using Git ... as 
> the workflow for Flex is now the same, perhaps it explains a little and helps 
> clear the confusion with git:
> https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos
> 
> Chris
> 
> 
> Von: Erik de Bruin [e...@ixsoftware.nl]
> Gesendet: Dienstag, 12. März 2013 13:08
> An: dev@flex.apache.org
> Betreff: Re: SVN to Git migration in progress
> 
> What advantage is having a local repo to having a local working copy?
> It seems to me that all it does is add an extra layer between me and my 
> co-contributors. I need to 'commit' to my local repo and then 'push' to get 
> it out to the world, where before only a 'commit' was needed...
> 
> EdB
> 
> 
> 
> On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira 
>  wrote:
>> commit is like SVN, you are making a commit in your *local* repo.
>> 
>> When GIT will became RW, you will be able to "push" to the remote repo
>> sharing your changes.
>> 
>> In Git you have a fully functional local repo, and there's a shared
>> one remotely while in SVN there's only one remotely...
>> 
>> 
>> 
>> 2013/3/12 Erik de Bruin 
>> 
>>> Joao,
>>> 
>>> Thank you... but that went right over my head. I'm still at the stage
>>> where I'm trying to grok the difference between 'commit' and 'push'...
>>> I'll get there, but I'm so not pleased with (the timing) of this move
>>> that you all get to enjoy my wining about it until I have the
>>> FalconJx stuff - which I had nicely lined up for a SVN commit -
>>> working again in the new git repos I've been forced to make, and my
>>> code is safely 'staged/committed/pushed' for all to enjoy.
>>> 
>>> EdB
>>> 
>>> 
>>> 
>>> On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
>>>  wrote:
>>> > Eric, If you want to learn the basics behind git you can try
>>> > http://pcottle.github.com/learnGitBranching/ , it helped me.
>>> >
>>> >
>>> > On 12 March 2013 09:14, Erik de Bruin  wrote:
>>> >
>>> >> Are you sure?
>>> >>
>>> >> I did a 'git clone' and 'build.properties' shows:
>>> >>
>>> >> # flex-sdk-description values
>>> >> release = Apache Flex 4.9.1
>>> >> release.version = 4.9.1
>>> >>
>>> >> While the develop branch in SVN has:
>>> >>
>>> >> # flex-sdk-description values
>>> >> release = Apache Flex 4.10.0
>>> >> release.version = 4.10.0
>>> >>
>>> >> Oops?
>>> >>
>>> >> EdB
>>> >>
>>> >>
>>> >> On Tue, Mar 12, 2013 at 10:04 AM, Frédéric THOMAS
>>> >>  wrote:
>>> >> > it contains a copy of the develop branch you should do: git
>>> >> > clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git, it
>>> >> > will create
>>> a
>>> >> new
>>> >> > directory called flex-sdk, if you prefer 'develop' append ' develop'
>>> to
>>> >> the
>>> >> > clone command
>>> >> >
>>> >> > -Fred
>>> >> >
>>> >> > -Message d'origine- From: Erik de Bruin
>>> >>

Re: AW: SVN to Git migration in progress

[Frédéric THOMAS]

Just an update from the infra [1] :

 Fine, I've made your svn space rw again. That does mean we'll 
have to do the "make ro, create git repo, review it, make rw" dance from the 
start sometime later.


I suppose we can't commit in between ?

 The critical section is that the git repo must receive no 
commits while the PMC audits it. And that's usually accompanied by freezing 
svn (except site) to avoid a split brain condition. IOW if you commit to 
svn, git won't have those commits when made writable.


-Fred

[1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601070

-Message d'origine- 
From: christofer.d...@c-ware.de

Sent: Wednesday, March 13, 2013 12:32 PM
To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

Well in our case this would simply could be any committer of the project. At 
the time of me writing that article Velo was the only person with commit 
rights to the central repo :-)



Von: Gordon Smith [gosm...@adobe.com]
Gesendet: Dienstag, 12. März 2013 18:32
An: dev@flex.apache.org
Betreff: RE: SVN to Git migration in progress

"What happens here is that you commit to a publically accessible 
repository clone on GitHub that only you can commit to and then issue a 
"Pull Request" to Velo. He can now review your changes and pull these 
changes from your private fork at GitHub. If he likes what you did, he 
will apply your patches to the trunk and you're done."


Who is going to be the Velo for Apache Flex? That person is going to be very 
busy!


- Gordon


-Original Message-
From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Sent: Tuesday, March 12, 2013 9:00 AM
To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

I once wrote up the workflow of contributing to Flexmojos using Git ... as 
the workflow for Flex is now the same, perhaps it explains a little and 
helps clear the confusion with git:

https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Dienstag, 12. März 2013 13:08
An: dev@flex.apache.org
Betreff: Re: SVN to Git migration in progress

What advantage is having a local repo to having a local working copy?
It seems to me that all it does is add an extra layer between me and my 
co-contributors. I need to 'commit' to my local repo and then 'push' to get 
it out to the world, where before only a 'commit' was needed...


EdB



On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira 
 wrote:

commit is like SVN, you are making a commit in your *local* repo.

When GIT will became RW, you will be able to "push" to the remote repo
sharing your changes.

In Git you have a fully functional local repo, and there's a shared
one remotely while in SVN there's only one remotely...



2013/3/12 Erik de Bruin 


Joao,

Thank you... but that went right over my head. I'm still at the stage
where I'm trying to grok the difference between 'commit' and 'push'...
I'll get there, but I'm so not pleased with (the timing) of this move
that you all get to enjoy my wining about it until I have the
FalconJx stuff - which I had nicely lined up for a SVN commit -
working again in the new git repos I've been forced to make, and my
code is safely 'staged/committed/pushed' for all to enjoy.

EdB



On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
 wrote:
> Eric, If you want to learn the basics behind git you can try
> http://pcottle.github.com/learnGitBranching/ , it helped me.
>
>
> On 12 March 2013 09:14, Erik de Bruin  wrote:
>
>> Are you sure?
>>
>> I did a 'git clone' and 'build.properties' shows:
>>
>> # flex-sdk-description values
>> release = Apache Flex 4.9.1
>> release.version = 4.9.1
>>
>> While the develop branch in SVN has:
>>
>> # flex-sdk-description values
>> release = Apache Flex 4.10.0
>> release.version = 4.10.0
>>
>> Oops?
>>
>> EdB
>>
>>
>> On Tue, Mar 12, 2013 at 10:04 AM, Frédéric THOMAS
>>  wrote:
>> > it contains a copy of the develop branch you should do: git
>> > clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git, it
>> > will create
a
>> new
>> > directory called flex-sdk, if you prefer 'develop' append ' develop'
to
>> the
>> > clone command
>> >
>> > -Fred
>> >
>> > -Message d'origine- From: Erik de Bruin
>> > Sent: Tuesday, March 12, 2013 9:40 AM
>> >
>> > To: dev@flex.apache.org
>> > Subject: Re: SVN to Git migration in progress
>> >
>> > Just trying to understand what just happened:
>> >
>> > https://git-wip-us.apache.org/repos/asf/flex-sdk.git
>> >
>> > Does that contain a copy of 'trunk' or of 'branches/develop'?
>> >
>> > EdB
>> >
>> >
>> >
>> > On Tue, Mar 12, 2013 at 9:16 AM, Frédéric THOMAS
>> >  wrote:
>> >>
>> >> I'm currently cloning the repo to see how it has been done...
>> >>
>> >> -Fred
>> >>
>> >> -Message d'origine- From: Justin Mclean
>> >> Sent: Tuesday, March 12, 2013 9:11 AM
>> >>
>> >> To: dev@flex.apache.org
>

AW: SVN to Git migration in progress

[christofer.d...@c-ware.de]

Well in our case this would simply could be any committer of the project. At 
the time of me writing that article Velo was the only person with commit rights 
to the central repo :-)


Von: Gordon Smith [gosm...@adobe.com]
Gesendet: Dienstag, 12. März 2013 18:32
An: dev@flex.apache.org
Betreff: RE: SVN to Git migration in progress

> "What happens here is that you commit to a publically accessible repository 
> clone on GitHub that only you can commit to and then issue a "Pull Request" 
> to Velo. He can now review your changes and pull these changes from your 
> private fork at GitHub. If he likes what you did, he will apply your patches 
> to the trunk and you're done."

Who is going to be the Velo for Apache Flex? That person is going to be very 
busy!

- Gordon


-Original Message-
From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Sent: Tuesday, March 12, 2013 9:00 AM
To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

I once wrote up the workflow of contributing to Flexmojos using Git ... as the 
workflow for Flex is now the same, perhaps it explains a little and helps clear 
the confusion with git:
https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Dienstag, 12. März 2013 13:08
An: dev@flex.apache.org
Betreff: Re: SVN to Git migration in progress

What advantage is having a local repo to having a local working copy?
It seems to me that all it does is add an extra layer between me and my 
co-contributors. I need to 'commit' to my local repo and then 'push' to get it 
out to the world, where before only a 'commit' was needed...

EdB



On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira  
wrote:
> commit is like SVN, you are making a commit in your *local* repo.
>
> When GIT will became RW, you will be able to "push" to the remote repo
> sharing your changes.
>
> In Git you have a fully functional local repo, and there's a shared
> one remotely while in SVN there's only one remotely...
>
>
>
> 2013/3/12 Erik de Bruin 
>
>> Joao,
>>
>> Thank you... but that went right over my head. I'm still at the stage
>> where I'm trying to grok the difference between 'commit' and 'push'...
>> I'll get there, but I'm so not pleased with (the timing) of this move
>> that you all get to enjoy my wining about it until I have the
>> FalconJx stuff - which I had nicely lined up for a SVN commit -
>> working again in the new git repos I've been forced to make, and my
>> code is safely 'staged/committed/pushed' for all to enjoy.
>>
>> EdB
>>
>>
>>
>> On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
>>  wrote:
>> > Eric, If you want to learn the basics behind git you can try
>> > http://pcottle.github.com/learnGitBranching/ , it helped me.
>> >
>> >
>> > On 12 March 2013 09:14, Erik de Bruin  wrote:
>> >
>> >> Are you sure?
>> >>
>> >> I did a 'git clone' and 'build.properties' shows:
>> >>
>> >> # flex-sdk-description values
>> >> release = Apache Flex 4.9.1
>> >> release.version = 4.9.1
>> >>
>> >> While the develop branch in SVN has:
>> >>
>> >> # flex-sdk-description values
>> >> release = Apache Flex 4.10.0
>> >> release.version = 4.10.0
>> >>
>> >> Oops?
>> >>
>> >> EdB
>> >>
>> >>
>> >> On Tue, Mar 12, 2013 at 10:04 AM, Frédéric THOMAS
>> >>  wrote:
>> >> > it contains a copy of the develop branch you should do: git
>> >> > clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git, it
>> >> > will create
>> a
>> >> new
>> >> > directory called flex-sdk, if you prefer 'develop' append ' develop'
>> to
>> >> the
>> >> > clone command
>> >> >
>> >> > -Fred
>> >> >
>> >> > -Message d'origine- From: Erik de Bruin
>> >> > Sent: Tuesday, March 12, 2013 9:40 AM
>> >> >
>> >> > To: dev@flex.apache.org
>> >> > Subject: Re: SVN to Git migration in progress
>> >> >
>> >> > Just trying to understand what just happened:
>> >> >
>> >> > https://git-wip-us.apache.org/repos/asf/flex-sdk.git
>> >> >
>> >> > Does that contain a copy of 'trunk' or of 'branches/develop'?
>> >> >
>> >> > EdB
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Mar 12, 2013 at 9:16 AM, Frédéric THOMAS
>> >> >  wrote:
>> >> >>
>> >> >> I'm currently cloning the repo to see how it has been done...
>> >> >>
>> >> >> -Fred
>> >> >>
>> >> >> -Message d'origine- From: Justin Mclean
>> >> >> Sent: Tuesday, March 12, 2013 9:11 AM
>> >> >>
>> >> >> To: dev@flex.apache.org
>> >> >> Subject: Re: SVN to Git migration in progress
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >>> Hey, textLayout is converted to git too, so a git submodule
>> >> >>> init and
>> >> then
>> >> >>> git submodule update should do the trick, non ?
>> >> >>
>> >> >>
>> >> >> No because we need a subdirectory of the textLayout git repo.
>> >> >>
>> >> >> Justin
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Ix Multimedia Software
>> >> >
>> >> > Jan Luykenstraat 27
>> >> > 3521 VB Utrecht
>> >> >
>>

Re: TLF Issue (was Re: SVN to Git migration in progress)

[Frédéric THOMAS]

BTW, are these separate "repos" as far as Git is concerned or something 
else?)


Humm..Can you reformulate that pls ? :P

The only way I see if we don't want to use links is to use submodules but to 
use TLF as a submodule, it's root should be its sub directory textLayout so 
is that what we want ?


-Fred

-Message d'origine- 
From: Alex Harui

Sent: Tuesday, March 12, 2013 8:11 PM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)

I think we don't want to use hard-links.  And if submodules won't work, then
I think it is time to figure out how to cut releases by grabbing stuff from
different "repos".  (BTW, are these separate "repos" as far as Git is
concerned or something else?)

At Adobe, TLF was developed in Perforce by another team and we took drops
for Flex.  I'm sure we can do something similar.


On 3/12/13 11:37 AM, "Frédéric THOMAS"  wrote:


Submodules in Git are less flexible than svn:externals and less
straightforward to use, you can plug an entire git repo as submodule but
can't plug a sub-directory the a git repo as submodule. The problem with 
TLF

is we need to plug the sub-directory called textLayout to the 3.0.33
directory of our sdk repo, that's make submodules unusable.

One way to go is to clone the TLF repo a part, make a hard link from the
textLayout directory to a new 3.0.33 directory in the sdk repo, gitignore
this directory at the sdk repo level, if we want to work on TLF, we can do
it from the TLF repo itself.

Note:
- I've got this working and I finished to fill the .gitignore file.
- On windows, there's a free software to manage soft/hard link, but it's 
one

thing in more to do to setup the SDK that has to be explain in the readme.

-Fred

-Message d'origine-
From: Alex Harui
Sent: Tuesday, March 12, 2013 6:00 PM
To: dev@flex.apache.org
Subject: TLF Issue (was Re: SVN to Git migration in progress)

Well, I'm still learning about Git, but it looks like we have to resolve 
the
TLF svn:externals issue and it isn't clear that links in the file system 
are

going to work on Windows and are the "correct" solution.

Does anybody actually know the answer?  Or do we just have to figure it 
out

on our own.

One thing I saw on the internet says that you can just pull from the other
project if there aren't any conflicts with file names.  Would that work?

Were submodules and/or subtrees ruled out?  It appeared from the Git 
manual

that an update of the main project doesn't automatically update the
submodules, so that will leave us open to making mistakes staying in sync.

IMO, we should re-think why we had TLF as an svn:external.  I think we 
just
did it so the build scripts wouldn't have to change that much from the 
Adobe

days, so we could find the source where we were used to seeing it.

But looking not to far into the future, our releases may become a
composition of stuff from the various Apache Flex "sub-projects".  For
example, the FlexJS stuff is compositing things from the old Flex SDK, the
Falcon project and the ASJS project.

So, given that we might have sync issues in Git even with submodules, 
maybe

the answer is to rework the release scripts to composite from multiple
projects?

-Alex



On 3/12/13 3:59 AM, "Frédéric THOMAS"  wrote:


Still that :)

I guess on windows I should find a way to to a hard link, right ?

-Fred

-Message d'origine-
From: Justin Mclean
Sent: Tuesday, March 12, 2013 11:26 AM
To: dev@flex.apache.org
Subject: Re: SVN to Git migration in progress

Hi,

Well the good news is other than the flex-sdk git repo compiles a usable
SDK
if you work around the TLF issue.

Justin



--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Finishing the Git migration - Update

[Frédéric THOMAS]

Well I know it's not good already because InstallApacheFlex project goes 
back to the 17/07/2012 (fr date) in svn, I write something on the jira 
ticket [1]


-Fred

[1] https://issues.apache.org/jira/browse/INFRA-5549#comment-13601011

-Message d'origine- 
From: Frédéric THOMAS

Sent: Wednesday, March 13, 2013 10:51 AM
To: dev@flex.apache.org
Subject: Re: Finishing the Git migration - Update

The utilities git history goes back to the 15 aug 2012, someone can confirm
it's good or not  (I can't check by myself as utilities is not my svn root)
?

-Fred

-Message d'origine- 
From: Om

Sent: Wednesday, March 13, 2013 8:04 AM
To: dev@flex.apache.org
Subject: Re: Finishing the Git migration - Update

Utilities:


svn: http://svn.apache.org/viewvc/flex/utilities/
git: https://git-wip-us.apache.org/repos/asf?p=flex-utilities.git




I checked the utilities git repo.   I did a basic ant build and a full
directory diff of trunk and the tags.

Looks good to me.

Om

Re: [Git] Ignore files?

[Bertrand Delacretaz]

On Wed, Mar 13, 2013 at 10:57 AM, Carlos Rovira
 wrote:
> ...all can be done by consensus (mailing list voting) and then people
> executing that consensus will be the pseudo dictators/lieutenants. Someone
> must execute the integration of features, and the final integration

Sure, that will work!
-Bertrand

Re: [Git] Ignore files?

[Carlos Rovira]

Hi Bertrand,

I think all can be done by consensus (mailing list voting) and then people
executing that consensus will be the pseudo dictators/lieutenants. Someone
must execute the integration of features, and the final integration.



2013/3/13 Bertrand Delacretaz 

> On Wed, Mar 13, 2013 at 10:33 AM, Carlos Rovira
>  wrote:
> > ...At the end great projects has a Dictator a then people organizates
> around
> > lieutenants and each suborganization ensures the quality of a module or
> > features. Then the dictator is the person designated to integrate in the
> > final product, and that is what goes in a concrete version
>
> Careful with this, there are no dictators in Apache projects.
>
> At least not permanent ones - it's fine to designate someone as
> release manager for a specific release, and that someone can play the
> integration role that you mention, but decisions *must* occur
> according to the Apache consensus principles (including votes and
> vetos where needed), and you don't want to establish a permanent
> hierarchy.
>
> -Bertrand
>



-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

Re: Finishing the Git migration - Update

[Frédéric THOMAS]

The utilities git history goes back to the 15 aug 2012, someone can confirm 
it's good or not  (I can't check by myself as utilities is not my svn root) 
?


-Fred

-Message d'origine- 
From: Om

Sent: Wednesday, March 13, 2013 8:04 AM
To: dev@flex.apache.org
Subject: Re: Finishing the Git migration - Update

Utilities:


svn: http://svn.apache.org/viewvc/flex/utilities/
git: https://git-wip-us.apache.org/repos/asf?p=flex-utilities.git




I checked the utilities git repo.   I did a basic ant build and a full
directory diff of trunk and the tags.

Looks good to me.

Om 

Re: [Git] Ignore files?

[Bertrand Delacretaz]

On Wed, Mar 13, 2013 at 10:33 AM, Carlos Rovira
 wrote:
> ...At the end great projects has a Dictator a then people organizates around
> lieutenants and each suborganization ensures the quality of a module or
> features. Then the dictator is the person designated to integrate in the
> final product, and that is what goes in a concrete version

Careful with this, there are no dictators in Apache projects.

At least not permanent ones - it's fine to designate someone as
release manager for a specific release, and that someone can play the
integration role that you mention, but decisions *must* occur
according to the Apache consensus principles (including votes and
vetos where needed), and you don't want to establish a permanent
hierarchy.

-Bertrand

Re: [Git] Ignore files?

[Carlos Rovira]

Hi Justin,

now that we are starting in GIT we can't at this point set the future rules
that will work. We should wait some days until people get the basis and
then turn slowly to models that allow us to manage apache flex in a right
way. Apache Flex y so Big so in the future I see submodules (break flex-sdk
in submodules for diferent parts that already have its own relevance, and
impose a dictator-lieutenants workflow (this is has nothing to do with NVIE
that will continue to be use at branch level):

http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows#Dictator-and-Lieutenants-Workflow

In the mean while, we can propose some rules that avoid proliferation un
branches that will become useless. For example, a designated person could
have the task of prune branches as a dictator or moderator based in its own
decision (and people should have this into account).

At the end great projects has a Dictator a then people organizates around
lieutenants and each suborganization ensures the quality of a module or
features. Then the dictator is the person designated to integrate in the
final product, and that is what goes in a concrete version.

But as I said at the beginning, we must first walk before run. People
should take over the git basis a work a bit before such organization.





2013/3/12 Justin Mclean 

> Hi,
>
> > we should only share things with great potential to be merged in develop.
>
> Seems reasonable to me - but it may become a bit of a mess if we are not
> careful.
>
> More questions for the wiki that need an answer:
>
> How do we avoid the big bang integration issues that occur with this
> model? For instance making 4.9 was a huge pain having to merge in all the
> changes that had occurred since 4.8, I would hate to have to do that with
> 20 or 30 branches.
>
> If we have a large number of branches is it the release managers job to
> merge them all or the person who created the branch, what if they are no
> longer about?
>
> How do we prune branches that are no longer actively been worked on?
>
> Thanks,
> Justin




-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

Re: Finishing the Git migration - Update

[Justin Mclean]

Hi,

> You and your fancy commands :-)
When I started using computers a green 80x24 terminal was all you had :-)

>  I did see a couple of mis-matches related to file
> endings, though.  Not sure if MD5 takes that into account.
It should but I didn't see any - a little odd.

Justin

Re: SVN to Git migration in progress

[Erik de Bruin]

Some more links for reference.

The link to the [VOTE] email on using git and branching model:

http://markmail.org/message/2kklqltsdo4643lv

And the link to the [RESULT][VOTE] email:

http://markmail.org/message/ajlskznzec4wqda2

EdB



On Wed, Mar 13, 2013 at 9:29 AM, Erik de Bruin  wrote:
> Yennick,
>
> Thank you! I was already aware of that workflow. In fact, it IS the
> branching model Apache Flex will be using. It was voted in as the
> preferred way to work with git after the switch from SVN.
>
> EdB
>
>
>
> On Wed, Mar 13, 2013 at 8:54 AM, Yennick Trevels
>  wrote:
>> Erik,
>>
>> Here's an example of how a git workflow can look like:
>> http://nvie.com/posts/a-successful-git-branching-model/
>> While this is not necessarily the branching model that the Apache Flex
>> project will use, it should give you a better idea on how git works.
>> Also note that unless you see a "git push" command in that article,
>> everything is done on your local copy of the repository.
>>
>>
>> On Tue, Mar 12, 2013 at 8:41 PM, Erik de Bruin  wrote:
>>
>>> Thank you, I needed kittens!
>>>
>>> EdB
>>>
>>>
>>>
>>> On Tue, Mar 12, 2013 at 8:21 PM, Om  wrote:
>>> > On Tue, Mar 12, 2013 at 12:14 PM, Erik de Bruin 
>>> wrote:
>>> >
>>> >> It does make me feel a little better, all this ranting.
>>> >>
>>> >> And "bite the bullet and move on" is only possible if the people that
>>> >> actually know git actively help out the many active contributors that
>>> >> are complete newbies at it.
>>> >>
>>> >> One of the first things I like to see is an actual step-by-step in the
>>> >> Wiki that lists and explains all the commands we need to use if we
>>> >> want our code to move from our machines to somewhere where it is
>>> >> integrated and available to everyone else. If possible, it also
>>> >> explains where this 'somewhere' is and how you can keep your local
>>> >> code up to date with it (without having to worry you're on a different
>>> >> branch/fork/hub than most other people).
>>> >>
>>> >> Still confused,
>>> >>
>>> >> EdB
>>> >>
>>> >> PS. This will be my last "rant" on this subject, I'll kick the dog if
>>> >> I need to feel better from here on out.
>>> >>
>>> >>
>>> > As you can see, we are working to get all this done.
>>> >
>>> > In the meantime, watch these kittens playing:
>>> > http://www.youtube.com/watch?v=-efQuSlxgWY
>>> >
>>> > This is the best I can do for you now :-)
>>> >
>>> > Om
>>> >
>>> >
>>> >>
>>> >>
>>> >> On Tue, Mar 12, 2013 at 8:03 PM, Alex Harui  wrote:
>>> >> >
>>> >> >
>>> >> >
>>> >> > On 3/12/13 11:11 AM, "Erik de Bruin"  wrote:
>>> >> >
>>> >> >> I still don't see what problem this fixes. And having to work with
>>> >> >> something thats sucks for weeks while you're knee deep into a
>>> >> >> release/contribution is causing problems that weren't there. And more
>>> >> >> importantly: I don't see what this does for the project that needed
>>> to
>>> >> >> be done so desperately that we couldn't get a couple of days advance
>>> >> >> warning so we could at least commit our outstanding changes and
>>> finish
>>> >> >> the release(s) that were in progress?
>>> >> >>
>>> >> > Erik, there is no question that the migration should have been delayed
>>> >> and
>>> >> > better coordinated/communicated.  Normally Infra checks with us before
>>> >> doing
>>> >> > things like this.  Either they forgot or someone besides us gave the
>>> go
>>> >> > ahead.  If it makes you feel better to keep ranting, fine, but I don't
>>> >> think
>>> >> > it will cause us to reverse engines.
>>> >> >
>>> >> > I've never used Git, but everything I've read says it is a better
>>> >> > implementation of SCM.  I don't see complaints about Git like I do
>>> about
>>> >> > SVN.
>>> >> >
>>> >> > --
>>> >> > Alex Harui
>>> >> > Flex SDK Team
>>> >> > Adobe Systems, Inc.
>>> >> > http://blogs.adobe.com/aharui
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Ix Multimedia Software
>>> >>
>>> >> Jan Luykenstraat 27
>>> >> 3521 VB Utrecht
>>> >>
>>> >> T. 06-51952295
>>> >> I. www.ixsoftware.nl
>>> >>
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Finishing the Git migration - Update

[Om]

On Mar 13, 2013 1:23 AM, "Justin Mclean"  wrote:
>
> Hi,
>
> More encouraging is that I've did a MD5 check on every single file in the
Flex SDK SVN repo vs the Flex SDK Git repo (develop branches) and there's
no differences (other than TLF).
>
> Combination of commands:
> find  -exec md5 "{}" \; > MD5svn.txt
> find  -exec md5 "{}" \; > MD5git.txt
> cat MD5svn.txt | grep -v ".*\.svn.*" > MD5modsvn.txt
> cat MD5git.txt | grep -v ".*\.git.*" > MD5modgit.txt
> diff MD5modsvn.txt MD5modgit.txt
>
> Justin
>
>

You and your fancy commands :-)  I just used ExamDiff to do a folder diff
to do the same thing.  I did see a couple of mis-matches related to file
endings, though.  Not sure if MD5 takes that into account.

Om

Re: SVN to Git migration in progress

[Erik de Bruin]

Yennick,

Thank you! I was already aware of that workflow. In fact, it IS the
branching model Apache Flex will be using. It was voted in as the
preferred way to work with git after the switch from SVN.

EdB



On Wed, Mar 13, 2013 at 8:54 AM, Yennick Trevels
 wrote:
> Erik,
>
> Here's an example of how a git workflow can look like:
> http://nvie.com/posts/a-successful-git-branching-model/
> While this is not necessarily the branching model that the Apache Flex
> project will use, it should give you a better idea on how git works.
> Also note that unless you see a "git push" command in that article,
> everything is done on your local copy of the repository.
>
>
> On Tue, Mar 12, 2013 at 8:41 PM, Erik de Bruin  wrote:
>
>> Thank you, I needed kittens!
>>
>> EdB
>>
>>
>>
>> On Tue, Mar 12, 2013 at 8:21 PM, Om  wrote:
>> > On Tue, Mar 12, 2013 at 12:14 PM, Erik de Bruin 
>> wrote:
>> >
>> >> It does make me feel a little better, all this ranting.
>> >>
>> >> And "bite the bullet and move on" is only possible if the people that
>> >> actually know git actively help out the many active contributors that
>> >> are complete newbies at it.
>> >>
>> >> One of the first things I like to see is an actual step-by-step in the
>> >> Wiki that lists and explains all the commands we need to use if we
>> >> want our code to move from our machines to somewhere where it is
>> >> integrated and available to everyone else. If possible, it also
>> >> explains where this 'somewhere' is and how you can keep your local
>> >> code up to date with it (without having to worry you're on a different
>> >> branch/fork/hub than most other people).
>> >>
>> >> Still confused,
>> >>
>> >> EdB
>> >>
>> >> PS. This will be my last "rant" on this subject, I'll kick the dog if
>> >> I need to feel better from here on out.
>> >>
>> >>
>> > As you can see, we are working to get all this done.
>> >
>> > In the meantime, watch these kittens playing:
>> > http://www.youtube.com/watch?v=-efQuSlxgWY
>> >
>> > This is the best I can do for you now :-)
>> >
>> > Om
>> >
>> >
>> >>
>> >>
>> >> On Tue, Mar 12, 2013 at 8:03 PM, Alex Harui  wrote:
>> >> >
>> >> >
>> >> >
>> >> > On 3/12/13 11:11 AM, "Erik de Bruin"  wrote:
>> >> >
>> >> >> I still don't see what problem this fixes. And having to work with
>> >> >> something thats sucks for weeks while you're knee deep into a
>> >> >> release/contribution is causing problems that weren't there. And more
>> >> >> importantly: I don't see what this does for the project that needed
>> to
>> >> >> be done so desperately that we couldn't get a couple of days advance
>> >> >> warning so we could at least commit our outstanding changes and
>> finish
>> >> >> the release(s) that were in progress?
>> >> >>
>> >> > Erik, there is no question that the migration should have been delayed
>> >> and
>> >> > better coordinated/communicated.  Normally Infra checks with us before
>> >> doing
>> >> > things like this.  Either they forgot or someone besides us gave the
>> go
>> >> > ahead.  If it makes you feel better to keep ranting, fine, but I don't
>> >> think
>> >> > it will cause us to reverse engines.
>> >> >
>> >> > I've never used Git, but everything I've read says it is a better
>> >> > implementation of SCM.  I don't see complaints about Git like I do
>> about
>> >> > SVN.
>> >> >
>> >> > --
>> >> > Alex Harui
>> >> > Flex SDK Team
>> >> > Adobe Systems, Inc.
>> >> > http://blogs.adobe.com/aharui
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Ix Multimedia Software
>> >>
>> >> Jan Luykenstraat 27
>> >> 3521 VB Utrecht
>> >>
>> >> T. 06-51952295
>> >> I. www.ixsoftware.nl
>> >>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Finishing the Git migration - Update

[Justin Mclean]

Hi,

More encouraging is that I've did a MD5 check on every single file in the Flex 
SDK SVN repo vs the Flex SDK Git repo (develop branches) and there's no 
differences (other than TLF).

Combination of commands:
find  -exec md5 "{}" \; > MD5svn.txt
find  -exec md5 "{}" \; > MD5git.txt
cat MD5svn.txt | grep -v ".*\.svn.*" > MD5modsvn.txt 
cat MD5git.txt | grep -v ".*\.git.*" > MD5modgit.txt 
diff MD5modsvn.txt MD5modgit.txt

Justin

Re: Finishing the Git migration - Update

[Justin Mclean]

And when I said Eric I mean Erik - sorry about that Erik.

Re: Finishing the Git migration - Update

[Justin Mclean]

Hi,

Thanks to Eric I've seem to found the history of tag and branches issue. [1]

"Obviously, SVN is not Git. During the process of cloning a Git repository from 
the SVN repository, commits for tags and branches can get a bit confused. Each 
project is responsible for providing a list of ref updates that they would like 
to have applied to their repository before accepting it as writable."

So does one of the committers who voted for Git want to prepare this (I'm not 
even sure what they are asking for here):

Updates should be specified in a three column format of:
oldsha newsha ref-name

I'm mostly out of action for the next 2 days (at a conference which I'm 
speaking at) and over the weekend.

Thanks,
Justin

1.https://git-wip-us.apache.org/docs/switching-to-git.html

Re: SVN to Git migration in progress

[Yennick Trevels]

Erik,

Here's an example of how a git workflow can look like:
http://nvie.com/posts/a-successful-git-branching-model/
While this is not necessarily the branching model that the Apache Flex
project will use, it should give you a better idea on how git works.
Also note that unless you see a "git push" command in that article,
everything is done on your local copy of the repository.


On Tue, Mar 12, 2013 at 8:41 PM, Erik de Bruin  wrote:

> Thank you, I needed kittens!
>
> EdB
>
>
>
> On Tue, Mar 12, 2013 at 8:21 PM, Om  wrote:
> > On Tue, Mar 12, 2013 at 12:14 PM, Erik de Bruin 
> wrote:
> >
> >> It does make me feel a little better, all this ranting.
> >>
> >> And "bite the bullet and move on" is only possible if the people that
> >> actually know git actively help out the many active contributors that
> >> are complete newbies at it.
> >>
> >> One of the first things I like to see is an actual step-by-step in the
> >> Wiki that lists and explains all the commands we need to use if we
> >> want our code to move from our machines to somewhere where it is
> >> integrated and available to everyone else. If possible, it also
> >> explains where this 'somewhere' is and how you can keep your local
> >> code up to date with it (without having to worry you're on a different
> >> branch/fork/hub than most other people).
> >>
> >> Still confused,
> >>
> >> EdB
> >>
> >> PS. This will be my last "rant" on this subject, I'll kick the dog if
> >> I need to feel better from here on out.
> >>
> >>
> > As you can see, we are working to get all this done.
> >
> > In the meantime, watch these kittens playing:
> > http://www.youtube.com/watch?v=-efQuSlxgWY
> >
> > This is the best I can do for you now :-)
> >
> > Om
> >
> >
> >>
> >>
> >> On Tue, Mar 12, 2013 at 8:03 PM, Alex Harui  wrote:
> >> >
> >> >
> >> >
> >> > On 3/12/13 11:11 AM, "Erik de Bruin"  wrote:
> >> >
> >> >> I still don't see what problem this fixes. And having to work with
> >> >> something thats sucks for weeks while you're knee deep into a
> >> >> release/contribution is causing problems that weren't there. And more
> >> >> importantly: I don't see what this does for the project that needed
> to
> >> >> be done so desperately that we couldn't get a couple of days advance
> >> >> warning so we could at least commit our outstanding changes and
> finish
> >> >> the release(s) that were in progress?
> >> >>
> >> > Erik, there is no question that the migration should have been delayed
> >> and
> >> > better coordinated/communicated.  Normally Infra checks with us before
> >> doing
> >> > things like this.  Either they forgot or someone besides us gave the
> go
> >> > ahead.  If it makes you feel better to keep ranting, fine, but I don't
> >> think
> >> > it will cause us to reverse engines.
> >> >
> >> > I've never used Git, but everything I've read says it is a better
> >> > implementation of SCM.  I don't see complaints about Git like I do
> about
> >> > SVN.
> >> >
> >> > --
> >> > Alex Harui
> >> > Flex SDK Team
> >> > Adobe Systems, Inc.
> >> > http://blogs.adobe.com/aharui
> >> >
> >>
> >>
> >>
> >> --
> >> Ix Multimedia Software
> >>
> >> Jan Luykenstraat 27
> >> 3521 VB Utrecht
> >>
> >> T. 06-51952295
> >> I. www.ixsoftware.nl
> >>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

Re: Finishing the Git migration - Update

[Om]

On Wed, Mar 13, 2013 at 12:01 AM, Justin Mclean wrote:

> Hi,
>
> I've had a brief look at SDK, TLF and Utilities git hubs. There are some
> issues.
>
> There an issue in how TLF is used by SDK (was a snv:external)  but I don't
> know what we can do about it.
>
> It also seems that the log/history has been dropped on the develop branch
> as it only goes back to 5 Jan.
>

It looks like all on develop, the history before we became a TLP (i.e. when
we were incubating) is gone.  I will add this issue to the JIRA ticket.


>
> The history of the master branch may be missing some info as the log is a
> lot shorter that the released 4.9 tag - that doesn't seem right to me.
>
>
Ha, you forgot the 4.9.1 tag.  This tag's history matches that of the
master.




> Good news is I was able to check out and build a working SDK from git once
> I got around the TLF issue by hand.
>
> Thanks,
> Justin

[Git] committer best practices @ a.o

[Erik de Bruin]

Hi,

Another link I found that might be worthy of discussion by people who
actually understand what it says and how it relates to our chosen
workflow:

https://git-wip-us.apache.org/docs/committer-practices.html

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[Git] commit summary emails

[Erik de Bruin]

Hi,

Just wanted to leave this link here, which mentions that we may need
to take action wrt the commit emails:

https://git-wip-us.apache.org/docs/switching-to-git.html

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Finishing the Git migration - Update

[Erik de Bruin]

I can confirm the following Falcon projects:

- compiler
- compiler.jx
- compiler.jx.tests

That leaves:

- compiler.js
- compiler.tests

for someone who knows a lot more about these projects.

EdB



On Wed, Mar 13, 2013 at 8:04 AM, Om  wrote:
> Utilities:
>
>> svn: http://svn.apache.org/viewvc/flex/utilities/
>> git: https://git-wip-us.apache.org/repos/asf?p=flex-utilities.git
>>
>
>
> I checked the utilities git repo.   I did a basic ant build and a full
> directory diff of trunk and the tags.
>
> Looks good to me.
>
> Om



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Finishing the Git migration - Update

[Justin Mclean]

Hi,

I've had a brief look at SDK, TLF and Utilities git hubs. There are some issues.

There an issue in how TLF is used by SDK (was a snv:external)  but I don't know 
what we can do about it.

It also seems that the log/history has been dropped on the develop branch as it 
only goes back to 5 Jan.

The history of the master branch may be missing some info as the log is a lot 
shorter that the released 4.9 tag - that doesn't seem right to me.

Good news is I was able to check out and build a working SDK from git once I 
got around the TLF issue by hand.

Thanks,
Justin