royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlosrov...@apache.org>
Subject Re: 0.9.3 Release
Date Sat, 26 May 2018 07:16:53 GMT
Thanks Alex,

I committed as well some poms that needed change from 0.9.4 to 0.9.3
snapshot. We'll need to check why this ones are not update to the new
version when doing a prepare release.

I'll try as well to summarize briefly the discussion about reorganization
so people could check easily the main points of what we are discussing,
hope that helps to take decisions and go forward

Thanks

Carlos



2018-05-25 21:37 GMT+02:00 Alex Harui <aharui@adobe.com.invalid>:

> In case folks are wondering, I deleted the release/0.9.3 branches from all
> 3 repos.  There have been changes made in each of the branches since the
> branches were cut and there were also issues with the royale-compiler and
> royale-typedefs branches not having synced version numbers to their develop
> branches.
>
> I see a vote thread opened today on Maven's lists for the SCM plug in.
>
> AIUI, we are on hold for a release unless we get general consensus to what
> commit hash to release from for royale-asjs.
>
> -Alex
>
> ´╗┐On 5/17/18, 3:02 AM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira" <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org>
> wrote:
>
>     The minimun change is to see package names change.
>     Take into account that all is building and working ok. Only we have
>     problems in jsonly build since is only depends on ANT (what I think is
> not
>     good, since is missing maven build), in "/mustella/tests/basicTests/".
>     Looking at what's happening in that part will solve the build.
>
>     2018-05-17 11:40 GMT+02:00 Harbs <harbs.lists@gmail.com>:
>
>     > You are right. I missed this.
>     >
>     > What is the minimum change necessary to get this to work?
>     >
>     > > On May 17, 2018, at 12:24 PM, Carlos Rovira <
> carlosrovira@apache.org>
>     > wrote:
>     > >
>     > >  I think you missed one important point I
>     > > posted in other email: All blog post samples posted that are using
> the
>     > > actual names, packages and namespaces. If you release 0.9.3
> without all
>     > > that, we can destroy out credibility since in all posts we have:
>     > >
>     > > "The example uses the new Jewel UI set that supports themes. Jewel
> will
>     > be
>     > > available in the forthcoming 0.9.3 release of Royale. In the
> meanwhile
>     > you
>     > > can find it in the develop branch."
>     > >
>     > > and the code is tailored with the actual api.
>     > >
>     > > For that reason, I think is important to hold 0.9.3 until it can
> ship
>     > with
>     > > all that we are promising in website and social networks for the
> latest 2
>     > > months. I think this is crucial.
>     >
>     >
>
>
>     --
>     Carlos Rovira
>     https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%
> 7C9a61c338f4554b04aa9008d5bbdd5762%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636621481721528268&sdata=6FoSfupJoaFpfsqJcJ7HtHNpRoQluG
> Uzh6hlM21AH20%3D&reserved=0
>
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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