Nice, great idea!
Chris
From: Erik de Bruin
Sent: Tuesday, December 09, 2014 8:19 PM
To: dev@flex.apache.org
Good point. I will create the 4.15 JIRA right then, and remove them from
the 4.14 one. That way we don't lose them, while keeping the process clean.
EdB
On Wedne
Good point. I will create the 4.15 JIRA right then, and remove them from
the 4.14 one. That way we don't lose them, while keeping the process clean.
EdB
On Wednesday, December 10, 2014, Justin Mclean
wrote:
> HI,
>
> > I will remove any unassigned issues from the 4.14 roster when I cut
> > th
HI,
> I will remove any unassigned issues from the 4.14 roster when I cut
> the release branch this Friday.
IMO it's better to leave them in the JIRA ticket rather than remove them so
when you make the next release you already have some issues you may want to fix.
Justin
I also decided to mark FLEX-34555 as not a problem. The test case is
doing something rather unusual, so unless we get more information from the
author, it should be resolvable in the author’s code.
On 12/9/14, 9:13 AM, "Alex Harui" wrote:
>Added a comment to FLEX-33934. It isn’t an issue with
Added a comment to FLEX-33934. It isn’t an issue with the FocusManager or
DataGrid per-se. Someone else might be able to apply and test my
suggestions. I’m buried in the BlazeDS integration right now.
-Alex
On 12/9/14, 8:32 AM, "Erik de Bruin" wrote:
>Would all the committers that have JIRA
Would all the committers that have JIRA issues that are marked for
4.14 [1] assigned to them please take a look at them. Can you then:
1) report if you have time to take them on in the next few weeks, and/or
2) commit your code and resolve them ;-)
I will remove any unassigned issues from the 4.
mailto:dev@flex.apache.org>"
mailto:dev@flex.apache.org>>
Subject: Re: [LAST CALL] one week till the release branch is cut
On Dec 8, 2014 2:47 PM, "Alex Harui"
mailto:aha...@adobe.com>> wrote:
>
> Hi Chris,
>
> Sorry for the delay, you should be able
but I don't see the option when I
click on "More". I also cannot edit the summary/description etc. Is there
something that I need to do to give my JIRA account permissions?
>> >
>> > Thanks,
>> >
>> > Chris
>> >
>> >> From
the summary/description etc. Is there something
> that I need to do to give my JIRA account permissions?
>
> Thanks,
>
> Chris
>
>> From: e...@ixsoftware.nl<mailto:e...@ixsoftware.nl>
>> Date: Mon, 8 Dec 2014 10:05:50 +0100
>> Subject: Re: [LAST CALL] one
nt permissions?
> >
> > Thanks,
> >
> > Chris
> >
> >> From: e...@ixsoftware.nl
> >> Date: Mon, 8 Dec 2014 10:05:50 +0100
> >> Subject: Re: [LAST CALL] one week till the release branch is cut
> >> To: dev@flex.apache.org
> >>
&
y/description etc. Is there something
> that I need to do to give my JIRA account permissions?
>
> Thanks,
>
> Chris
>
>> From: e...@ixsoftware.nl
>> Date: Mon, 8 Dec 2014 10:05:50 +0100
>> Subject: Re: [LAST CALL] one week till the release branch is cut
>
mary/description etc. Is there something
that I need to do to give my JIRA account permissions?
Thanks,
Chris
> From: e...@ixsoftware.nl
> Date: Mon, 8 Dec 2014 10:05:50 +0100
> Subject: Re: [LAST CALL] one week till the release branch is cut
> To: dev@flex.apache.org
>
> Hi,
Hi,
Currently these issues are being worked on:
- stabilizing TLF
- use Apache Flex BlazeDS jar(s) instead of Adobe version
And several JIRA issues are assigned and I presume under development.
Is someone else working on anything else that they want considered to
be part of the next release?
T
> release scripts before releasing the SDK. My latest idea was that we
> could avoid the logistics of a BlazeDS release simply by bundling enough
> BlazeDS source and the jar the way we do for TLF.
+1 on trying the "TLF" style option first. That seems "doable" in a
reasonalble timeframe...
EdB
Hopefully resolving one
>problematic download for the installer :-)
>
>Chris
>
>Gesendet mit meinem HTC
>
>- Reply message -
>Von: "Erik de Bruin"
>An: "dev@flex.apache.org"
>Betreff: [LAST CALL] one week till the release branch is cut
>Dat
ld anyone here specify what's actually preventing us? From Alex'
>>>>last
>>>>post I was in the impression that the objections he had were actually
>>>>more that the jars were not located where he had expected them ... I do
>>>>not want to ben
m HTC
- Reply message -
Von: "Erik de Bruin"
An: "dev@flex.apache.org"
Betreff: [LAST CALL] one week till the release branch is cut
Datum: Fr., Dez. 5, 2014 09:48
Or better yet (sorry for not grokking the rest of your email, Alex),
how long would it take to have the S
.. I do
>>>not want to bend a perfectly working maven build to imitate the directory
>>>structure of an Ant build. After all most people will load the libs from
>>>maven and therefore the location in the build is totally irrelevant (at
>>>least for me)
>>>
&g
Ant build. After all most people will load the libs from
>>maven and therefore the location in the build is totally irrelevant (at
>>least for me)
>>
>>Chris
>>
>>____________________
>>Von: Erik de Bruin
>>Gesendet: Donnerstag, 4. D
d the libs from
>maven and therefore the location in the build is totally irrelevant (at
>least for me)
>
>Chris
>
>
>Von: Erik de Bruin
>Gesendet: Donnerstag, 4. Dezember 2014 13:48
>An: dev@flex.apache.org
>Betreff: Re: [LAST
least for me)
Chris
Von: Erik de Bruin
Gesendet: Donnerstag, 4. Dezember 2014 13:48
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] one week till the release branch is cut
No need to get TLF in shape in a week. There will be plenty of time to
stabilise
No need to get TLF in shape in a week. There will be plenty of time to
stabilise it during the release cycles. I really want TLF to be part
of this release, and will give it every chance to make it.
If at some point TLF stabilisation will turn out to be impossible for
this release, we'll point the
FWIW, I do not think we’re going to have TLF in release shape in a week.
I’ve fixed a couple of bugs this week, but it’s slow going and I know of at
least two more that need to be fixed. There’s probably more than that. I’ll
only know after I get more of the tests to run.
I’m fine with pulling
Hi,
A friendly reminder that we're nearing another milestone towards the
4.14 release. Next week, Friday dec. 12th at 9 AM (UTC: 2014-12-12
09:00), to be precise, I'll cut the release branch. This marks the
last opportunity for any features or 'normal' bug fixes to be
committed to the repo and be
24 matches
Mail list logo
