I don't care what version number we give it as long as it is <1.  I'm more 
concerned about what commit hash we are going to use.  I see a great discussion 
going on about package re-organization, however, that is probably not going to 
be ready to release soon.

My 2 cents,
-Alex

On 5/26/18, 6:23 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" 
<carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> wrote:

    Hi Om,
    
    there's many changes since 0.9.2, so I was thinking the same as you. We
    don't need to go to 0.9.4, we can skip to 0.9.5 or as you say, 0.10.0
    
    thanks
    
    2018-05-26 15:20 GMT+02:00 OmPrakash Muppirala <bigosma...@gmail.com>:
    
    > I just remembered that we have already pushed a 0.9.3 release to npm.  We
    > will not be able to re release that version.  Perhaps we just skip to 
0.9.4
    > version next?
    >
    > Or even 0.10.0?
    >
    > Thanks,
    > Om
    >
    > On Sat, May 26, 2018, 12:17 AM Carlos Rovira <carlosrov...@apache.org>
    > wrote:
    >
    > > 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 <aha...@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.rov...@gmail.com on behalf of Carlos
    > > > Rovira" <carlos.rov...@gmail.com on behalf of carlosrov...@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.li...@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 <
    > > > carlosrov...@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
    > > 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C480f4748e4c04bcb5c8408d5c30be8bc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636629378271517790&sdata=31D%2FYlvqGMoMwP2rZOdLMaSzYklK1mjgwT6jWmXpWgg%3D&reserved=0
    > >
    >
    
    
    
    -- 
    Carlos Rovira
    
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C480f4748e4c04bcb5c8408d5c30be8bc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636629378271517790&sdata=31D%2FYlvqGMoMwP2rZOdLMaSzYklK1mjgwT6jWmXpWgg%3D&reserved=0
    

Reply via email to