I just created a feature branch which reverted back to the last change on the 4th and I applied my changes on that (as well as one of Alex’s — his second commit didn’t apply).
I’m using that branch for the meanwhile until this mess is straightened out so I can continue working. Harbs > On May 10, 2018, at 11:49 AM, Piotr Zarzycki <piotrzarzyck...@gmail.com> > wrote: > > +1. > > In my opinion it should be done in the following way. > 1) Refactoring in separate branch > 2) Announce on dev list > 3) Wait until someone look into that - if it passed 48h gentle reminder. - > The time in this project is rather longer in case of changes. > > Btw. I know couple of projects which forked Flex SDK and guys change it for > the project purpose. If you really wanted to have it totally separated you > can have your own SDK. - It's a pain, but you can move forward faster > instead of waiting or discuss with others on something. > > I really wanted to use Jewel for the new project as part of > Transpiledactionscript and this what is happening do not help. I'm not > talking about code changes, but rather time spent on that after those > changes. > > Piotr > > On Thu, May 10, 2018, 10:35 AM Harbs <harbs.li...@gmail.com> wrote: > >> Let me just say that I’m *very* frustrated right now. >> >> I’m busy chasing down all kinds of odd issues caused by a refactoring that >> we didn’t agree on. >> >> I really don’t have the time to be doing so right now… :-( >> >> Carlos, you REALLY should have: >> a) properly discussed this all *before* you made these changes. >> b) done this on a feature branch. >> >> At this point, I’d like to just revert all the refactoring changes. >> >> Harbs >> >>> On May 10, 2018, at 9:08 AM, Piotr Zarzycki <piotrzarzyck...@gmail.com> >> wrote: >>> >>> In that point I'm feeling that Even if couple of PMC members or >> committers >>> have some resistance, changes are being done no matter what. >> >>
