flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From OmPrakash Muppirala <bigosma...@gmail.com>
Subject Re: [DRAFT 2] 4.13.0 Announcement
Date Sat, 26 Jul 2014 15:52:18 GMT
On Fri, Jul 25, 2014 at 12:06 AM, Alex Harui <aharui@adobe.com> wrote:

> Technically, we are good to go, but I've chickened out of pushing the
> announcement because I am trying to finish up an AIR app that will at
> least monitor the checksums, and maybe even auto-update the config.xml
> file.  The worst case scenario is we announce, 500 folks start downloading
> and moments after the announce Adobe updates the playerglobal or AIR SDK
> and 500 folks fail to install while we are sleeping.  But if folks think
> we should just announce then we can go for it.
>
>
Let's wait till the weekend is over and announce on Monday morning.  I
don't think we want to delay the announcement anymore.

Thanks,
Om


> I've found out how browsers check the last modified time on things in the
> cache and am trying to get that to work from AIR.  Then the next step
> would be to figure out how to auto-update the config.xml.  Do you know if
> there is a way to automate the svnpubsub?
>
>
> -Alex
>
> On 7/24/14 12:25 PM, "OmPrakash Muppirala" <bigosmallm@gmail.com> wrote:
>
> >Alex, are we good to go?
> >
> >If there are no more changes to this draft, I will put out a blog post.
> >
> >Thanks,
> >Om
> >
> >
> >On Tue, Jul 22, 2014 at 8:29 AM, Alex Harui <aharui@adobe.com> wrote:
> >
> >>
> >>
> >> On 7/22/14 12:59 AM, "Tom Chiverton" <tc@extravision.com> wrote:
> >>
> >> >Wil https://issues.apache.org/jira/browse/FLEX-34405 be fixed by then
> ?
> >> No, it was reported after we voted to release.  Since we got several
> >> months into 4.12.1 before it was reported, I don't see it as a reason
> >>not
> >> to release.  Volunteers are welcome, of course, to fix the bug and push
> >>a
> >> 4.13.1 if they have the time and energy.
> >>
> >> >What about adl etc ending up in the wrong place sometimes ? That should
> >> >definitely be called out as a known issue ?
> >> AFAICT, it has been broken for a long time and only discovered recently,
> >> so again I wouldn't mess with the release notes and packaging to call it
> >> out.  Not sure I want to mention known issues that have so far affected
> >> few people in the announcement: I would rather focus on positive
> >>messages.
> >>  But if others agree with you I will add it.  And again, volunteers are
> >> welcome to address this issue as well.
> >>
> >> -Alex
> >>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message