At this point, if you can find the time to try rc6 and it works for you,
then waiting a couple more days to announce 4.12 may be the safest choice.
But I still don't understand why we don't think better messaging with an
asynchronous Installer release would solve the problem regarding
confusion.
But would flattening our namespaces get around package name collisions
that Carlos ran into? Doing so wouldn't negatively affect Closure's
output, or would it?
-Alex
On 3/8/14 8:54 AM, "Erik de Bruin" wrote:
>The Closure compiler flattens namespaces (dot notation) for us, among many
>other opt
+1 Binding
Source kit:
PGP signature okay (Good signature from "Alex Harui (CODE SIGNING KEY) <
aha...@apache.org>")
MD5 checksum okay
Building from source works fine
The README is very clear about how to build from sources
Binary kit (windows only):
PGP signature okay (Good signature from "Alex
>If Installer 3.0 piggybacks with SDK 4.12, we will have a lot of folks with an
>Installer that is capable of installing FlexJS.
>Then once we actually release FlexJS 1.0, it is just a matter of updating the
>config file.
>People can then readily download and install FlexJS without having to u
On Sat, Mar 8, 2014 at 12:54 PM, Maurice Amsellem <
maurice.amsel...@systar.com> wrote:
> >Why the stealth release now? What do we gain from that? Someone will
> inevitably blog/tweet about it and we will be in a position to explain
> what's happening.
> >I don't see any harm in waiting for a fe
>Why the stealth release now? What do we gain from that? Someone will
>inevitably blog/tweet about it and we will be in a position to explain what's
>happening.
>I don't see any harm in waiting for a few days to release the sdk and the
>Installer together.
- I agree there is no point for a st
On Mar 8, 2014 8:57 AM, "Erik de Bruin" wrote:
>
> Nick, I think you hit the sweet spot.
>
> +1 on the stealth release now and a noisy announcement when the new
> Installer is available.
>
> EdB
>
Why the stealth release now? What do we gain from that? Someone will
inevitably blog/tweet about i
Nick, I think you hit the sweet spot.
+1 on the stealth release now and a noisy announcement when the new
Installer is available.
EdB
On Sat, Mar 8, 2014 at 1:48 PM, Nicholas Kwiatkowski wrote:
> I say we "release" it but not make the announcements. By release, I mean
> update the website,
The Closure compiler flattens namespaces (dot notation) for us, among many
other optimisations. There is really no need to be worry about stuff like
that.
The GCC is really an awesome tool, you should check out it's output
sometime, you'll be amazed how much optimisation it achieves if fed a
prope
I say we "release" it but not make the announcements. By release, I mean
update the website, and update the installer config. When we pass the
installer vote, we can then do the blog post, and the official apache
announcement.
That way, we can get the new one out there, but only make the noise o
Hi,
> I think both are different things, so I'll make a release of SDK 4.12 and
> then after RC6 conclude a few days later will announce Installer.
So I think you mean to informally vote +1 to release both at different times
rather than -1 there?
Thanks,
Justin
Hi,
> For ex. soon I will add Polish language to installer - is this mean that I
> have to wait for the next release of sdk? :)
IMO No. As per Apache rules/guidelines any committer can make a release at any
time. it requires 3 +1 PMC votes to pass as an official release and a -1 is not
a veto,
I think both are different things, so I'll make a release of SDK 4.12 and
then after RC6 conclude a few days later will announce Installer. There's
in my opinion an additional marketing reason to do this since we should
take profit of all the work in separate pieces and separate in time to get
more
Hi Alex,
I think this is right since as I see it, generated code for JS takes the
role of somewhat like compiled code, regarding there's no developer use and
it's final. So whatever we do to get more speed the better, id we could get
speed with tricks like that we should change from dot notation t
>Along which comes the new features like FlexJS, etc.
That's exactly my point.
Installer 3.0 is more for FlexJS (and for internal maintenance purpose).
It's not "really" needed to install Flex SDK.
So if we don't want to get people confused, let's link Installer 3.0 to FlexJS
PR,
and ment
If we don't announce it, people won't bother to come check it out.
We do have an auto-update functionality built into Installer 2.7, but that
would require then to start the app first.
Whereas, if we pair it up with 4.12, folks who want the new sdk will
automatically get the new Installer.
Alon
A few thoughts:
Why should we announce the installer at all?
Do other products announce release of their installers ? I don't think so.
Whatever efforts and innovation there is in it, it's only a
convenience/commodity tool.
What new functionality does Installer 3.0 bring over 2.7 , from an
Hi,
I think we should wait and give installer the last chance rc6. We are
waiting for 4.12 so long - couple of days do not change to much, but in the
feature release of installer shouldn't be depend on release sdk.
For ex. soon I will add Polish language to installer - is this mean that I
have t
18 matches
Mail list logo
