Re: [FalconJX] Is it time to delete the FalconJS code?

I will probably just tag the repo unless someone speaks up really wanting a branch. -Alex On 1/11/16, 1:45 PM, "Andy Dufilie" wrote: >Setting a tag seems like the best way. > >git tag mytagname >git push origin mytagname > >then do whatever you want. > >On Mon, Jan 11,

Re: [FalconJX] Is it time to delete the FalconJS code?

Setting a tag seems like the best way. git tag mytagname git push origin mytagname then do whatever you want. On Mon, Jan 11, 2016 at 4:10 PM, OmPrakash Muppirala wrote: > Maybe this will work (based on this stackoverflow answer [1]) > > 1. Move the code to its own

Re: [FalconJX] Is it time to delete the FalconJS code?

Can't you just create a tag like "Last know existence of FalconJS" commit then delete. Or were other people saying they still wanted to code somewhere, seems to me that was some of the conversation. Mike On Mon, Jan 11, 2016 at 4:02 PM, Alex Harui wrote: > Does anybody have

Re: [FalconJX] Is it time to delete the FalconJS code?

Does anybody have an actual set of steps to create some sort of archival branch or can I just delete this project? -Alex On 12/21/15, 7:50 AM, "Michael Schmalle" wrote: >Well garbage is relative. I didn't mean it in a derogatory way, only that >the original authors

Re: [FalconJX] Is it time to delete the FalconJS code?

Maybe this will work (based on this stackoverflow answer [1]) 1. Move the code to its own branch. 2. Then tag the branch: git tag archive/ 3. Then delete the branch git branch -d To restore the branch: git checkout -b archive/

RE: [FalconJX] Is it time to delete the FalconJS code?

Might as well make an archive folder that's generic and we can put anything else we want to keep but don't want in the main source areas. -Mark

AW: [FalconJX] Is it time to delete the FalconJS code?

+1 I think I lost track how often, during my maven-deploy efforts I processed that stuff and was a little frustrated after finding out it's actually not used. I would generally suggest to move dead and experimental code to some place you don't confuse it with real parts of Falcon or FlexJS

Re: [FalconJX] Is it time to delete the FalconJS code?

+1 that kind of code makes people confused (so it did for me in the past). So better delete it and if someone needs he/she can download from the history 2015-12-21 10:22 GMT+01:00 Christofer Dutz : > +1 > > I think I lost track how often, during my maven-deploy

Re: [FalconJX] Is it time to delete the FalconJS code?

I would suggest putting it in a branch called falconjs_archive (or something like that to make it clear that it’s archived code) and removing it from develop branch. That way if there’s ever any reason to use code from there, it should be easy to pull it in. On Dec 21, 2015, at 10:26 AM, Alex

[FalconJX] Is it time to delete the FalconJS code?

Hi, It has been a long time since I've looked at the FalconJS code that was donated by Adobe. The FalconJX code seems to be working fine. The FalconJS code seems to be confusing some people who are trying to help find bugs in FalconJX, so I think it might be time to just delete the whole

Re: [FalconJX] Is it time to delete the FalconJS code?

Yup, I agree, it doesn't really need to be deleted but it needs to be so far away from FalconJX that a common dev wouldn't mistake it for anything other than archived history. The code is garbage, another reason why FalconJX even exists, I hated that code with a passion. :) Mike On Mon, Dec 21,

Re: [FalconJX] Is it time to delete the FalconJS code?

Well garbage is relative. I didn't mean it in a derogatory way, only that the original authors were the ones that could understand it. As far as FlaconJX, I wrote that as a prototype based off of my prior experience with AST traversing and the visitor pattern. That was almost 3 years ago now so

Re: [FalconJX] Is it time to delete the FalconJS code?

@Harbs, I don't know enough about Git and branching to know if this is the right way to "archive" stuff before deleting, but I would think that branch would need special handling after it is created because any attempt to merge with that branch might result in the deletion of that code. @Mark &