Things should build now. Charts will not work yet, but MDL example (at
least one) now runs for me.
‹peter
On 3/24/17, 2:58 AM, "Christofer Dutz" wrote:
>Hi Guys,
>
>Well I am expecting to be able to build develop Š if there are changes
>that break things, these belong in a feature branch until
Hi Guys,
Well I am expecting to be able to build develop … if there are changes that
break things, these belong in a feature branch until they are sorted out and
merged to develop as soon as things are finished. Now please fix the things
that are broken in develop this time, but make sure to us
I've committed and pushed changes to MDL that should make it compile. I
don't think it will work - I'll be doing that next but I wanted to get the
project to compile.
Basically, all of the List-like MDL classes now extends Group rather than
ContainerBase, which I should delete. Then I needed to ma
I should have committed a change to the build to exclude charts. Hmm.
Peter
> On Mar 23, 2017, at 12:57 PM, Christofer Dutz
> wrote:
>
> Well I guess things are broken now (
>
> I just updated and ran a new build and Charts is exploding at the moment …
>
> Chris
>
>
>
> Am 23.03.17, 1
Yes, Chris does have a good point and from now on* I will definitely use
feature branches. I thought I could squeeze this through.
I checked in changes to Chart that should make it compile. I doubt it will
run, but that is on the list. I will look into MDL now. That will take
longer.
I am leary a
I guess I should have used a feature branch. I'm not sure how long Charts
will take. I wrote most of that code and it got pretty gnarly using List
as a basis. It probably is better to use a feature branch. Let me see if I
understand the rollback process and can get that going. Definitely a
lesson l
Sure. Including me.
But Chris does have a point that we should be using feature branches more than
we are.
The tone of my question might have not come across correctly. I meant to ask
how difficult it would be to move all changes to a feature branch and push the
feature branch. If it’s too dif
But it was expected. I can help with MDL if you will need. Just let me know.
If fixes will be today, there is no point to revert anything.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Contai
Peter warned the list that his changes would break some things temporarily,
and he asked if he should proceed. Everyone who responded said that it was
okay.
- Josh
On Thu, Mar 23, 2017 at 10:11 AM, Harbs wrote:
> Very good question.
>
> Peter, is there any chance to roll back containers and lay
Very good question.
Peter, is there any chance to roll back containers and layouts and move all the
changes to a feature branch until things are stable?
> On Mar 23, 2017, at 7:58 AM, Christofer Dutz
> wrote:
>
> Why don't you guys use feature branches?
Well I guess things are broken now (
I just updated and ran a new build and Charts is exploding at the moment …
Chris
Am 23.03.17, 17:02 schrieb "Peter Ent" :
Hi,
I've committed the changes!! The build should skip, MDL, Charts, and Basic
projects. I will get MDL and Charts r
Hi,
I've committed the changes!! The build should skip, MDL, Charts, and Basic
projects. I will get MDL and Charts running next. But before that, I will
have an email out with a breakdown of the changes I've made. Look for that
in the next couple of hours.
Good luck! Please let me know what break
Peter,
I think you should commit and try to fix at first MDL - If you have any
problems let me know I will help you.
As for the content of Basic - I think Alex know what changes will have place
in Basic due to "dual" branch.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this m
Update: I'm 99% ready to commit. I will do this tomorrow morning, my time.
I've spent today fixing some last issues in HTML package, while cosmetic,
just didn't make things look too good. There are a couple more but I'll do
them later.
I did a local merge of the latest FlexJS code and my changes a
Yes. Commit.
Right now we need to use an earlier version because the current status is
broken.
> On Mar 22, 2017, at 4:37 PM, OK wrote:
>
> In case if something is broken for somebody maybe one option is to just check
> out a previous revision by using the particular commit hash?
>
> Olaf
>
In case if something is broken for somebody maybe one option is to just check
out a previous revision by using the particular commit hash?
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Container-and-Layout-Progress-tp60658p60673.html
Sent fro
Hi Peter,
+1 for commit, than fix Charts.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Container-and-Layout-Progress-tp60658p60672.html
Sent from the Apache Flex Development mailing list arch
Hi,
One more thing: When I make this commit, I'm pretty sure Charts will be
broken until I address it. I can hold off the commit and address Charts
first, but I would prefer to commit Core and HTML and then fix Charts and
anything else.
Would that strategy (commit first, fix Charts etc after) im
Hi Peter,
Thank you for a hard work.
I'm concerning about one thing. Alex mentioned that he will merge soon dual
branch to develop - It will be tons of conflicts - Maybe it would be good to
look also into that problem.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this messag
19 matches
Mail list logo
