Re: Requirements for Releases

2020-03-21 Thread Serkan Taş

I guess the operating system may be added.

 *   The release process should ideally work on these OS's (Linux, Windows, 
MacOS,..)

21.03.2020 12:20 tarihinde Christofer Dutz yazdı:

Hi all,

I would like to use this thread to collect some requirements for the release 
process.
Also would I like to ask you not to formulate things like “The release 
artifacts must be built with X” but rather “The release artifacts should be 
usable by X” cause that’s what really matters. I hope you get what I mean.

So far I have this:

   *   The release artifacts should be usable by Maven
   *   The release artifacts should be usable by Ant
   *   The release should include tests, which ensure the correct function of 
the royale-maven-plugin
   *   The release should include tests which ensure the correct function of 
the Ant targets
   *   It should be possible to verify a release by comparing it’s binary 
artifacts for equality (reproducible builds)
   *   It should be ensured a release candidate builds correctly with Ant and 
with Maven
   *   The release process should ideally work on any machine

Did I miss something?


Chris




Re: Let's bump Royale version to 1.0

2020-02-18 Thread Serkan Taş

Congratulations Alex,

Serkan...

18.02.2020 10:42 tarihinde Alex Harui yazdı:

Today, I received permission to disclose that Alina & Pashmina's team has 88 of 
their modules ready for release (tested and validated by their QA team).  They 
still have more modules to migrate before they deliver to their customer, but it is 
a good sign that the emulation is sufficient for many needs.

Once I can merge the "has" branch and re-stabilize, I will hope that's the last 
big change we need for a while.  I have heard that there are other migration efforts 
underway using migration and I'm sure they will keep finding bugs, but I'm feeling better 
about the emulation code.

-Alex

On 12/18/19, 9:05 AM, "Alex Harui"  wrote:

 Every day, I hope to hear news that Alina & Pashmina or Serkan or somebody else has 
deployed a production app using the MXRoyale and/or Spark Royale emulation components.  But 
instead, I see more bugs being filed for "obvious" things. You can look at the 
issues list of open and fixed issues and the commits that fixed them to get a feel for it.  
Each of us has their own threshold of how good a 1.0 version should be, so if more of you can 
look at these bugs and think it is ok for a 1.0 to have these problems, then great, let's 
release the next version as 1.0, but when I try to remember what Flex 1.0 was like, I think 
it didn't have these kinds of problems.
 
 As Carlos said below, we get one chance to make a good first impression, so I am being conservative.  But it isn't my decision alone.  It is really up to the rest of you.
 
 -Alex
 
 On 12/18/19, 6:41 AM, "Carlos Rovira"  wrote:
 
 Hi Piotr,
 
 I'm afraid my perception is that we need to get to 1.0 in a natural way. I

 mean: releasing 1.0 and giving exposure in all ways we can (webs, 
social
 media, magazines,...), means people will try us. If they try and fail, 
will
 never come back. So think about this as "only on bullet in your gun", 
if
 you fail de shot, that will be bad for all the work we are done. I'm 
ok to
 release 1.0 as soon as we see from "bird eye perspective" that all 
things
 work as we expect.
 
 For me that things are:
 
 * Documentation will need to have at least some missing pages of features

 like: DataBindnig, Loading External Data (HTTPSerice, RemoteObject, 
JSON),
 View States, Item Renderers. Things like this are essential.
 * Emulation components need to be in a shape that allow migrations in a
 good degree. I think people approaching direct migration with emulation
 components will many issues. I don't take into account look and feel of
 emulation components, just functionality and working from a flex code
 perspective, and just normal use cases with MX/Spark code, not third 
party
 libraries that we have no control over. Simple apps like TDF, and 
examples
 should work.
 
 If we decided we want to bypass the previous, at least we need to ensure

 "first try" of Royale for a newcomer (someone that knows very few 
about the
 tech) is successful. This is most important things of all. The other 
two
 are needed if we want people does not get frustrated and have 
solutions on
 their own and stay with us. The opposite is people can have a first try
 successful but abandon Royale due to unfinished things.
 
 I think 0.9.7-SNAPSHOT captures in a realistic number where we are.

 Technology works, and most people using it now can do lots of things, 
but
 we still need to cover some things to reach that 1.0. We are not too 
far
 but I think is still some month in the future.
 
 just my 2 :)
 
 Carlos
 
 
 
 
 El mié., 18 dic. 2019 a las 10:30, Piotr Zarzycki (<

 piotrzarzyck...@gmail.com>) escribió:
 
 > Hello,

 >
 > This thread is old and this was the last message from me. What has 
changed
 > on your end guys ?
 >
 > Thanks,
 > Piotr
 >
 > wt., 30 kwi 2019 o 10:07 Piotr Zarzycki 
 > napisał(a):
 >
 > > Hi Guys,
 > >
 > > Thank you so far for a great discussion. I see that there is an 
obvious
 > > needs to improve documentation the most.
 > >
 > > I would like to express my personal feelings regarding releasing 
anything
 > > what is not 1.0 after 0.9.6. Based on my experience with this 
project I
 > > don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will take 
less
 > than
 > > 6-8 months form now on. Even if we will have automatic release 
process I
 > > cannot believe that is going to happen in a less time than I 
mention.
 > >
   

Re: Welcome Greg Dove to Apache Royale's PMC

2019-10-29 Thread Serkan Taş

Congrats. Greg,

Good luck !

Serkan

29.10.2019 11:05 tarihinde Piotr Zarzycki yazdı:

  Hi Greg,

Welcome among PMCs and good luck!

Piotr

wt., 29 paź 2019 o 08:51 Harbs  napisał(a):


It is with great pleasure that I announce that the Apache Royale PMC
members have voted in Greg Dove to the PMC.  Please join us in welcoming
him.  This is a recognition of Greg's great work in helping out with Apache
Royale's compiler and architecture among other things.

Regards,
Harbs
(On behalf of Apache Royale PMC)







Re: Welcome Andrew Wetmore to Apache Royale's PMC

2019-10-03 Thread Serkan Taş
Congrat. Andrew.
Serkan.
Android için Outlook'u edinin



On Thu, Oct 3, 2019 at 8:56 PM +0300, "OmPrakash Muppirala" 
 wrote:










It is with great pleasure that I announce that the Apache Royale PMC
members have voted in Andrew Wetmore to the PMC.  Please join us in
welcoming him.  This is a recognition of Andrew's great work in helping out
with Apache Royale's documentation among other things.

Regards,
Om
(On behalf of Apache Royale PMC)







Re: [MAVEN-BUILD] Royale-asjs - Build # 1321 - Still Failing

2018-11-17 Thread Serkan Taş

Thanks Carlos, it is fixed by cleaning maven repo.

17.11.2018 14:02 tarihinde Carlos Rovira yazdı:

I think I fixed the build and was some poms not updated. typedefs and
framework was using 0.9.4 so that made MXRoyale fail.
I removed my royale folder in .m2 and all is generating ok just using
0.9.5-SNAPSHOT and as well SDK generation with ant is ok as well

El sáb., 17 nov. 2018 a las 10:12, Serkan Taş (<
serkan@likyateknoloji.com>) escribió:


+1

17.11.2018 12:07 tarihinde Carlos Rovira yazdı:

Hi, I 'm trying to build locally but some changes to MXRoyale are failing
Are someone looking at this now?
I need to build so, let me know in order to see if I must work on fixing
the issue
thanks

El vie., 16 nov. 2018 a las 23:25, Apache Jenkins Server (<
jenk...@builds.apache.org>) escribió:


The Apache Jenkins build system has built Royale-asjs (build #1321)

Status: Still Failing

Check console output at https://builds.apache.org/job/Royale-asjs/1321/
to view the results.








Re: [MAVEN-BUILD] Royale-asjs - Build # 1321 - Still Failing

2018-11-17 Thread Serkan Taş

+1

17.11.2018 12:07 tarihinde Carlos Rovira yazdı:

Hi, I 'm trying to build locally but some changes to MXRoyale are failing
Are someone looking at this now?
I need to build so, let me know in order to see if I must work on fixing
the issue
thanks

El vie., 16 nov. 2018 a las 23:25, Apache Jenkins Server (<
jenk...@builds.apache.org>) escribió:


The Apache Jenkins build system has built Royale-asjs (build #1321)

Status: Still Failing

Check console output at https://builds.apache.org/job/Royale-asjs/1321/
to view the results.