On Sun, Jan 28, 2018 at 11:42 PM, Alex Harui
wrote:
> I was (and still am) confused by Om's effort to publish the NPM artifacts.
> I was waiting to hear back from Om as to whether it was going to happen
> so we know whether to recommend to folks to use the URL on
I was (and still am) confused by Om's effort to publish the NPM artifacts.
I was waiting to hear back from Om as to whether it was going to happen
so we know whether to recommend to folks to use the URL on GitHub or not.
I will send the announcement shortly with the GH URL, and we can send a
On Jan 28, 2018 3:34 AM, "Piotr Zarzycki" wrote:
Om,
But Alex figure out that we can use links from GitHub which I published
[1]. Only JSOnly working.
sudo npm install -g
https://github.com/apache/royale-asjs/releases/download/apache-royale-0.9.0
Om,
But Alex figure out that we can use links from GitHub which I published
[1]. Only JSOnly working.
sudo npm install -g
https://github.com/apache/royale-asjs/releases/download/apache-royale-0.9.0
/apache-royale-0.9.0-bin-js.tar.gz
Can we for that release ?
Thanks, Piotr
2018-01-28 12:31
On Sun, Jan 28, 2018 at 3:29 AM, Piotr Zarzycki
wrote:
> Yeah. I was going to ask for the Announce as well. Let's mention link to
> working version of NPM, which you Alex figure out. We could put them to the
> website.
>
As mentioned earlier, the npm package is broken
Yeah. I was going to ask for the Announce as well. Let's mention link to
working version of NPM, which you Alex figure out. We could put them to the
website.
Thanks,
Piotr
2018-01-28 11:24 GMT+01:00 Carlos Rovira :
> Hi,
>
> I'm a bit confused here. What happen with the
Hi,
I'm a bit confused here. What happen with the release and announcement? If
we have a release we should announce it. We published in twitter and
facebook that we was very close to our first release but starts to be a big
delay since that.
Thanks
2018-01-25 20:29 GMT+01:00 Jason Guild
Please comment on the draft below which tries to implement feedback on the
first draft. I'm thinking we should wait to see if Om can find a way to
publish the artifacts via NPM or find a non-mirrored URL for the NPM
package before we finalize instructions about NPM and send out the
announcement.