Re: JIRA issues with SDK that are simple to fix
No. A locked file error. Any work I was doing, was outside the working copy, so nothing should be lost… On Mar 11, 2013, at 9:24 PM, Om wrote: > Is the error something about TLF? If so, there is an easy way to fix it. > That way you wont lose your work. > > And btw, you could also create a patch from your current work, trash > working copy and re-apply it to your new workspace. There is no real > reason to lose work. > > Om > > On Mon, Mar 11, 2013 at 12:19 PM, Harbs wrote: > >> My working copy had errors and refused to update. I trashed the whole >> thing and I'm checking out a fresh copy. I guess nothing is happening here >> until tomorrow… :-( >> >> On Mar 11, 2013, at 9:32 AM, Harbs wrote: >> >>> Thanks. That was helpful. My working copy of the repository is not up to >> date. I'll update later when I get to my office and give it a go. >>> >>> I use Cornerstone for svn. I have no idea how to generate a patch with >> it, but I'll look into that. All my use of svn has been very basic… ;-) >>> >>> Harbs >>> >>> On Mar 11, 2013, at 9:08 AM, Justin Mclean wrote: >>> Hi, > Can you define "patch"? Do you mean just taking the full .as file and >> attaching it, or something else? Patches are files that describe the differences line by line between >> two files. SVN can generate patches via "svn patch" on the command line but >> all SVN tools that I know of have a way of generating patches. For instance >> subclipse it's right click Team - > Generate Patch. Patches can also be generated from a pull request in the ApacheFlex >> Github mirror and be applied to the current SVN mirror. Thanks, Justin >>> >> >>
Re: JIRA issues with SDK that are simple to fix
Is the error something about TLF? If so, there is an easy way to fix it. That way you wont lose your work. And btw, you could also create a patch from your current work, trash working copy and re-apply it to your new workspace. There is no real reason to lose work. Om On Mon, Mar 11, 2013 at 12:19 PM, Harbs wrote: > My working copy had errors and refused to update. I trashed the whole > thing and I'm checking out a fresh copy. I guess nothing is happening here > until tomorrow… :-( > > On Mar 11, 2013, at 9:32 AM, Harbs wrote: > > > Thanks. That was helpful. My working copy of the repository is not up to > date. I'll update later when I get to my office and give it a go. > > > > I use Cornerstone for svn. I have no idea how to generate a patch with > it, but I'll look into that. All my use of svn has been very basic… ;-) > > > > Harbs > > > > On Mar 11, 2013, at 9:08 AM, Justin Mclean wrote: > > > >> Hi, > >> > >>> Can you define "patch"? Do you mean just taking the full .as file and > attaching it, or something else? > >> Patches are files that describe the differences line by line between > two files. SVN can generate patches via "svn patch" on the command line but > all SVN tools that I know of have a way of generating patches. For instance > subclipse it's right click Team - > Generate Patch. > >> > >> Patches can also be generated from a pull request in the ApacheFlex > Github mirror and be applied to the current SVN mirror. > >> > >> Thanks, > >> Justin > > > >
Re: JIRA issues with SDK that are simple to fix
My working copy had errors and refused to update. I trashed the whole thing and I'm checking out a fresh copy. I guess nothing is happening here until tomorrow… :-( On Mar 11, 2013, at 9:32 AM, Harbs wrote: > Thanks. That was helpful. My working copy of the repository is not up to > date. I'll update later when I get to my office and give it a go. > > I use Cornerstone for svn. I have no idea how to generate a patch with it, > but I'll look into that. All my use of svn has been very basic… ;-) > > Harbs > > On Mar 11, 2013, at 9:08 AM, Justin Mclean wrote: > >> Hi, >> >>> Can you define "patch"? Do you mean just taking the full .as file and >>> attaching it, or something else? >> Patches are files that describe the differences line by line between two >> files. SVN can generate patches via "svn patch" on the command line but all >> SVN tools that I know of have a way of generating patches. For instance >> subclipse it's right click Team - > Generate Patch. >> >> Patches can also be generated from a pull request in the ApacheFlex Github >> mirror and be applied to the current SVN mirror. >> >> Thanks, >> Justin >
Re: JIRA issues with SDK that are simple to fix
Check out the "Squashing Bugs" section on our website : http://flex.apache.org/community-getinvolved.html Essentially, you add a patch to the ticket, and we put them in for you (after a review). More (good) patches give you karma and will get you voted in to be a committer. -Nick On Mon, Mar 11, 2013 at 2:47 AM, Harbs wrote: > How would a non-committer work on this? Most of them specify the needed > fix. What's the process for getting those fixes in? > > i.e. https://issues.apache.org/jira/browse/FLEX-29004 > > On Mar 11, 2013, at 5:43 AM, Justin Mclean wrote: > > > Hi, > > > >> I can take a look at them. I didn't troll those "Easy to fix" in hopes > >> that some other community members might take them on, but it's probably > >> best to get them out the door. > > > > Yep I was hoping some of the less active committer or people looking to > be committers would pick them up, but if we want to get a new release out > the door I think they should be fixed, most have been hanging about for a > while. > > > > Thanks, > > Justin > >
Re: JIRA issues with SDK that are simple to fix
Thanks. That was helpful. My working copy of the repository is not up to date. I'll update later when I get to my office and give it a go. I use Cornerstone for svn. I have no idea how to generate a patch with it, but I'll look into that. All my use of svn has been very basic… ;-) Harbs On Mar 11, 2013, at 9:08 AM, Justin Mclean wrote: > Hi, > >> Can you define "patch"? Do you mean just taking the full .as file and >> attaching it, or something else? > Patches are files that describe the differences line by line between two > files. SVN can generate patches via "svn patch" on the command line but all > SVN tools that I know of have a way of generating patches. For instance > subclipse it's right click Team - > Generate Patch. > > Patches can also be generated from a pull request in the ApacheFlex Github > mirror and be applied to the current SVN mirror. > > Thanks, > Justin
Re: JIRA issues with SDK that are simple to fix
Hi, > Can you define "patch"? Do you mean just taking the full .as file and > attaching it, or something else? Patches are files that describe the differences line by line between two files. SVN can generate patches via "svn patch" on the command line but all SVN tools that I know of have a way of generating patches. For instance subclipse it's right click Team - > Generate Patch. Patches can also be generated from a pull request in the ApacheFlex Github mirror and be applied to the current SVN mirror. Thanks, Justin
Re: JIRA issues with SDK that are simple to fix
Can you define "patch"? Do you mean just taking the full .as file and attaching it, or something else? On Mar 11, 2013, at 8:53 AM, Om wrote: > On Sun, Mar 10, 2013 at 11:47 PM, Harbs wrote: > >> How would a non-committer work on this? Most of them specify the needed >> fix. What's the process for getting those fixes in? >> >> i.e. https://issues.apache.org/jira/browse/FLEX-29004 >> >> > Harbs, > > Thanks for offering to help! > > You could make lives easier for committers by generating patches and > attaching them to JIRA. > Also, generating patches would force you to set up your sdk folders, etc. > in the right way. As you start working on more complicated issues that > touch a number of files, the process becomes easier to manage for you. > > And last but not least, if you keep contributing, you will be invited to > become a committer at which point you wont have to worry about this issue > :-) > > Regads, > Om > > > >> On Mar 11, 2013, at 5:43 AM, Justin Mclean wrote: >> >>> Hi, >>> I can take a look at them. I didn't troll those "Easy to fix" in hopes that some other community members might take them on, but it's probably best to get them out the door. >>> >>> Yep I was hoping some of the less active committer or people looking to >> be committers would pick them up, but if we want to get a new release out >> the door I think they should be fixed, most have been hanging about for a >> while. >>> >>> Thanks, >>> Justin >> >>
Re: JIRA issues with SDK that are simple to fix
Hi, > How would a non-committer work on this? Most of them specify the needed fix. > What's the process for getting those fixes in? As Om said supply fixes as patch files is a great help so would confirming or testing out the fixes (manually or by running Mustella tests), feedback on supplied patches is also welcome as they may not always be correct. Thanks, Justin
Re: JIRA issues with SDK that are simple to fix
On Sun, Mar 10, 2013 at 11:47 PM, Harbs wrote: > How would a non-committer work on this? Most of them specify the needed > fix. What's the process for getting those fixes in? > > i.e. https://issues.apache.org/jira/browse/FLEX-29004 > > Harbs, Thanks for offering to help! You could make lives easier for committers by generating patches and attaching them to JIRA. Also, generating patches would force you to set up your sdk folders, etc. in the right way. As you start working on more complicated issues that touch a number of files, the process becomes easier to manage for you. And last but not least, if you keep contributing, you will be invited to become a committer at which point you wont have to worry about this issue :-) Regads, Om > On Mar 11, 2013, at 5:43 AM, Justin Mclean wrote: > > > Hi, > > > >> I can take a look at them. I didn't troll those "Easy to fix" in hopes > >> that some other community members might take them on, but it's probably > >> best to get them out the door. > > > > Yep I was hoping some of the less active committer or people looking to > be committers would pick them up, but if we want to get a new release out > the door I think they should be fixed, most have been hanging about for a > while. > > > > Thanks, > > Justin > >
Re: JIRA issues with SDK that are simple to fix
How would a non-committer work on this? Most of them specify the needed fix. What's the process for getting those fixes in? i.e. https://issues.apache.org/jira/browse/FLEX-29004 On Mar 11, 2013, at 5:43 AM, Justin Mclean wrote: > Hi, > >> I can take a look at them. I didn't troll those "Easy to fix" in hopes >> that some other community members might take them on, but it's probably >> best to get them out the door. > > Yep I was hoping some of the less active committer or people looking to be > committers would pick them up, but if we want to get a new release out the > door I think they should be fixed, most have been hanging about for a while. > > Thanks, > Justin
Re: JIRA issues with SDK that are simple to fix
Hi, > I can take a look at them. I didn't troll those "Easy to fix" in hopes > that some other community members might take them on, but it's probably > best to get them out the door. Yep I was hoping some of the less active committer or people looking to be committers would pick them up, but if we want to get a new release out the door I think they should be fixed, most have been hanging about for a while. Thanks, Justin
Re: JIRA issues with SDK that are simple to fix
I can take a look at them. I didn't troll those "Easy to fix" in hopes that some other community members might take them on, but it's probably best to get them out the door. -Nick On Sun, Mar 10, 2013 at 8:54 PM, Justin Mclean wrote: > Hi, > > We have a fair number of issue that are relatively easy to fix. > https://issues.apache.org/jira/issues/?filter=12322826 > > There are about 16 issues that are currently unassigned. Anyone we wiling > to take any of these on? > > Thanks, > Justin
JIRA issues with SDK that are simple to fix
Hi, We have a fair number of issue that are relatively easy to fix. https://issues.apache.org/jira/issues/?filter=12322826 There are about 16 issues that are currently unassigned. Anyone we wiling to take any of these on? Thanks, Justin
