You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Christofer Dutz <ch...@c-ware.de> on 2020/03/25 11:39:02 UTC

Releasing: Finally giving up

Hi all,

after 3-4 days of some times 10-16 hours of working on getting the “process” running, I’m finally giving up.
We managed to fix a lot of issues in the way the steps were setup and managed to get to step 7 however there’s no getting past that.

The problem are the reproducible builds.

While for the java part I think we have all bases covered, however I can’t see however how I can fix the compiler to actually produce reproducible builds.

We are passing in the timestamp (slightly different format, however still correct as we also adjusted the format-string). When building locally, the timestamp is exactly as the timestamp string tells the compiler. On the CI however there’s this 60 minute offset. I have explicitly set the time-zone wherever I found time-zone relevant code to UTC (Which is the general best practice for date stuff). However the offset didn’t change. So I am completely out of ideas what could be causing this. If it really is the Summertime in the US, well I don’t know how to fix it (perhaps setup a rule to not release in this time).

Besides that, there are still differences in the library SWF:

  *   As I mentioned yesterday, the node typedef contains a “net” object definition in the local build and a “http” one on the CI server version.
  *   In other modules it’s simply the order of items generated. I guess it’s a similar issue as the one I fixed in the build-tools, but I have no idea how to fix it in the compiler

So in the end I’m giving up … I think the “process” is now way more stable than before, but it’s still a really fragile construct. Today Greg, Carlos and I did it together via Zoom and still we had to re-do some steps because one little preparation was missed.

I would strongly doubt that the reproducible builds really built globally reproducible builds in the past … perhaps it worked in a narrow corridor of time-zones and OS/Java versions (I did use java 1.8), but I simply can’t believe it ever was 100% reproducible.

So as long as this reproducibility is a requirement, I guess we’re done. I do understand what it’s used for in this context, however I think it’s just not working.

The other option would be to simply release with maven, which would have been a 1-2 hour experience for all modules.

I do agree that if the steps work and all preconditions would be checked (which they currently are not) it is very easy to break the “process”. And it involves running 13 jobs … but as far as I got it also the execution of 32 manual commands for everything till step 7
4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32

So as long as we’re forced to stick to this process … I guess someone else will have to do it.

Please feel free to revert any changes I did in the last few months.

Signing off,
Chris

PS: You really should make this ApacheRoyaleCI guy a committer considering the amount of emails he’s writing ;-)



Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,

I think is good to wait for Yishay try. I prefer he test the current
process and then comes back and report his founds.
I'll be more happy if all people here see the same problem we're having
instead of just believing in something that if is not tried is a black box
for the rest. For me was a black box until I was in front of it. I now have
a clear knowledge of it. Others need to see if arrives to the same shore or
not.

We need to solve this problem in a way that all people here choose an
option that see is the right one, and I think the only way that we all know
that is experiencing it.

So for me +1 to Yishay trying it and reporting, and thanks for taking that
step forward :)

Hoping to get soon your report of your experience.

Carlos


El jue., 26 mar. 2020 a las 14:47, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:

> Chris,
>
> I would love to test stuff, once it's really do for me everything. If you
> are saying that I will take source-bundle (not sure what do you mean by
> that - take source bundle from where) and do in console "ant -f build.xml"
> - That's not what expect. I expect that I will make everything being in one
> console windows.
>
> 1) Prepare RC1 with signed stuff - should I sign stuff if it's RC1 by my
> Apache gpg keys ?
> 2) Produce Maven distribution IDE so I could test them
> 3) Produce Ant IDE artifacts to test them
>
> Provide me an instruction which I do that and I will start going trough it
> in upcoming week. Instruction should also contains whether I need to create
> branches, tags etc. That instruction should contains everything what RM
> should do, what should click, type checkout etc. - Treat me that I would
> just join the project. I was an RM, some steps would be an obvious for me,
> but for Yishay or any other person won't be at all - whether he try old way
> of doing stuff or new.
>
> Thanks,
> Piotr
>
>
>
> czw., 26 mar 2020 o 14:04 Christofer Dutz <ch...@c-ware.de>
> napisał(a):
>
> > Hi Piotr,
> >
> > I would assume that ideally you would simply do a normal Maven release.
> >
> > This will produce all the artifacts needed for an official Apache release
> > and
> > also create and deploy the convenience binaries for Maven.
> >
> > I would then suggest to use the source-bundle and run the Ant build
> inside
> > it to produce the Ant convenience binary (SDK) from that.
> >
> > Chris
> >
> >
> >
> > Am 26.03.20, 13:43 schrieb "Piotr Zarzycki" <piotrzarzycki21@gmail.com
> >:
> >
> >     Hi Chris,
> >
> >     My end expectation is that I will be able to prepare RC1 by Maven,
> but
> > also
> >     take care of ANT build - I'm not sure maybe it would be enough if ANT
> > build
> >     will be launched by maven and produce IDE ready SDK - which could be
> > tested
> >     in that way.
> >
> >     Thanks,
> >     Piotr
> >
> >     czw., 26 mar 2020 o 13:38 Christofer Dutz <christofer.dutz@c-ware.de
> >
> >     napisał(a):
> >
> >     > Hi Piotr,
> >     >
> >     > generally the build is currently already in a state we should be
> > able to
> >     > release Royale with Maven.
> >     > I intentionally put all the bells and whistles in a profile that
> you
> > need
> >     > to activate “royale-release”.
> >     > If you don’t do that, it should be a normal Maven release.
> >     >
> >     > Chris
> >     >
> >     > Von: Piotr Zarzycki <pi...@gmail.com>
> >     > Antworten an: "dev@royale.apache.org" <de...@royale.apache.org>
> >     > Datum: Donnerstag, 26. März 2020 um 12:27
> >     > An: Apache Royale Development <de...@royale.apache.org>
> >     > Betreff: Re: Releasing: Finally giving up
> >     >
> >     > Hi All,
> >     >
> >     > I'm member of Apache Foundation for quite some time now. I think I
> > have
> >     > wrote maybe 2-3 emails during that time on members mailing list. -
> > Why? -
> >     > well I'm a person which doesn't like never ending stories, stories
> > which
> >     > are not end up with consensus nor action and I'm sorry but this is
> > how it
> >     > looks like in most cases there. Here we are in Apache Royale
> project
> > where
> >     > this thread ended up exactly the same - never ending story. - As
> PMC
> > of
> >     > this project I would like to say enough! :)
> >     >
> >     > I had hope that when Carlos and Chris try CI steps and in the
> > process they
> >     > may have some issues, but they will end up in the same place as I
> > ended up
> >     > where I was able to prepare RC1 in about 2h without the problem. It
> > turns
> >     > out that they end up in the place where I have started, in the
> place
> > where
> >     > I have spend 5-6 days of work to finally reach stable point. They
> > ended up
> >     > frustrated in the same way as I was!
> >     >
> >     > I really don't care now what kind of issue they have now, whether
> > it's
> >     > fixable or not - I just have enough of those never ending
> > discussions where
> >     > there is absolutely no results.
> >     >
> >     > I met Chris in US in Miami and I have spend with him best time
> ever,
> > he is
> >     > really great developer - if he is saying that he will have release
> > process
> >     > in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not
> in
> > a week
> >     > - start today!
> >     >
> >     > Please start whole work on that and make it happen. I will be the
> > first
> >     > who try the process and maybe with Chris's help we will solve also
> > issue
> >     > with uploading artifacts to staging area which we had.
> >     >
> >     > Good Luck,
> >     > Piotr
> >     >
> >     > czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> >     > contact@cristallium.com>> napisał(a):
> >     >
> >     > Hi Guys,
> >     >
> >     > I'm a lover of Flex dev guy since more than 10 years, been members
> > of Flex
> >     > group on Montpellier (France) at golden age of Flex and go at all
> >     > conferences when Michaël Chaize came to Montpellier (and using Flex
> > every
> >     > day).
> >     >
> >     > First of all I want to thank every one of you for your hard work,
> and
> >     > congratulate you for the actual Apache Royale capabilities.
> >     > With the last features (especialy datagrid), today your great work
> > make
> >     > possible to use Apache Royale in business application. Of course,
> > there are
> >     > bugs, but when reported, it's quickly fix, this is great.
> >     >
> >     > Now, this is a huge opportunity but also risk for all guys like me
> > to adop
> >     > Apache Royale for futur projects or use it instead of using Air
> when
> > it's
> >     > possible.
> >     > Personnaly, I first use it on my own Webs applications and perhaps
> > for my
> >     > customers on little applications for the begin. My big enormous
> > worry is to
> >     > use it and be alone in front of a SDK bug.
> >     > Seeing new release every 1 or 2 months should certainly reassure
> me.
> > For
> >     > now I see SDK 0.9.7 since a lot of time and this make me affraid
> and
> > I
> >     > don't understand why there is no 0.9.8.
> >     >
> >     > I'm speaking as an Apache Royale SDK user : I'm very sad to read
> > these
> >     > debates on the subject of tools to use for making release. I don't
> > care
> >     > about tools nedeed or not to build the release SDK.
> >     > I would like use Apache Royale to build RAD (Rapid Application Dev)
> > Web
> >     > applications and see more and more SDK features added, and
> > participate to
> >     > project (like today) by reporting bug  by using my time on isolate
> > the bug
> >     > and make tests cases with screenshoots to save your time in fixing
> > it.
> >     >
> >     > Using Reac, Bootstrap, AngularJS or other similar is a back to
> 80's.
> > How
> >     > can I explain my customer that I need 3 ou 4 days to make thinks
> > that took
> >     > me 1 day with Flex ?
> >     > The big competitive advantage of Apache Royale is not only be able
> to
> >     > re-use Flex apps but is also simplicity and time saving where other
> > SDK
> >     > can't do it. (I think you already know that)
> >     >
> >     > I am convinced that all guys like me will jump using Royale when
> > they will
> >     > know that there is a bug free SDK with fast evolution available.
> >     > (unfortunaly it's not known enough, nobody know someone working in
> >     > newspapers ?)
> >     >
> >     > So please, I beg you, don't waste your time on things that are not
> >     > essential and like Carlos said, go forward. From outside view,
> Apache
> >     > Royale stay sticky to 0.9.7.
> >     >
> >     > You are so close of a v1.0, I hope see it very soon and other
> > releases
> >     > with bugs fix every 1, 2 or 3 months.
> >     > Consider my comments as support and not criticism.
> >     >
> >     > Thanks again for your hard work.
> >     >
> >     > Long life and success to Apache Royale !
> >     >
> >     > Fred
> >     >
> >     >
> >     >
> >     > Le 26.03.2020 09:26, Carlos Rovira a écrit :
> >     > Hi,
> >     >
> >     > that's amazingly simple, so I think we should go that way without
> > doubt. I
> >     > think reached this point there's a clear sense of that we need to
> go
> > that
> >     > route.
> >     >
> >     > We tried our best to stick with the previous process and we're all
> >     > loosing lots of time. Then currently seems no more people in the
> > community
> >     > was interested in this thread, event to comment a single line (here
> > or in
> >     > the other users list thread), what means that or there's no more
> > people
> >     > like us in this project or people really is not interested and just
> > want us
> >     > to release and go forward.
> >     >
> >     > As previously I think most of the PMCs here (Om, Josh, Greg and me
> > for
> >     > sure), probably Yishay for his concise comments are more for this.
> >     > My thinking is that the right now I think only 2 PMCs are for CI
> > Server,
> >     > and other one that is uncertainly but didn't try the CI Server.
> >     >
> >     > I think all can live together while is not a must for the rest that
> > don't
> >     > want it the others option, so what's about if we release with the
> >     > super-simple steps Chris proposal, and others wanting to use CI do
> > that
> >     > when is their RM turn ? (of course maintaining it and making it
> work
> > for
> >     > his release without requiring nothing for the rest that doesn't
> want
> > it).
> >     >
> >     > Release as other projects do is recommended but not required, the
> > same as
> >     > the actual CI server (but this one should be less recommended since
> > is a
> >     > royale-only practice not seen in any other place).
> >     >
> >     > What's the important thing is to release, do it, and do it easily
> and
> >     > often.
> >     >
> >     > Thanks
> >     >
> >     >
> >     >
> >     > El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
> >     > christofer.dutz@c-ware.de<ma...@c-ware.de>>)
> > escribió:
> >     >
> >     >
> >     > Ok,
> >     >
> >     > I'll write this a last time as I do feel like we're going in
> circles
> > and
> >     > will from now on not participate in any discussion involving
> > releasing on a
> >     > CI server.
> >     >
> >     > A correct Maven release would use (There will be some additional
> > profiles
> >     > to activate to include all modules)
> >     >
> >     > 1) the "mvn release:branch" call in order to create the branch and
> > bump
> >     > the version of develop to the next version.
> >     > 2) the "mvn release:prepare" to change the pom to the release
> > version, set
> >     > the timestamp in the pom (for reproducible builds) build ... if all
> > tests
> >     > are good, commit the changes, tag this commit, update the poms to
> > the next
> >     > development version, commit those changes and push everything.
> >     > 3) the "mvn release:perform" which will checkout the tagged version
> > build
> >     > everything with the "apache-release" profile turned on (Which
> causes
> > the
> >     > source.jars, Javadoc.jars, hashes and gpg singatures to be created
> > as well
> >     > as the assembly) This also deploys the built artifacts to Nexus.
> >     >
> >     > Most of that you are already doing on the CI server however you're
> > not
> >     > letting it do all automatically (For lack of credentials)
> >     >
> >     > But ... if you would just be doing those steps on the RM machine.
> >     >
> >     > Chris
> >     >
> >     >
> >     >
> >     >
> >     >
> >     > Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
> > <mailto:
> >     > aharui@adobe.com.INVALID>>:
> >     >
> >     >
> >     >
> >     >     On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org
> > <mailto:
> >     > carlosrovira@apache.org>> wrote:
> >     >
> >     >         > What I want to know is what the Maven commands should be
> to
> >     > create a
> >     >         > release in this "conventional process" you are referring
> > to.
> >     >         >
> >     >
> >     >         If you want to know what's the conventional maven process
> > is, I
> >     > think I can
> >     >         ask Chris if he wants to work with me on that process,
> since
> > he
> >     > already did
> >     >         many other Apache projects, we can expect the process is
> > what is
> >     > needed for
> >     >         us to. But just expect that will be a series of standard
> > maven
> >     > commands
> >     >         (prepare, release,...), so nothing strange at all (I
> expect).
> >     >
> >     >         Do you want us to do that?
> >     >
> >     >     Yes.  I want to know what the series of standard Maven commands
> > are.
> >     > Then we can figure out how to convert them to run on the CI server.
> >     >
> >     >     -Alex
> >     >
> >     >         Thanks
> >     >
> >     >
> >     >         >
> >     >         > Maybe someone else can explain better than me.
> >     >         >
> >     >         > -Alex
> >     >         >
> >     >         > On 3/25/20, 2:22 PM, "Carlos Rovira" <
> > carlosrovira@apache.org
> >     > <ma...@apache.org>>
> >     > wrote:
> >     >         >
> >     >         >     Hi Alex,
> >     >         >
> >     >         >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
> >     >         > (<aharui@adobe.com.invalid<mailto:
> aharui@adobe.com.invalid
> > >>)
> >     >         >     escribió:
> >     >         >
> >     >         >     > Carlos,
> >     >         >     >
> >     >         >     > I'm pretty sure that part of the "conventional
> > process"
> >     > you want to
> >     >         > try
> >     >         >     > requires filling the staging repo from a local
> > machine.
> >     >         >     >
> >     >         >
> >     >         >     This is what we already did. If you go to [1] will
> see
> > [2].
> >     > That was
> >     >         > the
> >     >         >     upload of compiler to the staging repo. When trying
> to
> > do
> >     > the same for
> >     >         >     typedefs it failed when trying to fill repo from
> local
> >     > machine. I think
> >     >         >     Chris or I should not take more time in trying to fix
> > Ant
> >     > scripts that
> >     >         > are
> >     >         >     failing.
> >     >         >
> >     >         >     Thanks
> >     >         >
> >     >         >     [1]
> >     >         >
> >     >
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
> >     >         >     [2]
> >     >         >
> >     >
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
> >     >         >
> >     >         >
> >     >         >
> >     >         >
> >     >         >     >
> >     >         >     > --
> >     >         >     > Carlos Rovira
> >     >         >     >
> >     >         >
> >     >
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
> >     >         >     >
> >     >         >     >
> >     >         >     >
> >     >         >     >
> >     >         >
> >     >         >
> >     >         >
> >     >
> >     >         --
> >     >         Carlos Rovira
> >     >
> >     >
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
> >     >
> >     >
> >     >
> >     >
> >     >
> >     >
> >     > --
> >     >
> >     > Frédéric Gilli
> >     >
> >     > mob.0668542622
> >     >
> >     > http://www.cristallium.com
> >     >
> >     > [cid:171168797bb6addd0331]<http://www.cristallium.com/>
> >     >
> >     >
> >     >
> >     >
> >     > --
> >     >
> >     > Piotr Zarzycki
> >     >
> >     > Patreon: https://www.patreon.com/piotrzarzycki
> >     >
> >
> >
> >     --
> >
> >     Piotr Zarzycki
> >
> >     Patreon: *https://www.patreon.com/piotrzarzycki
> >     <https://www.patreon.com/piotrzarzycki>*
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Releasing: Finally giving up

Posted by Piotr Zarzycki <pi...@gmail.com>.
Chris,

I would love to test stuff, once it's really do for me everything. If you
are saying that I will take source-bundle (not sure what do you mean by
that - take source bundle from where) and do in console "ant -f build.xml"
- That's not what expect. I expect that I will make everything being in one
console windows.

1) Prepare RC1 with signed stuff - should I sign stuff if it's RC1 by my
Apache gpg keys ?
2) Produce Maven distribution IDE so I could test them
3) Produce Ant IDE artifacts to test them

Provide me an instruction which I do that and I will start going trough it
in upcoming week. Instruction should also contains whether I need to create
branches, tags etc. That instruction should contains everything what RM
should do, what should click, type checkout etc. - Treat me that I would
just join the project. I was an RM, some steps would be an obvious for me,
but for Yishay or any other person won't be at all - whether he try old way
of doing stuff or new.

Thanks,
Piotr



czw., 26 mar 2020 o 14:04 Christofer Dutz <ch...@c-ware.de>
napisał(a):

> Hi Piotr,
>
> I would assume that ideally you would simply do a normal Maven release.
>
> This will produce all the artifacts needed for an official Apache release
> and
> also create and deploy the convenience binaries for Maven.
>
> I would then suggest to use the source-bundle and run the Ant build inside
> it to produce the Ant convenience binary (SDK) from that.
>
> Chris
>
>
>
> Am 26.03.20, 13:43 schrieb "Piotr Zarzycki" <pi...@gmail.com>:
>
>     Hi Chris,
>
>     My end expectation is that I will be able to prepare RC1 by Maven, but
> also
>     take care of ANT build - I'm not sure maybe it would be enough if ANT
> build
>     will be launched by maven and produce IDE ready SDK - which could be
> tested
>     in that way.
>
>     Thanks,
>     Piotr
>
>     czw., 26 mar 2020 o 13:38 Christofer Dutz <ch...@c-ware.de>
>     napisał(a):
>
>     > Hi Piotr,
>     >
>     > generally the build is currently already in a state we should be
> able to
>     > release Royale with Maven.
>     > I intentionally put all the bells and whistles in a profile that you
> need
>     > to activate “royale-release”.
>     > If you don’t do that, it should be a normal Maven release.
>     >
>     > Chris
>     >
>     > Von: Piotr Zarzycki <pi...@gmail.com>
>     > Antworten an: "dev@royale.apache.org" <de...@royale.apache.org>
>     > Datum: Donnerstag, 26. März 2020 um 12:27
>     > An: Apache Royale Development <de...@royale.apache.org>
>     > Betreff: Re: Releasing: Finally giving up
>     >
>     > Hi All,
>     >
>     > I'm member of Apache Foundation for quite some time now. I think I
> have
>     > wrote maybe 2-3 emails during that time on members mailing list. -
> Why? -
>     > well I'm a person which doesn't like never ending stories, stories
> which
>     > are not end up with consensus nor action and I'm sorry but this is
> how it
>     > looks like in most cases there. Here we are in Apache Royale project
> where
>     > this thread ended up exactly the same - never ending story. - As PMC
> of
>     > this project I would like to say enough! :)
>     >
>     > I had hope that when Carlos and Chris try CI steps and in the
> process they
>     > may have some issues, but they will end up in the same place as I
> ended up
>     > where I was able to prepare RC1 in about 2h without the problem. It
> turns
>     > out that they end up in the place where I have started, in the place
> where
>     > I have spend 5-6 days of work to finally reach stable point. They
> ended up
>     > frustrated in the same way as I was!
>     >
>     > I really don't care now what kind of issue they have now, whether
> it's
>     > fixable or not - I just have enough of those never ending
> discussions where
>     > there is absolutely no results.
>     >
>     > I met Chris in US in Miami and I have spend with him best time ever,
> he is
>     > really great developer - if he is saying that he will have release
> process
>     > in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not in
> a week
>     > - start today!
>     >
>     > Please start whole work on that and make it happen. I will be the
> first
>     > who try the process and maybe with Chris's help we will solve also
> issue
>     > with uploading artifacts to staging area which we had.
>     >
>     > Good Luck,
>     > Piotr
>     >
>     > czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
>     > contact@cristallium.com>> napisał(a):
>     >
>     > Hi Guys,
>     >
>     > I'm a lover of Flex dev guy since more than 10 years, been members
> of Flex
>     > group on Montpellier (France) at golden age of Flex and go at all
>     > conferences when Michaël Chaize came to Montpellier (and using Flex
> every
>     > day).
>     >
>     > First of all I want to thank every one of you for your hard work, and
>     > congratulate you for the actual Apache Royale capabilities.
>     > With the last features (especialy datagrid), today your great work
> make
>     > possible to use Apache Royale in business application. Of course,
> there are
>     > bugs, but when reported, it's quickly fix, this is great.
>     >
>     > Now, this is a huge opportunity but also risk for all guys like me
> to adop
>     > Apache Royale for futur projects or use it instead of using Air when
> it's
>     > possible.
>     > Personnaly, I first use it on my own Webs applications and perhaps
> for my
>     > customers on little applications for the begin. My big enormous
> worry is to
>     > use it and be alone in front of a SDK bug.
>     > Seeing new release every 1 or 2 months should certainly reassure me.
> For
>     > now I see SDK 0.9.7 since a lot of time and this make me affraid and
> I
>     > don't understand why there is no 0.9.8.
>     >
>     > I'm speaking as an Apache Royale SDK user : I'm very sad to read
> these
>     > debates on the subject of tools to use for making release. I don't
> care
>     > about tools nedeed or not to build the release SDK.
>     > I would like use Apache Royale to build RAD (Rapid Application Dev)
> Web
>     > applications and see more and more SDK features added, and
> participate to
>     > project (like today) by reporting bug  by using my time on isolate
> the bug
>     > and make tests cases with screenshoots to save your time in fixing
> it.
>     >
>     > Using Reac, Bootstrap, AngularJS or other similar is a back to 80's.
> How
>     > can I explain my customer that I need 3 ou 4 days to make thinks
> that took
>     > me 1 day with Flex ?
>     > The big competitive advantage of Apache Royale is not only be able to
>     > re-use Flex apps but is also simplicity and time saving where other
> SDK
>     > can't do it. (I think you already know that)
>     >
>     > I am convinced that all guys like me will jump using Royale when
> they will
>     > know that there is a bug free SDK with fast evolution available.
>     > (unfortunaly it's not known enough, nobody know someone working in
>     > newspapers ?)
>     >
>     > So please, I beg you, don't waste your time on things that are not
>     > essential and like Carlos said, go forward. From outside view, Apache
>     > Royale stay sticky to 0.9.7.
>     >
>     > You are so close of a v1.0, I hope see it very soon and other
> releases
>     > with bugs fix every 1, 2 or 3 months.
>     > Consider my comments as support and not criticism.
>     >
>     > Thanks again for your hard work.
>     >
>     > Long life and success to Apache Royale !
>     >
>     > Fred
>     >
>     >
>     >
>     > Le 26.03.2020 09:26, Carlos Rovira a écrit :
>     > Hi,
>     >
>     > that's amazingly simple, so I think we should go that way without
> doubt. I
>     > think reached this point there's a clear sense of that we need to go
> that
>     > route.
>     >
>     > We tried our best to stick with the previous process and we're all
>     > loosing lots of time. Then currently seems no more people in the
> community
>     > was interested in this thread, event to comment a single line (here
> or in
>     > the other users list thread), what means that or there's no more
> people
>     > like us in this project or people really is not interested and just
> want us
>     > to release and go forward.
>     >
>     > As previously I think most of the PMCs here (Om, Josh, Greg and me
> for
>     > sure), probably Yishay for his concise comments are more for this.
>     > My thinking is that the right now I think only 2 PMCs are for CI
> Server,
>     > and other one that is uncertainly but didn't try the CI Server.
>     >
>     > I think all can live together while is not a must for the rest that
> don't
>     > want it the others option, so what's about if we release with the
>     > super-simple steps Chris proposal, and others wanting to use CI do
> that
>     > when is their RM turn ? (of course maintaining it and making it work
> for
>     > his release without requiring nothing for the rest that doesn't want
> it).
>     >
>     > Release as other projects do is recommended but not required, the
> same as
>     > the actual CI server (but this one should be less recommended since
> is a
>     > royale-only practice not seen in any other place).
>     >
>     > What's the important thing is to release, do it, and do it easily and
>     > often.
>     >
>     > Thanks
>     >
>     >
>     >
>     > El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
>     > christofer.dutz@c-ware.de<ma...@c-ware.de>>)
> escribió:
>     >
>     >
>     > Ok,
>     >
>     > I'll write this a last time as I do feel like we're going in circles
> and
>     > will from now on not participate in any discussion involving
> releasing on a
>     > CI server.
>     >
>     > A correct Maven release would use (There will be some additional
> profiles
>     > to activate to include all modules)
>     >
>     > 1) the "mvn release:branch" call in order to create the branch and
> bump
>     > the version of develop to the next version.
>     > 2) the "mvn release:prepare" to change the pom to the release
> version, set
>     > the timestamp in the pom (for reproducible builds) build ... if all
> tests
>     > are good, commit the changes, tag this commit, update the poms to
> the next
>     > development version, commit those changes and push everything.
>     > 3) the "mvn release:perform" which will checkout the tagged version
> build
>     > everything with the "apache-release" profile turned on (Which causes
> the
>     > source.jars, Javadoc.jars, hashes and gpg singatures to be created
> as well
>     > as the assembly) This also deploys the built artifacts to Nexus.
>     >
>     > Most of that you are already doing on the CI server however you're
> not
>     > letting it do all automatically (For lack of credentials)
>     >
>     > But ... if you would just be doing those steps on the RM machine.
>     >
>     > Chris
>     >
>     >
>     >
>     >
>     >
>     > Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
> <mailto:
>     > aharui@adobe.com.INVALID>>:
>     >
>     >
>     >
>     >     On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org
> <mailto:
>     > carlosrovira@apache.org>> wrote:
>     >
>     >         > What I want to know is what the Maven commands should be to
>     > create a
>     >         > release in this "conventional process" you are referring
> to.
>     >         >
>     >
>     >         If you want to know what's the conventional maven process
> is, I
>     > think I can
>     >         ask Chris if he wants to work with me on that process, since
> he
>     > already did
>     >         many other Apache projects, we can expect the process is
> what is
>     > needed for
>     >         us to. But just expect that will be a series of standard
> maven
>     > commands
>     >         (prepare, release,...), so nothing strange at all (I expect).
>     >
>     >         Do you want us to do that?
>     >
>     >     Yes.  I want to know what the series of standard Maven commands
> are.
>     > Then we can figure out how to convert them to run on the CI server.
>     >
>     >     -Alex
>     >
>     >         Thanks
>     >
>     >
>     >         >
>     >         > Maybe someone else can explain better than me.
>     >         >
>     >         > -Alex
>     >         >
>     >         > On 3/25/20, 2:22 PM, "Carlos Rovira" <
> carlosrovira@apache.org
>     > <ma...@apache.org>>
>     > wrote:
>     >         >
>     >         >     Hi Alex,
>     >         >
>     >         >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>     >         > (<aharui@adobe.com.invalid<mailto:aharui@adobe.com.invalid
> >>)
>     >         >     escribió:
>     >         >
>     >         >     > Carlos,
>     >         >     >
>     >         >     > I'm pretty sure that part of the "conventional
> process"
>     > you want to
>     >         > try
>     >         >     > requires filling the staging repo from a local
> machine.
>     >         >     >
>     >         >
>     >         >     This is what we already did. If you go to [1] will see
> [2].
>     > That was
>     >         > the
>     >         >     upload of compiler to the staging repo. When trying to
> do
>     > the same for
>     >         >     typedefs it failed when trying to fill repo from local
>     > machine. I think
>     >         >     Chris or I should not take more time in trying to fix
> Ant
>     > scripts that
>     >         > are
>     >         >     failing.
>     >         >
>     >         >     Thanks
>     >         >
>     >         >     [1]
>     >         >
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
>     >         >     [2]
>     >         >
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
>     >         >
>     >         >
>     >         >
>     >         >
>     >         >     >
>     >         >     > --
>     >         >     > Carlos Rovira
>     >         >     >
>     >         >
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>     >         >     >
>     >         >     >
>     >         >     >
>     >         >     >
>     >         >
>     >         >
>     >         >
>     >
>     >         --
>     >         Carlos Rovira
>     >
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>     >
>     >
>     >
>     >
>     >
>     >
>     > --
>     >
>     > Frédéric Gilli
>     >
>     > mob.0668542622
>     >
>     > http://www.cristallium.com
>     >
>     > [cid:171168797bb6addd0331]<http://www.cristallium.com/>
>     >
>     >
>     >
>     >
>     > --
>     >
>     > Piotr Zarzycki
>     >
>     > Patreon: https://www.patreon.com/piotrzarzycki
>     >
>
>
>     --
>
>     Piotr Zarzycki
>
>     Patreon: *https://www.patreon.com/piotrzarzycki
>     <https://www.patreon.com/piotrzarzycki>*
>
>
>

-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Releasing: Finally giving up

Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Piotr,

I would assume that ideally you would simply do a normal Maven release.

This will produce all the artifacts needed for an official Apache release and
also create and deploy the convenience binaries for Maven.

I would then suggest to use the source-bundle and run the Ant build inside 
it to produce the Ant convenience binary (SDK) from that.

Chris



Am 26.03.20, 13:43 schrieb "Piotr Zarzycki" <pi...@gmail.com>:

    Hi Chris,
    
    My end expectation is that I will be able to prepare RC1 by Maven, but also
    take care of ANT build - I'm not sure maybe it would be enough if ANT build
    will be launched by maven and produce IDE ready SDK - which could be tested
    in that way.
    
    Thanks,
    Piotr
    
    czw., 26 mar 2020 o 13:38 Christofer Dutz <ch...@c-ware.de>
    napisał(a):
    
    > Hi Piotr,
    >
    > generally the build is currently already in a state we should be able to
    > release Royale with Maven.
    > I intentionally put all the bells and whistles in a profile that you need
    > to activate “royale-release”.
    > If you don’t do that, it should be a normal Maven release.
    >
    > Chris
    >
    > Von: Piotr Zarzycki <pi...@gmail.com>
    > Antworten an: "dev@royale.apache.org" <de...@royale.apache.org>
    > Datum: Donnerstag, 26. März 2020 um 12:27
    > An: Apache Royale Development <de...@royale.apache.org>
    > Betreff: Re: Releasing: Finally giving up
    >
    > Hi All,
    >
    > I'm member of Apache Foundation for quite some time now. I think I have
    > wrote maybe 2-3 emails during that time on members mailing list. - Why? -
    > well I'm a person which doesn't like never ending stories, stories which
    > are not end up with consensus nor action and I'm sorry but this is how it
    > looks like in most cases there. Here we are in Apache Royale project where
    > this thread ended up exactly the same - never ending story. - As PMC of
    > this project I would like to say enough! :)
    >
    > I had hope that when Carlos and Chris try CI steps and in the process they
    > may have some issues, but they will end up in the same place as I ended up
    > where I was able to prepare RC1 in about 2h without the problem. It turns
    > out that they end up in the place where I have started, in the place where
    > I have spend 5-6 days of work to finally reach stable point. They ended up
    > frustrated in the same way as I was!
    >
    > I really don't care now what kind of issue they have now, whether it's
    > fixable or not - I just have enough of those never ending discussions where
    > there is absolutely no results.
    >
    > I met Chris in US in Miami and I have spend with him best time ever, he is
    > really great developer - if he is saying that he will have release process
    > in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not in a week
    > - start today!
    >
    > Please start whole work on that and make it happen. I will be the first
    > who try the process and maybe with Chris's help we will solve also issue
    > with uploading artifacts to staging area which we had.
    >
    > Good Luck,
    > Piotr
    >
    > czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
    > contact@cristallium.com>> napisał(a):
    >
    > Hi Guys,
    >
    > I'm a lover of Flex dev guy since more than 10 years, been members of Flex
    > group on Montpellier (France) at golden age of Flex and go at all
    > conferences when Michaël Chaize came to Montpellier (and using Flex every
    > day).
    >
    > First of all I want to thank every one of you for your hard work, and
    > congratulate you for the actual Apache Royale capabilities.
    > With the last features (especialy datagrid), today your great work make
    > possible to use Apache Royale in business application. Of course, there are
    > bugs, but when reported, it's quickly fix, this is great.
    >
    > Now, this is a huge opportunity but also risk for all guys like me to adop
    > Apache Royale for futur projects or use it instead of using Air when it's
    > possible.
    > Personnaly, I first use it on my own Webs applications and perhaps for my
    > customers on little applications for the begin. My big enormous worry is to
    > use it and be alone in front of a SDK bug.
    > Seeing new release every 1 or 2 months should certainly reassure me. For
    > now I see SDK 0.9.7 since a lot of time and this make me affraid and I
    > don't understand why there is no 0.9.8.
    >
    > I'm speaking as an Apache Royale SDK user : I'm very sad to read these
    > debates on the subject of tools to use for making release. I don't care
    > about tools nedeed or not to build the release SDK.
    > I would like use Apache Royale to build RAD (Rapid Application Dev) Web
    > applications and see more and more SDK features added, and participate to
    > project (like today) by reporting bug  by using my time on isolate the bug
    > and make tests cases with screenshoots to save your time in fixing it.
    >
    > Using Reac, Bootstrap, AngularJS or other similar is a back to 80's. How
    > can I explain my customer that I need 3 ou 4 days to make thinks that took
    > me 1 day with Flex ?
    > The big competitive advantage of Apache Royale is not only be able to
    > re-use Flex apps but is also simplicity and time saving where other SDK
    > can't do it. (I think you already know that)
    >
    > I am convinced that all guys like me will jump using Royale when they will
    > know that there is a bug free SDK with fast evolution available.
    > (unfortunaly it's not known enough, nobody know someone working in
    > newspapers ?)
    >
    > So please, I beg you, don't waste your time on things that are not
    > essential and like Carlos said, go forward. From outside view, Apache
    > Royale stay sticky to 0.9.7.
    >
    > You are so close of a v1.0, I hope see it very soon and other releases
    > with bugs fix every 1, 2 or 3 months.
    > Consider my comments as support and not criticism.
    >
    > Thanks again for your hard work.
    >
    > Long life and success to Apache Royale !
    >
    > Fred
    >
    >
    >
    > Le 26.03.2020 09:26, Carlos Rovira a écrit :
    > Hi,
    >
    > that's amazingly simple, so I think we should go that way without doubt. I
    > think reached this point there's a clear sense of that we need to go that
    > route.
    >
    > We tried our best to stick with the previous process and we're all
    > loosing lots of time. Then currently seems no more people in the community
    > was interested in this thread, event to comment a single line (here or in
    > the other users list thread), what means that or there's no more people
    > like us in this project or people really is not interested and just want us
    > to release and go forward.
    >
    > As previously I think most of the PMCs here (Om, Josh, Greg and me for
    > sure), probably Yishay for his concise comments are more for this.
    > My thinking is that the right now I think only 2 PMCs are for CI Server,
    > and other one that is uncertainly but didn't try the CI Server.
    >
    > I think all can live together while is not a must for the rest that don't
    > want it the others option, so what's about if we release with the
    > super-simple steps Chris proposal, and others wanting to use CI do that
    > when is their RM turn ? (of course maintaining it and making it work for
    > his release without requiring nothing for the rest that doesn't want it).
    >
    > Release as other projects do is recommended but not required, the same as
    > the actual CI server (but this one should be less recommended since is a
    > royale-only practice not seen in any other place).
    >
    > What's the important thing is to release, do it, and do it easily and
    > often.
    >
    > Thanks
    >
    >
    >
    > El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
    > christofer.dutz@c-ware.de<ma...@c-ware.de>>) escribió:
    >
    >
    > Ok,
    >
    > I'll write this a last time as I do feel like we're going in circles and
    > will from now on not participate in any discussion involving releasing on a
    > CI server.
    >
    > A correct Maven release would use (There will be some additional profiles
    > to activate to include all modules)
    >
    > 1) the "mvn release:branch" call in order to create the branch and bump
    > the version of develop to the next version.
    > 2) the "mvn release:prepare" to change the pom to the release version, set
    > the timestamp in the pom (for reproducible builds) build ... if all tests
    > are good, commit the changes, tag this commit, update the poms to the next
    > development version, commit those changes and push everything.
    > 3) the "mvn release:perform" which will checkout the tagged version build
    > everything with the "apache-release" profile turned on (Which causes the
    > source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
    > as the assembly) This also deploys the built artifacts to Nexus.
    >
    > Most of that you are already doing on the CI server however you're not
    > letting it do all automatically (For lack of credentials)
    >
    > But ... if you would just be doing those steps on the RM machine.
    >
    > Chris
    >
    >
    >
    >
    >
    > Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID<mailto:
    > aharui@adobe.com.INVALID>>:
    >
    >
    >
    >     On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org<mailto:
    > carlosrovira@apache.org>> wrote:
    >
    >         > What I want to know is what the Maven commands should be to
    > create a
    >         > release in this "conventional process" you are referring to.
    >         >
    >
    >         If you want to know what's the conventional maven process is, I
    > think I can
    >         ask Chris if he wants to work with me on that process, since he
    > already did
    >         many other Apache projects, we can expect the process is what is
    > needed for
    >         us to. But just expect that will be a series of standard maven
    > commands
    >         (prepare, release,...), so nothing strange at all (I expect).
    >
    >         Do you want us to do that?
    >
    >     Yes.  I want to know what the series of standard Maven commands are.
    > Then we can figure out how to convert them to run on the CI server.
    >
    >     -Alex
    >
    >         Thanks
    >
    >
    >         >
    >         > Maybe someone else can explain better than me.
    >         >
    >         > -Alex
    >         >
    >         > On 3/25/20, 2:22 PM, "Carlos Rovira" <carlosrovira@apache.org
    > <ma...@apache.org>>
    > wrote:
    >         >
    >         >     Hi Alex,
    >         >
    >         >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
    >         > (<ah...@adobe.com.invalid>>)
    >         >     escribió:
    >         >
    >         >     > Carlos,
    >         >     >
    >         >     > I'm pretty sure that part of the "conventional process"
    > you want to
    >         > try
    >         >     > requires filling the staging repo from a local machine.
    >         >     >
    >         >
    >         >     This is what we already did. If you go to [1] will see [2].
    > That was
    >         > the
    >         >     upload of compiler to the staging repo. When trying to do
    > the same for
    >         >     typedefs it failed when trying to fill repo from local
    > machine. I think
    >         >     Chris or I should not take more time in trying to fix Ant
    > scripts that
    >         > are
    >         >     failing.
    >         >
    >         >     Thanks
    >         >
    >         >     [1]
    >         >
    >
    > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
    >         >     [2]
    >         >
    >
    > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
    >         >
    >         >
    >         >
    >         >
    >         >     >
    >         >     > --
    >         >     > Carlos Rovira
    >         >     >
    >         >
    >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
    >         >     >
    >         >     >
    >         >     >
    >         >     >
    >         >
    >         >
    >         >
    >
    >         --
    >         Carlos Rovira
    >
    >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
    >
    >
    >
    >
    >
    >
    > --
    >
    > Frédéric Gilli
    >
    > mob.0668542622
    >
    > http://www.cristallium.com
    >
    > [cid:171168797bb6addd0331]<http://www.cristallium.com/>
    >
    >
    >
    >
    > --
    >
    > Piotr Zarzycki
    >
    > Patreon: https://www.patreon.com/piotrzarzycki
    >
    
    
    -- 
    
    Piotr Zarzycki
    
    Patreon: *https://www.patreon.com/piotrzarzycki
    <https://www.patreon.com/piotrzarzycki>*
    


Re: Releasing: Finally giving up

Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Chris,

My end expectation is that I will be able to prepare RC1 by Maven, but also
take care of ANT build - I'm not sure maybe it would be enough if ANT build
will be launched by maven and produce IDE ready SDK - which could be tested
in that way.

Thanks,
Piotr

czw., 26 mar 2020 o 13:38 Christofer Dutz <ch...@c-ware.de>
napisał(a):

> Hi Piotr,
>
> generally the build is currently already in a state we should be able to
> release Royale with Maven.
> I intentionally put all the bells and whistles in a profile that you need
> to activate “royale-release”.
> If you don’t do that, it should be a normal Maven release.
>
> Chris
>
> Von: Piotr Zarzycki <pi...@gmail.com>
> Antworten an: "dev@royale.apache.org" <de...@royale.apache.org>
> Datum: Donnerstag, 26. März 2020 um 12:27
> An: Apache Royale Development <de...@royale.apache.org>
> Betreff: Re: Releasing: Finally giving up
>
> Hi All,
>
> I'm member of Apache Foundation for quite some time now. I think I have
> wrote maybe 2-3 emails during that time on members mailing list. - Why? -
> well I'm a person which doesn't like never ending stories, stories which
> are not end up with consensus nor action and I'm sorry but this is how it
> looks like in most cases there. Here we are in Apache Royale project where
> this thread ended up exactly the same - never ending story. - As PMC of
> this project I would like to say enough! :)
>
> I had hope that when Carlos and Chris try CI steps and in the process they
> may have some issues, but they will end up in the same place as I ended up
> where I was able to prepare RC1 in about 2h without the problem. It turns
> out that they end up in the place where I have started, in the place where
> I have spend 5-6 days of work to finally reach stable point. They ended up
> frustrated in the same way as I was!
>
> I really don't care now what kind of issue they have now, whether it's
> fixable or not - I just have enough of those never ending discussions where
> there is absolutely no results.
>
> I met Chris in US in Miami and I have spend with him best time ever, he is
> really great developer - if he is saying that he will have release process
> in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not in a week
> - start today!
>
> Please start whole work on that and make it happen. I will be the first
> who try the process and maybe with Chris's help we will solve also issue
> with uploading artifacts to staging area which we had.
>
> Good Luck,
> Piotr
>
> czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> contact@cristallium.com>> napisał(a):
>
> Hi Guys,
>
> I'm a lover of Flex dev guy since more than 10 years, been members of Flex
> group on Montpellier (France) at golden age of Flex and go at all
> conferences when Michaël Chaize came to Montpellier (and using Flex every
> day).
>
> First of all I want to thank every one of you for your hard work, and
> congratulate you for the actual Apache Royale capabilities.
> With the last features (especialy datagrid), today your great work make
> possible to use Apache Royale in business application. Of course, there are
> bugs, but when reported, it's quickly fix, this is great.
>
> Now, this is a huge opportunity but also risk for all guys like me to adop
> Apache Royale for futur projects or use it instead of using Air when it's
> possible.
> Personnaly, I first use it on my own Webs applications and perhaps for my
> customers on little applications for the begin. My big enormous worry is to
> use it and be alone in front of a SDK bug.
> Seeing new release every 1 or 2 months should certainly reassure me. For
> now I see SDK 0.9.7 since a lot of time and this make me affraid and I
> don't understand why there is no 0.9.8.
>
> I'm speaking as an Apache Royale SDK user : I'm very sad to read these
> debates on the subject of tools to use for making release. I don't care
> about tools nedeed or not to build the release SDK.
> I would like use Apache Royale to build RAD (Rapid Application Dev) Web
> applications and see more and more SDK features added, and participate to
> project (like today) by reporting bug  by using my time on isolate the bug
> and make tests cases with screenshoots to save your time in fixing it.
>
> Using Reac, Bootstrap, AngularJS or other similar is a back to 80's. How
> can I explain my customer that I need 3 ou 4 days to make thinks that took
> me 1 day with Flex ?
> The big competitive advantage of Apache Royale is not only be able to
> re-use Flex apps but is also simplicity and time saving where other SDK
> can't do it. (I think you already know that)
>
> I am convinced that all guys like me will jump using Royale when they will
> know that there is a bug free SDK with fast evolution available.
> (unfortunaly it's not known enough, nobody know someone working in
> newspapers ?)
>
> So please, I beg you, don't waste your time on things that are not
> essential and like Carlos said, go forward. From outside view, Apache
> Royale stay sticky to 0.9.7.
>
> You are so close of a v1.0, I hope see it very soon and other releases
> with bugs fix every 1, 2 or 3 months.
> Consider my comments as support and not criticism.
>
> Thanks again for your hard work.
>
> Long life and success to Apache Royale !
>
> Fred
>
>
>
> Le 26.03.2020 09:26, Carlos Rovira a écrit :
> Hi,
>
> that's amazingly simple, so I think we should go that way without doubt. I
> think reached this point there's a clear sense of that we need to go that
> route.
>
> We tried our best to stick with the previous process and we're all
> loosing lots of time. Then currently seems no more people in the community
> was interested in this thread, event to comment a single line (here or in
> the other users list thread), what means that or there's no more people
> like us in this project or people really is not interested and just want us
> to release and go forward.
>
> As previously I think most of the PMCs here (Om, Josh, Greg and me for
> sure), probably Yishay for his concise comments are more for this.
> My thinking is that the right now I think only 2 PMCs are for CI Server,
> and other one that is uncertainly but didn't try the CI Server.
>
> I think all can live together while is not a must for the rest that don't
> want it the others option, so what's about if we release with the
> super-simple steps Chris proposal, and others wanting to use CI do that
> when is their RM turn ? (of course maintaining it and making it work for
> his release without requiring nothing for the rest that doesn't want it).
>
> Release as other projects do is recommended but not required, the same as
> the actual CI server (but this one should be less recommended since is a
> royale-only practice not seen in any other place).
>
> What's the important thing is to release, do it, and do it easily and
> often.
>
> Thanks
>
>
>
> El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
> christofer.dutz@c-ware.de<ma...@c-ware.de>>) escribió:
>
>
> Ok,
>
> I'll write this a last time as I do feel like we're going in circles and
> will from now on not participate in any discussion involving releasing on a
> CI server.
>
> A correct Maven release would use (There will be some additional profiles
> to activate to include all modules)
>
> 1) the "mvn release:branch" call in order to create the branch and bump
> the version of develop to the next version.
> 2) the "mvn release:prepare" to change the pom to the release version, set
> the timestamp in the pom (for reproducible builds) build ... if all tests
> are good, commit the changes, tag this commit, update the poms to the next
> development version, commit those changes and push everything.
> 3) the "mvn release:perform" which will checkout the tagged version build
> everything with the "apache-release" profile turned on (Which causes the
> source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
> as the assembly) This also deploys the built artifacts to Nexus.
>
> Most of that you are already doing on the CI server however you're not
> letting it do all automatically (For lack of credentials)
>
> But ... if you would just be doing those steps on the RM machine.
>
> Chris
>
>
>
>
>
> Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID<mailto:
> aharui@adobe.com.INVALID>>:
>
>
>
>     On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org<mailto:
> carlosrovira@apache.org>> wrote:
>
>         > What I want to know is what the Maven commands should be to
> create a
>         > release in this "conventional process" you are referring to.
>         >
>
>         If you want to know what's the conventional maven process is, I
> think I can
>         ask Chris if he wants to work with me on that process, since he
> already did
>         many other Apache projects, we can expect the process is what is
> needed for
>         us to. But just expect that will be a series of standard maven
> commands
>         (prepare, release,...), so nothing strange at all (I expect).
>
>         Do you want us to do that?
>
>     Yes.  I want to know what the series of standard Maven commands are.
> Then we can figure out how to convert them to run on the CI server.
>
>     -Alex
>
>         Thanks
>
>
>         >
>         > Maybe someone else can explain better than me.
>         >
>         > -Alex
>         >
>         > On 3/25/20, 2:22 PM, "Carlos Rovira" <carlosrovira@apache.org
> <ma...@apache.org>>
> wrote:
>         >
>         >     Hi Alex,
>         >
>         >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>         > (<ah...@adobe.com.invalid>>)
>         >     escribió:
>         >
>         >     > Carlos,
>         >     >
>         >     > I'm pretty sure that part of the "conventional process"
> you want to
>         > try
>         >     > requires filling the staging repo from a local machine.
>         >     >
>         >
>         >     This is what we already did. If you go to [1] will see [2].
> That was
>         > the
>         >     upload of compiler to the staging repo. When trying to do
> the same for
>         >     typedefs it failed when trying to fill repo from local
> machine. I think
>         >     Chris or I should not take more time in trying to fix Ant
> scripts that
>         > are
>         >     failing.
>         >
>         >     Thanks
>         >
>         >     [1]
>         >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
>         >     [2]
>         >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
>         >
>         >
>         >
>         >
>         >     >
>         >     > --
>         >     > Carlos Rovira
>         >     >
>         >
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>         >     >
>         >     >
>         >     >
>         >     >
>         >
>         >
>         >
>
>         --
>         Carlos Rovira
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>
>
>
>
>
>
> --
>
> Frédéric Gilli
>
> mob.0668542622
>
> http://www.cristallium.com
>
> [cid:171168797bb6addd0331]<http://www.cristallium.com/>
>
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: https://www.patreon.com/piotrzarzycki
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Releasing: Finally giving up

Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Piotr,

generally the build is currently already in a state we should be able to release Royale with Maven.
I intentionally put all the bells and whistles in a profile that you need to activate “royale-release”.
If you don’t do that, it should be a normal Maven release.

Chris

Von: Piotr Zarzycki <pi...@gmail.com>
Antworten an: "dev@royale.apache.org" <de...@royale.apache.org>
Datum: Donnerstag, 26. März 2020 um 12:27
An: Apache Royale Development <de...@royale.apache.org>
Betreff: Re: Releasing: Finally giving up

Hi All,

I'm member of Apache Foundation for quite some time now. I think I have wrote maybe 2-3 emails during that time on members mailing list. - Why? - well I'm a person which doesn't like never ending stories, stories which are not end up with consensus nor action and I'm sorry but this is how it looks like in most cases there. Here we are in Apache Royale project where this thread ended up exactly the same - never ending story. - As PMC of this project I would like to say enough! :)

I had hope that when Carlos and Chris try CI steps and in the process they may have some issues, but they will end up in the same place as I ended up where I was able to prepare RC1 in about 2h without the problem. It turns out that they end up in the place where I have started, in the place where I have spend 5-6 days of work to finally reach stable point. They ended up frustrated in the same way as I was!

I really don't care now what kind of issue they have now, whether it's fixable or not - I just have enough of those never ending discussions where there is absolutely no results.

I met Chris in US in Miami and I have spend with him best time ever, he is really great developer - if he is saying that he will have release process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not in a week - start today!

Please start whole work on that and make it happen. I will be the first who try the process and maybe with Chris's help we will solve also issue with uploading artifacts to staging area which we had.

Good Luck,
Piotr

czw., 26 mar 2020 o 12:02 <co...@cristallium.com>> napisał(a):

Hi Guys,

I'm a lover of Flex dev guy since more than 10 years, been members of Flex group on Montpellier (France) at golden age of Flex and go at all conferences when Michaël Chaize came to Montpellier (and using Flex every day).

First of all I want to thank every one of you for your hard work, and congratulate you for the actual Apache Royale capabilities.
With the last features (especialy datagrid), today your great work make possible to use Apache Royale in business application. Of course, there are bugs, but when reported, it's quickly fix, this is great.

Now, this is a huge opportunity but also risk for all guys like me to adop Apache Royale for futur projects or use it instead of using Air when it's possible.
Personnaly, I first use it on my own Webs applications and perhaps for my customers on little applications for the begin. My big enormous worry is to use it and be alone in front of a SDK bug.
Seeing new release every 1 or 2 months should certainly reassure me. For now I see SDK 0.9.7 since a lot of time and this make me affraid and I don't understand why there is no 0.9.8.

I'm speaking as an Apache Royale SDK user : I'm very sad to read these debates on the subject of tools to use for making release. I don't care about tools nedeed or not to build the release SDK.
I would like use Apache Royale to build RAD (Rapid Application Dev) Web applications and see more and more SDK features added, and participate to project (like today) by reporting bug  by using my time on isolate the bug and make tests cases with screenshoots to save your time in fixing it.

Using Reac, Bootstrap, AngularJS or other similar is a back to 80's. How can I explain my customer that I need 3 ou 4 days to make thinks that took me 1 day with Flex ?
The big competitive advantage of Apache Royale is not only be able to re-use Flex apps but is also simplicity and time saving where other SDK can't do it. (I think you already know that)

I am convinced that all guys like me will jump using Royale when they will know that there is a bug free SDK with fast evolution available. (unfortunaly it's not known enough, nobody know someone working in newspapers ?)

So please, I beg you, don't waste your time on things that are not essential and like Carlos said, go forward. From outside view, Apache Royale stay sticky to 0.9.7.

You are so close of a v1.0, I hope see it very soon and other releases with bugs fix every 1, 2 or 3 months.
Consider my comments as support and not criticism.

Thanks again for your hard work.

Long life and success to Apache Royale !

Fred



Le 26.03.2020 09:26, Carlos Rovira a écrit :
Hi,

that's amazingly simple, so I think we should go that way without doubt. I
think reached this point there's a clear sense of that we need to go that
route.

We tried our best to stick with the previous process and we're all
loosing lots of time. Then currently seems no more people in the community
was interested in this thread, event to comment a single line (here or in
the other users list thread), what means that or there's no more people
like us in this project or people really is not interested and just want us
to release and go forward.

As previously I think most of the PMCs here (Om, Josh, Greg and me for
sure), probably Yishay for his concise comments are more for this.
My thinking is that the right now I think only 2 PMCs are for CI Server,
and other one that is uncertainly but didn't try the CI Server.

I think all can live together while is not a must for the rest that don't
want it the others option, so what's about if we release with the
super-simple steps Chris proposal, and others wanting to use CI do that
when is their RM turn ? (of course maintaining it and making it work for
his release without requiring nothing for the rest that doesn't want it).

Release as other projects do is recommended but not required, the same as
the actual CI server (but this one should be less recommended since is a
royale-only practice not seen in any other place).

What's the important thing is to release, do it, and do it easily and often.

Thanks



El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
christofer.dutz@c-ware.de<ma...@c-ware.de>>) escribió:


Ok,

I'll write this a last time as I do feel like we're going in circles and
will from now on not participate in any discussion involving releasing on a
CI server.

A correct Maven release would use (There will be some additional profiles
to activate to include all modules)

1) the "mvn release:branch" call in order to create the branch and bump
the version of develop to the next version.
2) the "mvn release:prepare" to change the pom to the release version, set
the timestamp in the pom (for reproducible builds) build ... if all tests
are good, commit the changes, tag this commit, update the poms to the next
development version, commit those changes and push everything.
3) the "mvn release:perform" which will checkout the tagged version build
everything with the "apache-release" profile turned on (Which causes the
source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
as the assembly) This also deploys the built artifacts to Nexus.

Most of that you are already doing on the CI server however you're not
letting it do all automatically (For lack of credentials)

But ... if you would just be doing those steps on the RM machine.

Chris





Am 26.03.20, 05:54 schrieb "Alex Harui" <ah...@adobe.com.INVALID>>:



    On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org>> wrote:

        > What I want to know is what the Maven commands should be to
create a
        > release in this "conventional process" you are referring to.
        >

        If you want to know what's the conventional maven process is, I
think I can
        ask Chris if he wants to work with me on that process, since he
already did
        many other Apache projects, we can expect the process is what is
needed for
        us to. But just expect that will be a series of standard maven
commands
        (prepare, release,...), so nothing strange at all (I expect).

        Do you want us to do that?

    Yes.  I want to know what the series of standard Maven commands are.
Then we can figure out how to convert them to run on the CI server.

    -Alex

        Thanks


        >
        > Maybe someone else can explain better than me.
        >
        > -Alex
        >
        > On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org>>
wrote:
        >
        >     Hi Alex,
        >
        >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
        > (<ah...@adobe.com.invalid>>)
        >     escribió:
        >
        >     > Carlos,
        >     >
        >     > I'm pretty sure that part of the "conventional process"
you want to
        > try
        >     > requires filling the staging repo from a local machine.
        >     >
        >
        >     This is what we already did. If you go to [1] will see [2].
That was
        > the
        >     upload of compiler to the staging repo. When trying to do
the same for
        >     typedefs it failed when trying to fill repo from local
machine. I think
        >     Chris or I should not take more time in trying to fix Ant
scripts that
        > are
        >     failing.
        >
        >     Thanks
        >
        >     [1]
        >
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
        >     [2]
        >
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
        >
        >
        >
        >
        >     >
        >     > --
        >     > Carlos Rovira
        >     >
        >
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
        >     >
        >     >
        >     >
        >     >
        >
        >
        >

        --
        Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0






--

Frédéric Gilli

mob.0668542622

http://www.cristallium.com

[cid:171168797bb6addd0331]<http://www.cristallium.com/>




--

Piotr Zarzycki

Patreon: https://www.patreon.com/piotrzarzycki

Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
ok Yishay, thanks!

El vie., 27 mar. 2020 a las 9:57, Yishay Weiss (<yi...@hotmail.com>)
escribió:

> No objections from me.
>
> ________________________________
> From: Carlos Rovira <ca...@apache.org>
> Sent: Friday, March 27, 2020 11:47:24 AM
> To: Apache Royale Development <de...@royale.apache.org>
> Subject: Re: Releasing: Finally giving up
>
> Hi Alex
>
> thanks. I want to ask first Yishay since he took over. If he doesn't object
> anything we can do it.
>
>
> El jue., 26 mar. 2020 a las 19:50, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
> > @Yishay Weiss
> >
> > Let's wait until the set of Maven steps are available from Chris and
> > Carlos.  Then I will try to find some cycles to help you.  Because of
> where
> > I live, where the schools are closed, and my kids schedule, I have good
> > weeks and bad weeks for having time for work, so it will be best to wait
> to
> > try a release until we have the steps and it is one of my good weeks
> (next
> > good week starts this Friday at 5pm my time).
> >
> > Thanks,
> > -Alex
> >
> > On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> >     Hi All,
> >
> >     I too, feel very uncomfortable participating in these threads. While
> > grateful to Carlos and Chris for their work I’m very annoyed with the
> tone
> > of ultimatums and doom and gloom. Alex has put in a lot of work into this
> > and I trust his concerns are technical, rather than protecting his ego as
> > has been suggested. We need to get this discussion back on technical
> tracks.
> >
> >     Since Chris has given up, and it looks like Carlos has as well, I
> > volunteer to start the release process from scratch next Sunday, which is
> > after Israel has switched to day light saving. I will try to do the
> process
> > incrementally and in parallel to my other tasks. If by the end of the
> week
> > it turns out the process is too cumbersome and cannot realistically be
> made
> > to work smoothly I will be in favor of changing the requirements to
> enable
> > Chris’s mvn setup to be the main release tool.
> >
> >     Thanks,
> >     Yishay
> >
> >     From: Piotr Zarzycki<ma...@gmail.com>
> >     Sent: Thursday, March 26, 2020 1:27 PM
> >     To: Apache Royale Development<ma...@royale.apache.org>
> >     Subject: Re: Releasing: Finally giving up
> >
> >     Hi All,
> >
> >     I'm member of Apache Foundation for quite some time now. I think I
> > have wrote maybe 2-3 emails during that time on members mailing list. -
> > Why? - well I'm a person which doesn't like never ending stories, stories
> > which are not end up with consensus nor action and I'm sorry but this is
> > how it looks like in most cases there. Here we are in Apache Royale
> project
> > where this thread ended up exactly the same - never ending story. - As
> PMC
> > of this project I would like to say enough! :)
> >
> >     I had hope that when Carlos and Chris try CI steps and in the process
> > they may have some issues, but they will end up in the same place as I
> > ended up where I was able to prepare RC1 in about 2h without the problem.
> > It turns out that they end up in the place where I have started, in the
> > place where I have spend 5-6 days of work to finally reach stable point.
> > They ended up frustrated in the same way as I was!
> >
> >     I really don't care now what kind of issue they have now, whether
> it's
> > fixable or not - I just have enough of those never ending discussions
> where
> > there is absolutely no results.
> >
> >     I met Chris in US in Miami and I have spend with him best time ever,
> > he is really great developer - if he is saying that he will have release
> > process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not
> > in a week - start today!
> >
> >     Please start whole work on that and make it happen. I will be the
> > first who try the process and maybe with Chris's help we will solve also
> > issue with uploading artifacts to staging area which we had.
> >
> >     Good Luck,
> >     Piotr
> >
> >     czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> > contact@cristallium.com>> napisał(a):
> >
> >     Hi Guys,
> >
> >     I'm a lover of Flex dev guy since more than 10 years, been members of
> > Flex group on Montpellier (France) at golden age of Flex and go at all
> > conferences when Michaël Chaize came to Montpellier (and using Flex every
> > day).
> >
> >     First of all I want to thank every one of you for your hard work, and
> > congratulate you for the actual Apache Royale capabilities.
> >     With the last features (especialy datagrid), today your great work
> > make possible to use Apache Royale in business application. Of course,
> > there are bugs, but when reported, it's quickly fix, this is great.
> >
> >     Now, this is a huge opportunity but also risk for all guys like me to
> > adop Apache Royale for futur projects or use it instead of using Air when
> > it's possible.
> >     Personnaly, I first use it on my own Webs applications and perhaps
> for
> > my customers on little applications for the begin. My big enormous worry
> is
> > to use it and be alone in front of a SDK bug.
> >     Seeing new release every 1 or 2 months should certainly reassure me.
> > For now I see SDK 0.9.7 since a lot of time and this make me affraid and
> I
> > don't understand why there is no 0.9.8.
> >
> >     I'm speaking as an Apache Royale SDK user : I'm very sad to read
> these
> > debates on the subject of tools to use for making release. I don't care
> > about tools nedeed or not to build the release SDK.
> >     I would like use Apache Royale to build RAD (Rapid Application Dev)
> > Web applications and see more and more SDK features added, and
> participate
> > to project (like today) by reporting bug  by using my time on isolate the
> > bug and make tests cases with screenshoots to save your time in fixing
> it.
> >
> >     Using Reac, Bootstrap, AngularJS or other similar is a back to 80's.
> > How can I explain my customer that I need 3 ou 4 days to make thinks that
> > took me 1 day with Flex ?
> >     The big competitive advantage of Apache Royale is not only be able to
> > re-use Flex apps but is also simplicity and time saving where other SDK
> > can't do it. (I think you already know that)
> >
> >     I am convinced that all guys like me will jump using Royale when they
> > will know that there is a bug free SDK with fast evolution available.
> > (unfortunaly it's not known enough, nobody know someone working in
> > newspapers ?)
> >
> >     So please, I beg you, don't waste your time on things that are not
> > essential and like Carlos said, go forward. From outside view, Apache
> > Royale stay sticky to 0.9.7.
> >
> >     You are so close of a v1.0, I hope see it very soon and other
> releases
> > with bugs fix every 1, 2 or 3 months.
> >     Consider my comments as support and not criticism.
> >
> >     Thanks again for your hard work.
> >
> >     Long life and success to Apache Royale !
> >
> >     Fred
> >
> >
> >
> >     Le 26.03.2020 09:26, Carlos Rovira a écrit :
> >     Hi,
> >
> >     that's amazingly simple, so I think we should go that way without
> > doubt. I
> >     think reached this point there's a clear sense of that we need to go
> > that
> >     route.
> >
> >     We tried our best to stick with the previous process and we're all
> >     loosing lots of time. Then currently seems no more people in the
> > community
> >     was interested in this thread, event to comment a single line (here
> or
> > in
> >     the other users list thread), what means that or there's no more
> people
> >     like us in this project or people really is not interested and just
> > want us
> >     to release and go forward.
> >
> >     As previously I think most of the PMCs here (Om, Josh, Greg and me
> for
> >     sure), probably Yishay for his concise comments are more for this.
> >     My thinking is that the right now I think only 2 PMCs are for CI
> > Server,
> >     and other one that is uncertainly but didn't try the CI Server.
> >
> >     I think all can live together while is not a must for the rest that
> > don't
> >     want it the others option, so what's about if we release with the
> >     super-simple steps Chris proposal, and others wanting to use CI do
> that
> >     when is their RM turn ? (of course maintaining it and making it work
> > for
> >     his release without requiring nothing for the rest that doesn't want
> > it).
> >
> >     Release as other projects do is recommended but not required, the
> same
> > as
> >     the actual CI server (but this one should be less recommended since
> is
> > a
> >     royale-only practice not seen in any other place).
> >
> >     What's the important thing is to release, do it, and do it easily and
> > often.
> >
> >     Thanks
> >
> >
> >
> >     El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
> >     christofer.dutz@c-ware.de<ma...@c-ware.de>>)
> > escribió:
> >
> >
> >     Ok,
> >
> >     I'll write this a last time as I do feel like we're going in circles
> > and
> >     will from now on not participate in any discussion involving
> releasing
> > on a
> >     CI server.
> >
> >     A correct Maven release would use (There will be some additional
> > profiles
> >     to activate to include all modules)
> >
> >     1) the "mvn release:branch" call in order to create the branch and
> bump
> >     the version of develop to the next version.
> >     2) the "mvn release:prepare" to change the pom to the release
> version,
> > set
> >     the timestamp in the pom (for reproducible builds) build ... if all
> > tests
> >     are good, commit the changes, tag this commit, update the poms to the
> > next
> >     development version, commit those changes and push everything.
> >     3) the "mvn release:perform" which will checkout the tagged version
> > build
> >     everything with the "apache-release" profile turned on (Which causes
> > the
> >     source.jars, Javadoc.jars, hashes and gpg singatures to be created as
> > well
> >     as the assembly) This also deploys the built artifacts to Nexus.
> >
> >     Most of that you are already doing on the CI server however you're
> not
> >     letting it do all automatically (For lack of credentials)
> >
> >     But ... if you would just be doing those steps on the RM machine.
> >
> >     Chris
> >
> >
> >
> >
> >
> >     Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
> > <ma...@adobe.com.INVALID>>:
> >
> >
> >
> >         On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org
> > <ma...@apache.org>> wrote:
> >
> >             > What I want to know is what the Maven commands should be to
> >     create a
> >             > release in this "conventional process" you are referring
> to.
> >             >
> >
> >             If you want to know what's the conventional maven process
> is, I
> >     think I can
> >             ask Chris if he wants to work with me on that process, since
> he
> >     already did
> >             many other Apache projects, we can expect the process is what
> > is
> >     needed for
> >             us to. But just expect that will be a series of standard
> maven
> >     commands
> >             (prepare, release,...), so nothing strange at all (I expect).
> >
> >             Do you want us to do that?
> >
> >         Yes.  I want to know what the series of standard Maven commands
> > are.
> >     Then we can figure out how to convert them to run on the CI server.
> >
> >         -Alex
> >
> >             Thanks
> >
> >
> >             >
> >             > Maybe someone else can explain better than me.
> >             >
> >             > -Alex
> >             >
> >             > On 3/25/20, 2:22 PM, "Carlos Rovira" <
> > carlosrovira@apache.org<ma...@apache.org>>
> >     wrote:
> >             >
> >             >     Hi Alex,
> >             >
> >             >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
> >             > (<aharui@adobe.com.invalid<mailto:aharui@adobe.com.invalid
> > >>)
> >             >     escribió:
> >             >
> >             >     > Carlos,
> >             >     >
> >             >     > I'm pretty sure that part of the "conventional
> process"
> >     you want to
> >             > try
> >             >     > requires filling the staging repo from a local
> machine.
> >             >     >
> >             >
> >             >     This is what we already did. If you go to [1] will see
> > [2].
> >     That was
> >             > the
> >             >     upload of compiler to the staging repo. When trying to
> do
> >     the same for
> >             >     typedefs it failed when trying to fill repo from local
> >     machine. I think
> >             >     Chris or I should not take more time in trying to fix
> Ant
> >     scripts that
> >             > are
> >             >     failing.
> >             >
> >             >     Thanks
> >             >
> >             >     [1]
> >             >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=SzmPqflLUwAxBCIkm%2BFn2BO8OZVJH1Gp66CVl349I3g%3D&amp;reserved=0
> >             >     [2]
> >             >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=VONdkWMhQpEGhSlVoXwFuhdnApXmrSaTnSP%2FDeH6stc%3D&amp;reserved=0
> >             >
> >             >
> >             >
> >             >
> >             >     >
> >             >     > --
> >             >     > Carlos Rovira
> >             >     >
> >             >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=jPUGE0ohIi%2BFYoKZefaob1pSsIjC4AEEjE04N27FiI0%3D&amp;reserved=0
> >             >     >
> >             >     >
> >             >     >
> >             >     >
> >             >
> >             >
> >             >
> >
> >             --
> >             Carlos Rovira
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=bkaODFbcmtjdxlibVdfQRKtIzcXImHIQ4HpKQOTgLM8%3D&amp;reserved=0
> >
> >
> >
> >
> >
> >
> >     --
> >
> >     Frédéric Gilli
> >
> >     mob.0668542622
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
> >
> >     [cid:171168797bb6addd0331]<
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
> > >
> >
> >
> >
> >
> >     --
> >
> >     Piotr Zarzycki
> >
> >     Patreon:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=j%2BLcn3n8gF9Ro8d0S5EgcHamMg42sVnJXBymeIeQEUk%3D&amp;reserved=0
> >
> >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


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

RE: Releasing: Finally giving up

Posted by Yishay Weiss <yi...@hotmail.com>.
No objections from me.

________________________________
From: Carlos Rovira <ca...@apache.org>
Sent: Friday, March 27, 2020 11:47:24 AM
To: Apache Royale Development <de...@royale.apache.org>
Subject: Re: Releasing: Finally giving up

Hi Alex

thanks. I want to ask first Yishay since he took over. If he doesn't object
anything we can do it.


El jue., 26 mar. 2020 a las 19:50, Alex Harui (<ah...@adobe.com.invalid>)
escribió:

> @Yishay Weiss
>
> Let's wait until the set of Maven steps are available from Chris and
> Carlos.  Then I will try to find some cycles to help you.  Because of where
> I live, where the schools are closed, and my kids schedule, I have good
> weeks and bad weeks for having time for work, so it will be best to wait to
> try a release until we have the steps and it is one of my good weeks (next
> good week starts this Friday at 5pm my time).
>
> Thanks,
> -Alex
>
> On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
>     Hi All,
>
>     I too, feel very uncomfortable participating in these threads. While
> grateful to Carlos and Chris for their work I’m very annoyed with the tone
> of ultimatums and doom and gloom. Alex has put in a lot of work into this
> and I trust his concerns are technical, rather than protecting his ego as
> has been suggested. We need to get this discussion back on technical tracks.
>
>     Since Chris has given up, and it looks like Carlos has as well, I
> volunteer to start the release process from scratch next Sunday, which is
> after Israel has switched to day light saving. I will try to do the process
> incrementally and in parallel to my other tasks. If by the end of the week
> it turns out the process is too cumbersome and cannot realistically be made
> to work smoothly I will be in favor of changing the requirements to enable
> Chris’s mvn setup to be the main release tool.
>
>     Thanks,
>     Yishay
>
>     From: Piotr Zarzycki<ma...@gmail.com>
>     Sent: Thursday, March 26, 2020 1:27 PM
>     To: Apache Royale Development<ma...@royale.apache.org>
>     Subject: Re: Releasing: Finally giving up
>
>     Hi All,
>
>     I'm member of Apache Foundation for quite some time now. I think I
> have wrote maybe 2-3 emails during that time on members mailing list. -
> Why? - well I'm a person which doesn't like never ending stories, stories
> which are not end up with consensus nor action and I'm sorry but this is
> how it looks like in most cases there. Here we are in Apache Royale project
> where this thread ended up exactly the same - never ending story. - As PMC
> of this project I would like to say enough! :)
>
>     I had hope that when Carlos and Chris try CI steps and in the process
> they may have some issues, but they will end up in the same place as I
> ended up where I was able to prepare RC1 in about 2h without the problem.
> It turns out that they end up in the place where I have started, in the
> place where I have spend 5-6 days of work to finally reach stable point.
> They ended up frustrated in the same way as I was!
>
>     I really don't care now what kind of issue they have now, whether it's
> fixable or not - I just have enough of those never ending discussions where
> there is absolutely no results.
>
>     I met Chris in US in Miami and I have spend with him best time ever,
> he is really great developer - if he is saying that he will have release
> process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not
> in a week - start today!
>
>     Please start whole work on that and make it happen. I will be the
> first who try the process and maybe with Chris's help we will solve also
> issue with uploading artifacts to staging area which we had.
>
>     Good Luck,
>     Piotr
>
>     czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> contact@cristallium.com>> napisał(a):
>
>     Hi Guys,
>
>     I'm a lover of Flex dev guy since more than 10 years, been members of
> Flex group on Montpellier (France) at golden age of Flex and go at all
> conferences when Michaël Chaize came to Montpellier (and using Flex every
> day).
>
>     First of all I want to thank every one of you for your hard work, and
> congratulate you for the actual Apache Royale capabilities.
>     With the last features (especialy datagrid), today your great work
> make possible to use Apache Royale in business application. Of course,
> there are bugs, but when reported, it's quickly fix, this is great.
>
>     Now, this is a huge opportunity but also risk for all guys like me to
> adop Apache Royale for futur projects or use it instead of using Air when
> it's possible.
>     Personnaly, I first use it on my own Webs applications and perhaps for
> my customers on little applications for the begin. My big enormous worry is
> to use it and be alone in front of a SDK bug.
>     Seeing new release every 1 or 2 months should certainly reassure me.
> For now I see SDK 0.9.7 since a lot of time and this make me affraid and I
> don't understand why there is no 0.9.8.
>
>     I'm speaking as an Apache Royale SDK user : I'm very sad to read these
> debates on the subject of tools to use for making release. I don't care
> about tools nedeed or not to build the release SDK.
>     I would like use Apache Royale to build RAD (Rapid Application Dev)
> Web applications and see more and more SDK features added, and participate
> to project (like today) by reporting bug  by using my time on isolate the
> bug and make tests cases with screenshoots to save your time in fixing it.
>
>     Using Reac, Bootstrap, AngularJS or other similar is a back to 80's.
> How can I explain my customer that I need 3 ou 4 days to make thinks that
> took me 1 day with Flex ?
>     The big competitive advantage of Apache Royale is not only be able to
> re-use Flex apps but is also simplicity and time saving where other SDK
> can't do it. (I think you already know that)
>
>     I am convinced that all guys like me will jump using Royale when they
> will know that there is a bug free SDK with fast evolution available.
> (unfortunaly it's not known enough, nobody know someone working in
> newspapers ?)
>
>     So please, I beg you, don't waste your time on things that are not
> essential and like Carlos said, go forward. From outside view, Apache
> Royale stay sticky to 0.9.7.
>
>     You are so close of a v1.0, I hope see it very soon and other releases
> with bugs fix every 1, 2 or 3 months.
>     Consider my comments as support and not criticism.
>
>     Thanks again for your hard work.
>
>     Long life and success to Apache Royale !
>
>     Fred
>
>
>
>     Le 26.03.2020 09:26, Carlos Rovira a écrit :
>     Hi,
>
>     that's amazingly simple, so I think we should go that way without
> doubt. I
>     think reached this point there's a clear sense of that we need to go
> that
>     route.
>
>     We tried our best to stick with the previous process and we're all
>     loosing lots of time. Then currently seems no more people in the
> community
>     was interested in this thread, event to comment a single line (here or
> in
>     the other users list thread), what means that or there's no more people
>     like us in this project or people really is not interested and just
> want us
>     to release and go forward.
>
>     As previously I think most of the PMCs here (Om, Josh, Greg and me for
>     sure), probably Yishay for his concise comments are more for this.
>     My thinking is that the right now I think only 2 PMCs are for CI
> Server,
>     and other one that is uncertainly but didn't try the CI Server.
>
>     I think all can live together while is not a must for the rest that
> don't
>     want it the others option, so what's about if we release with the
>     super-simple steps Chris proposal, and others wanting to use CI do that
>     when is their RM turn ? (of course maintaining it and making it work
> for
>     his release without requiring nothing for the rest that doesn't want
> it).
>
>     Release as other projects do is recommended but not required, the same
> as
>     the actual CI server (but this one should be less recommended since is
> a
>     royale-only practice not seen in any other place).
>
>     What's the important thing is to release, do it, and do it easily and
> often.
>
>     Thanks
>
>
>
>     El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
>     christofer.dutz@c-ware.de<ma...@c-ware.de>>)
> escribió:
>
>
>     Ok,
>
>     I'll write this a last time as I do feel like we're going in circles
> and
>     will from now on not participate in any discussion involving releasing
> on a
>     CI server.
>
>     A correct Maven release would use (There will be some additional
> profiles
>     to activate to include all modules)
>
>     1) the "mvn release:branch" call in order to create the branch and bump
>     the version of develop to the next version.
>     2) the "mvn release:prepare" to change the pom to the release version,
> set
>     the timestamp in the pom (for reproducible builds) build ... if all
> tests
>     are good, commit the changes, tag this commit, update the poms to the
> next
>     development version, commit those changes and push everything.
>     3) the "mvn release:perform" which will checkout the tagged version
> build
>     everything with the "apache-release" profile turned on (Which causes
> the
>     source.jars, Javadoc.jars, hashes and gpg singatures to be created as
> well
>     as the assembly) This also deploys the built artifacts to Nexus.
>
>     Most of that you are already doing on the CI server however you're not
>     letting it do all automatically (For lack of credentials)
>
>     But ... if you would just be doing those steps on the RM machine.
>
>     Chris
>
>
>
>
>
>     Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
> <ma...@adobe.com.INVALID>>:
>
>
>
>         On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org
> <ma...@apache.org>> wrote:
>
>             > What I want to know is what the Maven commands should be to
>     create a
>             > release in this "conventional process" you are referring to.
>             >
>
>             If you want to know what's the conventional maven process is, I
>     think I can
>             ask Chris if he wants to work with me on that process, since he
>     already did
>             many other Apache projects, we can expect the process is what
> is
>     needed for
>             us to. But just expect that will be a series of standard maven
>     commands
>             (prepare, release,...), so nothing strange at all (I expect).
>
>             Do you want us to do that?
>
>         Yes.  I want to know what the series of standard Maven commands
> are.
>     Then we can figure out how to convert them to run on the CI server.
>
>         -Alex
>
>             Thanks
>
>
>             >
>             > Maybe someone else can explain better than me.
>             >
>             > -Alex
>             >
>             > On 3/25/20, 2:22 PM, "Carlos Rovira" <
> carlosrovira@apache.org<ma...@apache.org>>
>     wrote:
>             >
>             >     Hi Alex,
>             >
>             >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>             > (<aharui@adobe.com.invalid<mailto:aharui@adobe.com.invalid
> >>)
>             >     escribió:
>             >
>             >     > Carlos,
>             >     >
>             >     > I'm pretty sure that part of the "conventional process"
>     you want to
>             > try
>             >     > requires filling the staging repo from a local machine.
>             >     >
>             >
>             >     This is what we already did. If you go to [1] will see
> [2].
>     That was
>             > the
>             >     upload of compiler to the staging repo. When trying to do
>     the same for
>             >     typedefs it failed when trying to fill repo from local
>     machine. I think
>             >     Chris or I should not take more time in trying to fix Ant
>     scripts that
>             > are
>             >     failing.
>             >
>             >     Thanks
>             >
>             >     [1]
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=SzmPqflLUwAxBCIkm%2BFn2BO8OZVJH1Gp66CVl349I3g%3D&amp;reserved=0
>             >     [2]
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=VONdkWMhQpEGhSlVoXwFuhdnApXmrSaTnSP%2FDeH6stc%3D&amp;reserved=0
>             >
>             >
>             >
>             >
>             >     >
>             >     > --
>             >     > Carlos Rovira
>             >     >
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=jPUGE0ohIi%2BFYoKZefaob1pSsIjC4AEEjE04N27FiI0%3D&amp;reserved=0
>             >     >
>             >     >
>             >     >
>             >     >
>             >
>             >
>             >
>
>             --
>             Carlos Rovira
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=bkaODFbcmtjdxlibVdfQRKtIzcXImHIQ4HpKQOTgLM8%3D&amp;reserved=0
>
>
>
>
>
>
>     --
>
>     Frédéric Gilli
>
>     mob.0668542622
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
>
>     [cid:171168797bb6addd0331]<
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
> >
>
>
>
>
>     --
>
>     Piotr Zarzycki
>
>     Patreon:
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=j%2BLcn3n8gF9Ro8d0S5EgcHamMg42sVnJXBymeIeQEUk%3D&amp;reserved=0
>
>
>
>

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

Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex

thanks. I want to ask first Yishay since he took over. If he doesn't object
anything we can do it.


El jue., 26 mar. 2020 a las 19:50, Alex Harui (<ah...@adobe.com.invalid>)
escribió:

> @Yishay Weiss
>
> Let's wait until the set of Maven steps are available from Chris and
> Carlos.  Then I will try to find some cycles to help you.  Because of where
> I live, where the schools are closed, and my kids schedule, I have good
> weeks and bad weeks for having time for work, so it will be best to wait to
> try a release until we have the steps and it is one of my good weeks (next
> good week starts this Friday at 5pm my time).
>
> Thanks,
> -Alex
>
> On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
>     Hi All,
>
>     I too, feel very uncomfortable participating in these threads. While
> grateful to Carlos and Chris for their work I’m very annoyed with the tone
> of ultimatums and doom and gloom. Alex has put in a lot of work into this
> and I trust his concerns are technical, rather than protecting his ego as
> has been suggested. We need to get this discussion back on technical tracks.
>
>     Since Chris has given up, and it looks like Carlos has as well, I
> volunteer to start the release process from scratch next Sunday, which is
> after Israel has switched to day light saving. I will try to do the process
> incrementally and in parallel to my other tasks. If by the end of the week
> it turns out the process is too cumbersome and cannot realistically be made
> to work smoothly I will be in favor of changing the requirements to enable
> Chris’s mvn setup to be the main release tool.
>
>     Thanks,
>     Yishay
>
>     From: Piotr Zarzycki<ma...@gmail.com>
>     Sent: Thursday, March 26, 2020 1:27 PM
>     To: Apache Royale Development<ma...@royale.apache.org>
>     Subject: Re: Releasing: Finally giving up
>
>     Hi All,
>
>     I'm member of Apache Foundation for quite some time now. I think I
> have wrote maybe 2-3 emails during that time on members mailing list. -
> Why? - well I'm a person which doesn't like never ending stories, stories
> which are not end up with consensus nor action and I'm sorry but this is
> how it looks like in most cases there. Here we are in Apache Royale project
> where this thread ended up exactly the same - never ending story. - As PMC
> of this project I would like to say enough! :)
>
>     I had hope that when Carlos and Chris try CI steps and in the process
> they may have some issues, but they will end up in the same place as I
> ended up where I was able to prepare RC1 in about 2h without the problem.
> It turns out that they end up in the place where I have started, in the
> place where I have spend 5-6 days of work to finally reach stable point.
> They ended up frustrated in the same way as I was!
>
>     I really don't care now what kind of issue they have now, whether it's
> fixable or not - I just have enough of those never ending discussions where
> there is absolutely no results.
>
>     I met Chris in US in Miami and I have spend with him best time ever,
> he is really great developer - if he is saying that he will have release
> process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not
> in a week - start today!
>
>     Please start whole work on that and make it happen. I will be the
> first who try the process and maybe with Chris's help we will solve also
> issue with uploading artifacts to staging area which we had.
>
>     Good Luck,
>     Piotr
>
>     czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> contact@cristallium.com>> napisał(a):
>
>     Hi Guys,
>
>     I'm a lover of Flex dev guy since more than 10 years, been members of
> Flex group on Montpellier (France) at golden age of Flex and go at all
> conferences when Michaël Chaize came to Montpellier (and using Flex every
> day).
>
>     First of all I want to thank every one of you for your hard work, and
> congratulate you for the actual Apache Royale capabilities.
>     With the last features (especialy datagrid), today your great work
> make possible to use Apache Royale in business application. Of course,
> there are bugs, but when reported, it's quickly fix, this is great.
>
>     Now, this is a huge opportunity but also risk for all guys like me to
> adop Apache Royale for futur projects or use it instead of using Air when
> it's possible.
>     Personnaly, I first use it on my own Webs applications and perhaps for
> my customers on little applications for the begin. My big enormous worry is
> to use it and be alone in front of a SDK bug.
>     Seeing new release every 1 or 2 months should certainly reassure me.
> For now I see SDK 0.9.7 since a lot of time and this make me affraid and I
> don't understand why there is no 0.9.8.
>
>     I'm speaking as an Apache Royale SDK user : I'm very sad to read these
> debates on the subject of tools to use for making release. I don't care
> about tools nedeed or not to build the release SDK.
>     I would like use Apache Royale to build RAD (Rapid Application Dev)
> Web applications and see more and more SDK features added, and participate
> to project (like today) by reporting bug  by using my time on isolate the
> bug and make tests cases with screenshoots to save your time in fixing it.
>
>     Using Reac, Bootstrap, AngularJS or other similar is a back to 80's.
> How can I explain my customer that I need 3 ou 4 days to make thinks that
> took me 1 day with Flex ?
>     The big competitive advantage of Apache Royale is not only be able to
> re-use Flex apps but is also simplicity and time saving where other SDK
> can't do it. (I think you already know that)
>
>     I am convinced that all guys like me will jump using Royale when they
> will know that there is a bug free SDK with fast evolution available.
> (unfortunaly it's not known enough, nobody know someone working in
> newspapers ?)
>
>     So please, I beg you, don't waste your time on things that are not
> essential and like Carlos said, go forward. From outside view, Apache
> Royale stay sticky to 0.9.7.
>
>     You are so close of a v1.0, I hope see it very soon and other releases
> with bugs fix every 1, 2 or 3 months.
>     Consider my comments as support and not criticism.
>
>     Thanks again for your hard work.
>
>     Long life and success to Apache Royale !
>
>     Fred
>
>
>
>     Le 26.03.2020 09:26, Carlos Rovira a écrit :
>     Hi,
>
>     that's amazingly simple, so I think we should go that way without
> doubt. I
>     think reached this point there's a clear sense of that we need to go
> that
>     route.
>
>     We tried our best to stick with the previous process and we're all
>     loosing lots of time. Then currently seems no more people in the
> community
>     was interested in this thread, event to comment a single line (here or
> in
>     the other users list thread), what means that or there's no more people
>     like us in this project or people really is not interested and just
> want us
>     to release and go forward.
>
>     As previously I think most of the PMCs here (Om, Josh, Greg and me for
>     sure), probably Yishay for his concise comments are more for this.
>     My thinking is that the right now I think only 2 PMCs are for CI
> Server,
>     and other one that is uncertainly but didn't try the CI Server.
>
>     I think all can live together while is not a must for the rest that
> don't
>     want it the others option, so what's about if we release with the
>     super-simple steps Chris proposal, and others wanting to use CI do that
>     when is their RM turn ? (of course maintaining it and making it work
> for
>     his release without requiring nothing for the rest that doesn't want
> it).
>
>     Release as other projects do is recommended but not required, the same
> as
>     the actual CI server (but this one should be less recommended since is
> a
>     royale-only practice not seen in any other place).
>
>     What's the important thing is to release, do it, and do it easily and
> often.
>
>     Thanks
>
>
>
>     El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
>     christofer.dutz@c-ware.de<ma...@c-ware.de>>)
> escribió:
>
>
>     Ok,
>
>     I'll write this a last time as I do feel like we're going in circles
> and
>     will from now on not participate in any discussion involving releasing
> on a
>     CI server.
>
>     A correct Maven release would use (There will be some additional
> profiles
>     to activate to include all modules)
>
>     1) the "mvn release:branch" call in order to create the branch and bump
>     the version of develop to the next version.
>     2) the "mvn release:prepare" to change the pom to the release version,
> set
>     the timestamp in the pom (for reproducible builds) build ... if all
> tests
>     are good, commit the changes, tag this commit, update the poms to the
> next
>     development version, commit those changes and push everything.
>     3) the "mvn release:perform" which will checkout the tagged version
> build
>     everything with the "apache-release" profile turned on (Which causes
> the
>     source.jars, Javadoc.jars, hashes and gpg singatures to be created as
> well
>     as the assembly) This also deploys the built artifacts to Nexus.
>
>     Most of that you are already doing on the CI server however you're not
>     letting it do all automatically (For lack of credentials)
>
>     But ... if you would just be doing those steps on the RM machine.
>
>     Chris
>
>
>
>
>
>     Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
> <ma...@adobe.com.INVALID>>:
>
>
>
>         On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org
> <ma...@apache.org>> wrote:
>
>             > What I want to know is what the Maven commands should be to
>     create a
>             > release in this "conventional process" you are referring to.
>             >
>
>             If you want to know what's the conventional maven process is, I
>     think I can
>             ask Chris if he wants to work with me on that process, since he
>     already did
>             many other Apache projects, we can expect the process is what
> is
>     needed for
>             us to. But just expect that will be a series of standard maven
>     commands
>             (prepare, release,...), so nothing strange at all (I expect).
>
>             Do you want us to do that?
>
>         Yes.  I want to know what the series of standard Maven commands
> are.
>     Then we can figure out how to convert them to run on the CI server.
>
>         -Alex
>
>             Thanks
>
>
>             >
>             > Maybe someone else can explain better than me.
>             >
>             > -Alex
>             >
>             > On 3/25/20, 2:22 PM, "Carlos Rovira" <
> carlosrovira@apache.org<ma...@apache.org>>
>     wrote:
>             >
>             >     Hi Alex,
>             >
>             >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>             > (<aharui@adobe.com.invalid<mailto:aharui@adobe.com.invalid
> >>)
>             >     escribió:
>             >
>             >     > Carlos,
>             >     >
>             >     > I'm pretty sure that part of the "conventional process"
>     you want to
>             > try
>             >     > requires filling the staging repo from a local machine.
>             >     >
>             >
>             >     This is what we already did. If you go to [1] will see
> [2].
>     That was
>             > the
>             >     upload of compiler to the staging repo. When trying to do
>     the same for
>             >     typedefs it failed when trying to fill repo from local
>     machine. I think
>             >     Chris or I should not take more time in trying to fix Ant
>     scripts that
>             > are
>             >     failing.
>             >
>             >     Thanks
>             >
>             >     [1]
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=SzmPqflLUwAxBCIkm%2BFn2BO8OZVJH1Gp66CVl349I3g%3D&amp;reserved=0
>             >     [2]
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=VONdkWMhQpEGhSlVoXwFuhdnApXmrSaTnSP%2FDeH6stc%3D&amp;reserved=0
>             >
>             >
>             >
>             >
>             >     >
>             >     > --
>             >     > Carlos Rovira
>             >     >
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=jPUGE0ohIi%2BFYoKZefaob1pSsIjC4AEEjE04N27FiI0%3D&amp;reserved=0
>             >     >
>             >     >
>             >     >
>             >     >
>             >
>             >
>             >
>
>             --
>             Carlos Rovira
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=bkaODFbcmtjdxlibVdfQRKtIzcXImHIQ4HpKQOTgLM8%3D&amp;reserved=0
>
>
>
>
>
>
>     --
>
>     Frédéric Gilli
>
>     mob.0668542622
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
>
>     [cid:171168797bb6addd0331]<
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
> >
>
>
>
>
>     --
>
>     Piotr Zarzycki
>
>     Patreon:
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=j%2BLcn3n8gF9Ro8d0S5EgcHamMg42sVnJXBymeIeQEUk%3D&amp;reserved=0
>
>
>
>

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

Re: Releasing: Finally giving up

Posted by Greg Dove <gr...@gmail.com>.
There were issues identified with the original process as Chris and Carlos
worked through it that prevented them from completing it. Exposing any
problems in that itself is helpful, but I also observed that it was a very
frustrating discovery by Chris and Carlos, and we should be thankful it is
now known.

-The timestamp issue. Alex, you already suggested this was perhaps an issue
with the original process, and we are waiting to see if DST alignment is
the 'fix' (if it is, it still needs a real fix, we all agree).
-Chris mentioned that the compiler output is also inconsistent which makes
binary reproducibles a problem in the swf part of swcs. Perhaps there are
some settings for this that are not apparent to address it. In a swc, the
xml content/ordering seems to match which also corresponds to classes being
output in the same order in the bytecode of the swf content. But the class
members inside the bytecode for each class can be in a different order.
-there were also differences in the actual content between CI server and
local for nodejs externs, for unknown reasons

If there are indeed problems with the 'standard' against which the
alternative needs to be assessed then nobody is 'on the hook' or 'off the
hook'. So far it just means the starting point does not seem to be a
reliable reference implementation to attempt to match in the first place.
Let's focus on fixing that.




On Mon, Mar 30, 2020 at 8:48 AM Carlos Rovira <ca...@apache.org>
wrote:

> Hi Alex and Yishay,
>
> as compiler-build-tools is released (hope others will have the time to test
> and vote it soon), let me know if I finally start 0.9.7.
> I'll be ok with whatever you decided.
>
> Thanks! :)
>
> Carlos
>
>
>
> El dom., 29 mar. 2020 a las 21:43, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
> > I share your concern with the precedent being set here.  I don't think
> the
> > folks behind these changes should be off the hook for getting the CI
> steps
> > to work again.  Otherwise, any of us can go break stuff under the
> rationale
> > of making something else better and let someone else deal with the mess.
> >
> > Still, certain things have to be done.  I think there is consensus that a
> > release should be doable on a local machine or the CI server.  So,
> > hopefully Carlos is off to not just create an RC, but also document the
> > steps required to do this end-to-end on a local machine by actually doing
> > it.  That made sense while waiting for Sunday to roll around to see if
> that
> > gets past the timestamp issue in the SWCs.
> >
> > If you have time to tweak the CI steps and see if they work to help get
> > them working again, feel free to do so.  I will hopefully have cycles to
> > help.   The credentials are in the private@ archives.  I recommend
> > creating a completely new set of steps by cloning the old jobs as needed.
> > For example we won't need the 1a (utils) step (or probably the other
> utils
> > steps) anymore.  A differently named step or two is needed to match what
> > Carlos did for the compiler-build-tools release.
> >
> > If you can help them resolve the SWC timestamp issue, I hope to see the
> > folks who committed to restoring these steps back to working order will
> > complete that task.
> >
> > My 2 cents,
> > -Alex
> >
> > On 3/29/20, 10:43 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> >     I guess I misunderstood. I thought we were only talking about the
> > compiler-build-tools release.
> >
> >     Carlos, I of course don’t mind you doing the work. I have plenty on
> my
> > plate. I’m concerned with the process. Although I haven’t been following
> > the threads closely enough to understand the whole technical debate, I
> did
> > understand that Alex and others have expressed reservations (e.g. should
> > the release actually use ant to verify the ant build). Has this debate
> > reached a conclusion that enjoys a consensus? If not, there should
> probably
> > be a vote. I don’t want to encourage a dynamic where debates are won by
> > unilateral action.
> >
> >     If everyone feels comfortable with Carlos releasing with mvn, then I
> > won’t object. If there are reservations then I’d still like to give it
> > another week, and see if an RM newbie like me can apply the process
> > suggested by Alex.
> >
> >     Thanks.
> >
> >     From: Carlos Rovira<ma...@apache.org>
> >     Sent: Sunday, March 29, 2020 7:34 PM
> >     To: Apache Royale Development<ma...@royale.apache.org>
> >     Subject: Re: Releasing: Finally giving up
> >
> >     Hi Yishay,
> >
> >     I think we were all in agreement so I'll make the release. Right now
> > we're
> >     voting the compiler-build-tools 1.2.0 release
> >     As soon as this is approved, I'll continue withe 0.9.7 release.
> >
> >     compiler build tools 1.2.0 is done to release some small changes for
> >     reproducible builds and check the optional path about to release
> > compiler
> >     build tools or jburg versions in the future (that should be very
> rare).
> >
> >     Thanks
> >
> >
> >     El dom., 29 mar. 2020 a las 15:59, Yishay Weiss (<
> > yishayjobs@hotmail.com>)
> >     escribió:
> >
> >     > Ok, I’m ready. What’s next? Do I need to cancel an RC? How do I
> > login to
> >     > Jenkins? Where do I start?
> >     >
> >     > From: Alex Harui<ma...@adobe.com>
> >     > Sent: Thursday, March 26, 2020 8:50 PM
> >     > To: dev@royale.apache.org<ma...@royale.apache.org>; Yishay
> >     > Weiss<ma...@hotmail.com>
> >     > Subject: Re: Releasing: Finally giving up
> >     >
> >     > @Yishay Weiss
> >     >
> >     > Let's wait until the set of Maven steps are available from Chris
> and
> >     > Carlos.  Then I will try to find some cycles to help you.  Because
> > of where
> >     > I live, where the schools are closed, and my kids schedule, I have
> > good
> >     > weeks and bad weeks for having time for work, so it will be best to
> > wait to
> >     > try a release until we have the steps and it is one of my good
> weeks
> > (next
> >     > good week starts this Friday at 5pm my time).
> >     >
> >     > Thanks,
> >     > -Alex
> >     >
> >     > On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >     >
> >     >     Hi All,
> >     >
> >     >     I too, feel very uncomfortable participating in these threads.
> > While
> >     > grateful to Carlos and Chris for their work I’m very annoyed with
> > the tone
> >     > of ultimatums and doom and gloom. Alex has put in a lot of work
> into
> > this
> >     > and I trust his concerns are technical, rather than protecting his
> > ego as
> >     > has been suggested. We need to get this discussion back on
> technical
> > tracks.
> >     >
> >     >     Since Chris has given up, and it looks like Carlos has as
> well, I
> >     > volunteer to start the release process from scratch next Sunday,
> > which is
> >     > after Israel has switched to day light saving. I will try to do the
> > process
> >     > incrementally and in parallel to my other tasks. If by the end of
> > the week
> >     > it turns out the process is too cumbersome and cannot realistically
> > be made
> >     > to work smoothly I will be in favor of changing the requirements to
> > enable
> >     > Chris’s mvn setup to be the main release tool.
> >     >
> >     >     Thanks,
> >     >     Yishay
> >     >
> >     >     From: Piotr Zarzycki<ma...@gmail.com>
> >     >     Sent: Thursday, March 26, 2020 1:27 PM
> >     >     To: Apache Royale Development<ma...@royale.apache.org>
> >     >     Subject: Re: Releasing: Finally giving up
> >     >
> >     >     Hi All,
> >     >
> >     >     I'm member of Apache Foundation for quite some time now. I
> think
> > I
> >     > have wrote maybe 2-3 emails during that time on members mailing
> > list. -
> >     > Why? - well I'm a person which doesn't like never ending stories,
> > stories
> >     > which are not end up with consensus nor action and I'm sorry but
> > this is
> >     > how it looks like in most cases there. Here we are in Apache Royale
> > project
> >     > where this thread ended up exactly the same - never ending story. -
> > As PMC
> >     > of this project I would like to say enough! :)
> >     >
> >     >     I had hope that when Carlos and Chris try CI steps and in the
> > process
> >     > they may have some issues, but they will end up in the same place
> as
> > I
> >     > ended up where I was able to prepare RC1 in about 2h without the
> > problem.
> >     > It turns out that they end up in the place where I have started, in
> > the
> >     > place where I have spend 5-6 days of work to finally reach stable
> > point.
> >     > They ended up frustrated in the same way as I was!
> >     >
> >     >     I really don't care now what kind of issue they have now,
> > whether it's
> >     > fixable or not - I just have enough of those never ending
> > discussions where
> >     > there is absolutely no results.
> >     >
> >     >     I met Chris in US in Miami and I have spend with him best time
> > ever,
> >     > he is really great developer - if he is saying that he will have
> > release
> >     > process in 3-4 steps on my machine - I'm +1 make it so. Not
> > tomorrow, not
> >     > in a week - start today!
> >     >
> >     >     Please start whole work on that and make it happen. I will be
> the
> >     > first who try the process and maybe with Chris's help we will solve
> > also
> >     > issue with uploading artifacts to staging area which we had.
> >     >
> >     >     Good Luck,
> >     >     Piotr
> >     >
> >     >     czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> >     > contact@cristallium.com>> napisał(a):
> >     >
> >     >     Hi Guys,
> >     >
> >     >     I'm a lover of Flex dev guy since more than 10 years, been
> > members of
> >     > Flex group on Montpellier (France) at golden age of Flex and go at
> > all
> >     > conferences when Michaël Chaize came to Montpellier (and using Flex
> > every
> >     > day).
> >     >
> >     >     First of all I want to thank every one of you for your hard
> > work, and
> >     > congratulate you for the actual Apache Royale capabilities.
> >     >     With the last features (especialy datagrid), today your great
> > work
> >     > make possible to use Apache Royale in business application. Of
> > course,
> >     > there are bugs, but when reported, it's quickly fix, this is great.
> >     >
> >     >     Now, this is a huge opportunity but also risk for all guys like
> > me to
> >     > adop Apache Royale for futur projects or use it instead of using
> Air
> > when
> >     > it's possible.
> >     >     Personnaly, I first use it on my own Webs applications and
> > perhaps for
> >     > my customers on little applications for the begin. My big enormous
> > worry is
> >     > to use it and be alone in front of a SDK bug.
> >     >     Seeing new release every 1 or 2 months should certainly
> reassure
> > me.
> >     > For now I see SDK 0.9.7 since a lot of time and this make me
> affraid
> > and I
> >     > don't understand why there is no 0.9.8.
> >     >
> >     >     I'm speaking as an Apache Royale SDK user : I'm very sad to
> read
> > these
> >     > debates on the subject of tools to use for making release. I don't
> > care
> >     > about tools nedeed or not to build the release SDK.
> >     >     I would like use Apache Royale to build RAD (Rapid Application
> > Dev)
> >     > Web applications and see more and more SDK features added, and
> > participate
> >     > to project (like today) by reporting bug  by using my time on
> > isolate the
> >     > bug and make tests cases with screenshoots to save your time in
> > fixing it.
> >     >
> >     >     Using Reac, Bootstrap, AngularJS or other similar is a back to
> > 80's.
> >     > How can I explain my customer that I need 3 ou 4 days to make
> thinks
> > that
> >     > took me 1 day with Flex ?
> >     >     The big competitive advantage of Apache Royale is not only be
> > able to
> >     > re-use Flex apps but is also simplicity and time saving where other
> > SDK
> >     > can't do it. (I think you already know that)
> >     >
> >     >     I am convinced that all guys like me will jump using Royale
> when
> > they
> >     > will know that there is a bug free SDK with fast evolution
> available.
> >     > (unfortunaly it's not known enough, nobody know someone working in
> >     > newspapers ?)
> >     >
> >     >     So please, I beg you, don't waste your time on things that are
> > not
> >     > essential and like Carlos said, go forward. From outside view,
> Apache
> >     > Royale stay sticky to 0.9.7.
> >     >
> >     >     You are so close of a v1.0, I hope see it very soon and other
> > releases
> >     > with bugs fix every 1, 2 or 3 months.
> >     >     Consider my comments as support and not criticism.
> >     >
> >     >     Thanks again for your hard work.
> >     >
> >     >     Long life and success to Apache Royale !
> >     >
> >     >     Fred
> >     >
> >     >
> >     >
> >     >     Le 26.03.2020 09:26, Carlos Rovira a écrit :
> >     >     Hi,
> >     >
> >     >     that's amazingly simple, so I think we should go that way
> without
> >     > doubt. I
> >     >     think reached this point there's a clear sense of that we need
> > to go
> >     > that
> >     >     route.
> >     >
> >     >     We tried our best to stick with the previous process and we're
> > all
> >     >     loosing lots of time. Then currently seems no more people in
> the
> >     > community
> >     >     was interested in this thread, event to comment a single line
> > (here or
> >     > in
> >     >     the other users list thread), what means that or there's no
> more
> > people
> >     >     like us in this project or people really is not interested and
> > just
> >     > want us
> >     >     to release and go forward.
> >     >
> >     >     As previously I think most of the PMCs here (Om, Josh, Greg and
> > me for
> >     >     sure), probably Yishay for his concise comments are more for
> > this.
> >     >     My thinking is that the right now I think only 2 PMCs are for
> CI
> >     > Server,
> >     >     and other one that is uncertainly but didn't try the CI Server.
> >     >
> >     >     I think all can live together while is not a must for the rest
> > that
> >     > don't
> >     >     want it the others option, so what's about if we release with
> the
> >     >     super-simple steps Chris proposal, and others wanting to use CI
> > do that
> >     >     when is their RM turn ? (of course maintaining it and making it
> > work
> >     > for
> >     >     his release without requiring nothing for the rest that doesn't
> > want
> >     > it).
> >     >
> >     >     Release as other projects do is recommended but not required,
> > the same
> >     > as
> >     >     the actual CI server (but this one should be less recommended
> > since is
> >     > a
> >     >     royale-only practice not seen in any other place).
> >     >
> >     >     What's the important thing is to release, do it, and do it
> > easily and
> >     > often.
> >     >
> >     >     Thanks
> >     >
> >     >
> >     >
> >     >     El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
> >     >     christofer.dutz@c-ware.de<ma...@c-ware.de>>)
> >     > escribió:
> >     >
> >     >
> >     >     Ok,
> >     >
> >     >     I'll write this a last time as I do feel like we're going in
> > circles
> >     > and
> >     >     will from now on not participate in any discussion involving
> > releasing
> >     > on a
> >     >     CI server.
> >     >
> >     >     A correct Maven release would use (There will be some
> additional
> >     > profiles
> >     >     to activate to include all modules)
> >     >
> >     >     1) the "mvn release:branch" call in order to create the branch
> > and bump
> >     >     the version of develop to the next version.
> >     >     2) the "mvn release:prepare" to change the pom to the release
> > version,
> >     > set
> >     >     the timestamp in the pom (for reproducible builds) build ... if
> > all
> >     > tests
> >     >     are good, commit the changes, tag this commit, update the poms
> > to the
> >     > next
> >     >     development version, commit those changes and push everything.
> >     >     3) the "mvn release:perform" which will checkout the tagged
> > version
> >     > build
> >     >     everything with the "apache-release" profile turned on (Which
> > causes
> >     > the
> >     >     source.jars, Javadoc.jars, hashes and gpg singatures to be
> > created as
> >     > well
> >     >     as the assembly) This also deploys the built artifacts to
> Nexus.
> >     >
> >     >     Most of that you are already doing on the CI server however
> > you're not
> >     >     letting it do all automatically (For lack of credentials)
> >     >
> >     >     But ... if you would just be doing those steps on the RM
> machine.
> >     >
> >     >     Chris
> >     >
> >     >
> >     >
> >     >
> >     >
> >     >     Am 26.03.20, 05:54 schrieb "Alex Harui"
> <aharui@adobe.com.INVALID
> >     > <ma...@adobe.com.INVALID>>:
> >     >
> >     >
> >     >
> >     >         On 3/25/20, 4:46 PM, "Carlos Rovira" <
> > carlosrovira@apache.org
> >     > <ma...@apache.org>> wrote:
> >     >
> >     >             > What I want to know is what the Maven commands should
> > be to
> >     >     create a
> >     >             > release in this "conventional process" you are
> > referring to.
> >     >             >
> >     >
> >     >             If you want to know what's the conventional maven
> > process is, I
> >     >     think I can
> >     >             ask Chris if he wants to work with me on that process,
> > since he
> >     >     already did
> >     >             many other Apache projects, we can expect the process
> is
> > what
> >     > is
> >     >     needed for
> >     >             us to. But just expect that will be a series of
> standard
> > maven
> >     >     commands
> >     >             (prepare, release,...), so nothing strange at all (I
> > expect).
> >     >
> >     >             Do you want us to do that?
> >     >
> >     >         Yes.  I want to know what the series of standard Maven
> > commands
> >     > are.
> >     >     Then we can figure out how to convert them to run on the CI
> > server.
> >     >
> >     >         -Alex
> >     >
> >     >             Thanks
> >     >
> >     >
> >     >             >
> >     >             > Maybe someone else can explain better than me.
> >     >             >
> >     >             > -Alex
> >     >             >
> >     >             > On 3/25/20, 2:22 PM, "Carlos Rovira" <
> >     > carlosrovira@apache.org<ma...@apache.org>>
> >     >     wrote:
> >     >             >
> >     >             >     Hi Alex,
> >     >             >
> >     >             >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
> >     >             > (<aharui@adobe.com.invalid<mailto:
> > aharui@adobe.com.invalid
> >     > >>)
> >     >             >     escribió:
> >     >             >
> >     >             >     > Carlos,
> >     >             >     >
> >     >             >     > I'm pretty sure that part of the "conventional
> > process"
> >     >     you want to
> >     >             > try
> >     >             >     > requires filling the staging repo from a local
> > machine.
> >     >             >     >
> >     >             >
> >     >             >     This is what we already did. If you go to [1]
> will
> > see
> >     > [2].
> >     >     That was
> >     >             > the
> >     >             >     upload of compiler to the staging repo. When
> > trying to do
> >     >     the same for
> >     >             >     typedefs it failed when trying to fill repo from
> > local
> >     >     machine. I think
> >     >             >     Chris or I should not take more time in trying to
> > fix Ant
> >     >     scripts that
> >     >             > are
> >     >             >     failing.
> >     >             >
> >     >             >     Thanks
> >     >             >
> >     >             >     [1]
> >     >             >
> >     >
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840951898&amp;sdata=U8BmlIdd6ZajuOEn1jNCWlrJbAn%2BV1BQbwhsXkRc854%3D&amp;reserved=0
> >     >             >     [2]
> >     >             >
> >     >
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840951898&amp;sdata=PKLdBG1DimNg3wANGcs3cTfiR3nelEed1tBZM%2FvVU%2Bk%3D&amp;reserved=0
> >     >             >
> >     >             >
> >     >             >
> >     >             >
> >     >             >     >
> >     >             >     > --
> >     >             >     > Carlos Rovira
> >     >             >     >
> >     >             >
> >     >
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840951898&amp;sdata=3uxFi47xpWG7B3m7OF%2FqniyK7yb3uUDZD4CCgaUtwPM%3D&amp;reserved=0
> >     >             >     >
> >     >             >     >
> >     >             >     >
> >     >             >     >
> >     >             >
> >     >             >
> >     >             >
> >     >
> >     >             --
> >     >             Carlos Rovira
> >     >
> >     >
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=xtI3M5bsNTrNr5pz7b7cDKaWaqkcbLGrcovspTCH8xk%3D&amp;reserved=0
> >     >
> >     >
> >     >
> >     >
> >     >
> >     >
> >     >     --
> >     >
> >     >     Frédéric Gilli
> >     >
> >     >     mob.0668542622
> >     >
> >     >
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=FmIv8VzENVjH8Lbe%2FYiZb%2BtripSYb5JG%2F5hdWvnVW9M%3D&amp;reserved=0
> >     >
> >     >     [cid:171168797bb6addd0331]<
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=FmIv8VzENVjH8Lbe%2FYiZb%2BtripSYb5JG%2F5hdWvnVW9M%3D&amp;reserved=0
> >     > >
> >     >
> >     >
> >     >
> >     >
> >     >     --
> >     >
> >     >     Piotr Zarzycki
> >     >
> >     >     Patreon:
> >     >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=xF1gfNEs6uwJ3oyQ%2BdzA4PJ0eB%2BcGmaBBvas8KVYk9c%3D&amp;reserved=0
> >     >
> >     >
> >     >
> >     >
> >
> >     --
> >     Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=xtI3M5bsNTrNr5pz7b7cDKaWaqkcbLGrcovspTCH8xk%3D&amp;reserved=0
> >
> >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex and Yishay,

as compiler-build-tools is released (hope others will have the time to test
and vote it soon), let me know if I finally start 0.9.7.
I'll be ok with whatever you decided.

Thanks! :)

Carlos



El dom., 29 mar. 2020 a las 21:43, Alex Harui (<ah...@adobe.com.invalid>)
escribió:

> I share your concern with the precedent being set here.  I don't think the
> folks behind these changes should be off the hook for getting the CI steps
> to work again.  Otherwise, any of us can go break stuff under the rationale
> of making something else better and let someone else deal with the mess.
>
> Still, certain things have to be done.  I think there is consensus that a
> release should be doable on a local machine or the CI server.  So,
> hopefully Carlos is off to not just create an RC, but also document the
> steps required to do this end-to-end on a local machine by actually doing
> it.  That made sense while waiting for Sunday to roll around to see if that
> gets past the timestamp issue in the SWCs.
>
> If you have time to tweak the CI steps and see if they work to help get
> them working again, feel free to do so.  I will hopefully have cycles to
> help.   The credentials are in the private@ archives.  I recommend
> creating a completely new set of steps by cloning the old jobs as needed.
> For example we won't need the 1a (utils) step (or probably the other utils
> steps) anymore.  A differently named step or two is needed to match what
> Carlos did for the compiler-build-tools release.
>
> If you can help them resolve the SWC timestamp issue, I hope to see the
> folks who committed to restoring these steps back to working order will
> complete that task.
>
> My 2 cents,
> -Alex
>
> On 3/29/20, 10:43 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
>     I guess I misunderstood. I thought we were only talking about the
> compiler-build-tools release.
>
>     Carlos, I of course don’t mind you doing the work. I have plenty on my
> plate. I’m concerned with the process. Although I haven’t been following
> the threads closely enough to understand the whole technical debate, I did
> understand that Alex and others have expressed reservations (e.g. should
> the release actually use ant to verify the ant build). Has this debate
> reached a conclusion that enjoys a consensus? If not, there should probably
> be a vote. I don’t want to encourage a dynamic where debates are won by
> unilateral action.
>
>     If everyone feels comfortable with Carlos releasing with mvn, then I
> won’t object. If there are reservations then I’d still like to give it
> another week, and see if an RM newbie like me can apply the process
> suggested by Alex.
>
>     Thanks.
>
>     From: Carlos Rovira<ma...@apache.org>
>     Sent: Sunday, March 29, 2020 7:34 PM
>     To: Apache Royale Development<ma...@royale.apache.org>
>     Subject: Re: Releasing: Finally giving up
>
>     Hi Yishay,
>
>     I think we were all in agreement so I'll make the release. Right now
> we're
>     voting the compiler-build-tools 1.2.0 release
>     As soon as this is approved, I'll continue withe 0.9.7 release.
>
>     compiler build tools 1.2.0 is done to release some small changes for
>     reproducible builds and check the optional path about to release
> compiler
>     build tools or jburg versions in the future (that should be very rare).
>
>     Thanks
>
>
>     El dom., 29 mar. 2020 a las 15:59, Yishay Weiss (<
> yishayjobs@hotmail.com>)
>     escribió:
>
>     > Ok, I’m ready. What’s next? Do I need to cancel an RC? How do I
> login to
>     > Jenkins? Where do I start?
>     >
>     > From: Alex Harui<ma...@adobe.com>
>     > Sent: Thursday, March 26, 2020 8:50 PM
>     > To: dev@royale.apache.org<ma...@royale.apache.org>; Yishay
>     > Weiss<ma...@hotmail.com>
>     > Subject: Re: Releasing: Finally giving up
>     >
>     > @Yishay Weiss
>     >
>     > Let's wait until the set of Maven steps are available from Chris and
>     > Carlos.  Then I will try to find some cycles to help you.  Because
> of where
>     > I live, where the schools are closed, and my kids schedule, I have
> good
>     > weeks and bad weeks for having time for work, so it will be best to
> wait to
>     > try a release until we have the steps and it is one of my good weeks
> (next
>     > good week starts this Friday at 5pm my time).
>     >
>     > Thanks,
>     > -Alex
>     >
>     > On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>     >
>     >     Hi All,
>     >
>     >     I too, feel very uncomfortable participating in these threads.
> While
>     > grateful to Carlos and Chris for their work I’m very annoyed with
> the tone
>     > of ultimatums and doom and gloom. Alex has put in a lot of work into
> this
>     > and I trust his concerns are technical, rather than protecting his
> ego as
>     > has been suggested. We need to get this discussion back on technical
> tracks.
>     >
>     >     Since Chris has given up, and it looks like Carlos has as well, I
>     > volunteer to start the release process from scratch next Sunday,
> which is
>     > after Israel has switched to day light saving. I will try to do the
> process
>     > incrementally and in parallel to my other tasks. If by the end of
> the week
>     > it turns out the process is too cumbersome and cannot realistically
> be made
>     > to work smoothly I will be in favor of changing the requirements to
> enable
>     > Chris’s mvn setup to be the main release tool.
>     >
>     >     Thanks,
>     >     Yishay
>     >
>     >     From: Piotr Zarzycki<ma...@gmail.com>
>     >     Sent: Thursday, March 26, 2020 1:27 PM
>     >     To: Apache Royale Development<ma...@royale.apache.org>
>     >     Subject: Re: Releasing: Finally giving up
>     >
>     >     Hi All,
>     >
>     >     I'm member of Apache Foundation for quite some time now. I think
> I
>     > have wrote maybe 2-3 emails during that time on members mailing
> list. -
>     > Why? - well I'm a person which doesn't like never ending stories,
> stories
>     > which are not end up with consensus nor action and I'm sorry but
> this is
>     > how it looks like in most cases there. Here we are in Apache Royale
> project
>     > where this thread ended up exactly the same - never ending story. -
> As PMC
>     > of this project I would like to say enough! :)
>     >
>     >     I had hope that when Carlos and Chris try CI steps and in the
> process
>     > they may have some issues, but they will end up in the same place as
> I
>     > ended up where I was able to prepare RC1 in about 2h without the
> problem.
>     > It turns out that they end up in the place where I have started, in
> the
>     > place where I have spend 5-6 days of work to finally reach stable
> point.
>     > They ended up frustrated in the same way as I was!
>     >
>     >     I really don't care now what kind of issue they have now,
> whether it's
>     > fixable or not - I just have enough of those never ending
> discussions where
>     > there is absolutely no results.
>     >
>     >     I met Chris in US in Miami and I have spend with him best time
> ever,
>     > he is really great developer - if he is saying that he will have
> release
>     > process in 3-4 steps on my machine - I'm +1 make it so. Not
> tomorrow, not
>     > in a week - start today!
>     >
>     >     Please start whole work on that and make it happen. I will be the
>     > first who try the process and maybe with Chris's help we will solve
> also
>     > issue with uploading artifacts to staging area which we had.
>     >
>     >     Good Luck,
>     >     Piotr
>     >
>     >     czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
>     > contact@cristallium.com>> napisał(a):
>     >
>     >     Hi Guys,
>     >
>     >     I'm a lover of Flex dev guy since more than 10 years, been
> members of
>     > Flex group on Montpellier (France) at golden age of Flex and go at
> all
>     > conferences when Michaël Chaize came to Montpellier (and using Flex
> every
>     > day).
>     >
>     >     First of all I want to thank every one of you for your hard
> work, and
>     > congratulate you for the actual Apache Royale capabilities.
>     >     With the last features (especialy datagrid), today your great
> work
>     > make possible to use Apache Royale in business application. Of
> course,
>     > there are bugs, but when reported, it's quickly fix, this is great.
>     >
>     >     Now, this is a huge opportunity but also risk for all guys like
> me to
>     > adop Apache Royale for futur projects or use it instead of using Air
> when
>     > it's possible.
>     >     Personnaly, I first use it on my own Webs applications and
> perhaps for
>     > my customers on little applications for the begin. My big enormous
> worry is
>     > to use it and be alone in front of a SDK bug.
>     >     Seeing new release every 1 or 2 months should certainly reassure
> me.
>     > For now I see SDK 0.9.7 since a lot of time and this make me affraid
> and I
>     > don't understand why there is no 0.9.8.
>     >
>     >     I'm speaking as an Apache Royale SDK user : I'm very sad to read
> these
>     > debates on the subject of tools to use for making release. I don't
> care
>     > about tools nedeed or not to build the release SDK.
>     >     I would like use Apache Royale to build RAD (Rapid Application
> Dev)
>     > Web applications and see more and more SDK features added, and
> participate
>     > to project (like today) by reporting bug  by using my time on
> isolate the
>     > bug and make tests cases with screenshoots to save your time in
> fixing it.
>     >
>     >     Using Reac, Bootstrap, AngularJS or other similar is a back to
> 80's.
>     > How can I explain my customer that I need 3 ou 4 days to make thinks
> that
>     > took me 1 day with Flex ?
>     >     The big competitive advantage of Apache Royale is not only be
> able to
>     > re-use Flex apps but is also simplicity and time saving where other
> SDK
>     > can't do it. (I think you already know that)
>     >
>     >     I am convinced that all guys like me will jump using Royale when
> they
>     > will know that there is a bug free SDK with fast evolution available.
>     > (unfortunaly it's not known enough, nobody know someone working in
>     > newspapers ?)
>     >
>     >     So please, I beg you, don't waste your time on things that are
> not
>     > essential and like Carlos said, go forward. From outside view, Apache
>     > Royale stay sticky to 0.9.7.
>     >
>     >     You are so close of a v1.0, I hope see it very soon and other
> releases
>     > with bugs fix every 1, 2 or 3 months.
>     >     Consider my comments as support and not criticism.
>     >
>     >     Thanks again for your hard work.
>     >
>     >     Long life and success to Apache Royale !
>     >
>     >     Fred
>     >
>     >
>     >
>     >     Le 26.03.2020 09:26, Carlos Rovira a écrit :
>     >     Hi,
>     >
>     >     that's amazingly simple, so I think we should go that way without
>     > doubt. I
>     >     think reached this point there's a clear sense of that we need
> to go
>     > that
>     >     route.
>     >
>     >     We tried our best to stick with the previous process and we're
> all
>     >     loosing lots of time. Then currently seems no more people in the
>     > community
>     >     was interested in this thread, event to comment a single line
> (here or
>     > in
>     >     the other users list thread), what means that or there's no more
> people
>     >     like us in this project or people really is not interested and
> just
>     > want us
>     >     to release and go forward.
>     >
>     >     As previously I think most of the PMCs here (Om, Josh, Greg and
> me for
>     >     sure), probably Yishay for his concise comments are more for
> this.
>     >     My thinking is that the right now I think only 2 PMCs are for CI
>     > Server,
>     >     and other one that is uncertainly but didn't try the CI Server.
>     >
>     >     I think all can live together while is not a must for the rest
> that
>     > don't
>     >     want it the others option, so what's about if we release with the
>     >     super-simple steps Chris proposal, and others wanting to use CI
> do that
>     >     when is their RM turn ? (of course maintaining it and making it
> work
>     > for
>     >     his release without requiring nothing for the rest that doesn't
> want
>     > it).
>     >
>     >     Release as other projects do is recommended but not required,
> the same
>     > as
>     >     the actual CI server (but this one should be less recommended
> since is
>     > a
>     >     royale-only practice not seen in any other place).
>     >
>     >     What's the important thing is to release, do it, and do it
> easily and
>     > often.
>     >
>     >     Thanks
>     >
>     >
>     >
>     >     El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
>     >     christofer.dutz@c-ware.de<ma...@c-ware.de>>)
>     > escribió:
>     >
>     >
>     >     Ok,
>     >
>     >     I'll write this a last time as I do feel like we're going in
> circles
>     > and
>     >     will from now on not participate in any discussion involving
> releasing
>     > on a
>     >     CI server.
>     >
>     >     A correct Maven release would use (There will be some additional
>     > profiles
>     >     to activate to include all modules)
>     >
>     >     1) the "mvn release:branch" call in order to create the branch
> and bump
>     >     the version of develop to the next version.
>     >     2) the "mvn release:prepare" to change the pom to the release
> version,
>     > set
>     >     the timestamp in the pom (for reproducible builds) build ... if
> all
>     > tests
>     >     are good, commit the changes, tag this commit, update the poms
> to the
>     > next
>     >     development version, commit those changes and push everything.
>     >     3) the "mvn release:perform" which will checkout the tagged
> version
>     > build
>     >     everything with the "apache-release" profile turned on (Which
> causes
>     > the
>     >     source.jars, Javadoc.jars, hashes and gpg singatures to be
> created as
>     > well
>     >     as the assembly) This also deploys the built artifacts to Nexus.
>     >
>     >     Most of that you are already doing on the CI server however
> you're not
>     >     letting it do all automatically (For lack of credentials)
>     >
>     >     But ... if you would just be doing those steps on the RM machine.
>     >
>     >     Chris
>     >
>     >
>     >
>     >
>     >
>     >     Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
>     > <ma...@adobe.com.INVALID>>:
>     >
>     >
>     >
>     >         On 3/25/20, 4:46 PM, "Carlos Rovira" <
> carlosrovira@apache.org
>     > <ma...@apache.org>> wrote:
>     >
>     >             > What I want to know is what the Maven commands should
> be to
>     >     create a
>     >             > release in this "conventional process" you are
> referring to.
>     >             >
>     >
>     >             If you want to know what's the conventional maven
> process is, I
>     >     think I can
>     >             ask Chris if he wants to work with me on that process,
> since he
>     >     already did
>     >             many other Apache projects, we can expect the process is
> what
>     > is
>     >     needed for
>     >             us to. But just expect that will be a series of standard
> maven
>     >     commands
>     >             (prepare, release,...), so nothing strange at all (I
> expect).
>     >
>     >             Do you want us to do that?
>     >
>     >         Yes.  I want to know what the series of standard Maven
> commands
>     > are.
>     >     Then we can figure out how to convert them to run on the CI
> server.
>     >
>     >         -Alex
>     >
>     >             Thanks
>     >
>     >
>     >             >
>     >             > Maybe someone else can explain better than me.
>     >             >
>     >             > -Alex
>     >             >
>     >             > On 3/25/20, 2:22 PM, "Carlos Rovira" <
>     > carlosrovira@apache.org<ma...@apache.org>>
>     >     wrote:
>     >             >
>     >             >     Hi Alex,
>     >             >
>     >             >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>     >             > (<aharui@adobe.com.invalid<mailto:
> aharui@adobe.com.invalid
>     > >>)
>     >             >     escribió:
>     >             >
>     >             >     > Carlos,
>     >             >     >
>     >             >     > I'm pretty sure that part of the "conventional
> process"
>     >     you want to
>     >             > try
>     >             >     > requires filling the staging repo from a local
> machine.
>     >             >     >
>     >             >
>     >             >     This is what we already did. If you go to [1] will
> see
>     > [2].
>     >     That was
>     >             > the
>     >             >     upload of compiler to the staging repo. When
> trying to do
>     >     the same for
>     >             >     typedefs it failed when trying to fill repo from
> local
>     >     machine. I think
>     >             >     Chris or I should not take more time in trying to
> fix Ant
>     >     scripts that
>     >             > are
>     >             >     failing.
>     >             >
>     >             >     Thanks
>     >             >
>     >             >     [1]
>     >             >
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840951898&amp;sdata=U8BmlIdd6ZajuOEn1jNCWlrJbAn%2BV1BQbwhsXkRc854%3D&amp;reserved=0
>     >             >     [2]
>     >             >
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840951898&amp;sdata=PKLdBG1DimNg3wANGcs3cTfiR3nelEed1tBZM%2FvVU%2Bk%3D&amp;reserved=0
>     >             >
>     >             >
>     >             >
>     >             >
>     >             >     >
>     >             >     > --
>     >             >     > Carlos Rovira
>     >             >     >
>     >             >
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840951898&amp;sdata=3uxFi47xpWG7B3m7OF%2FqniyK7yb3uUDZD4CCgaUtwPM%3D&amp;reserved=0
>     >             >     >
>     >             >     >
>     >             >     >
>     >             >     >
>     >             >
>     >             >
>     >             >
>     >
>     >             --
>     >             Carlos Rovira
>     >
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=xtI3M5bsNTrNr5pz7b7cDKaWaqkcbLGrcovspTCH8xk%3D&amp;reserved=0
>     >
>     >
>     >
>     >
>     >
>     >
>     >     --
>     >
>     >     Frédéric Gilli
>     >
>     >     mob.0668542622
>     >
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=FmIv8VzENVjH8Lbe%2FYiZb%2BtripSYb5JG%2F5hdWvnVW9M%3D&amp;reserved=0
>     >
>     >     [cid:171168797bb6addd0331]<
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=FmIv8VzENVjH8Lbe%2FYiZb%2BtripSYb5JG%2F5hdWvnVW9M%3D&amp;reserved=0
>     > >
>     >
>     >
>     >
>     >
>     >     --
>     >
>     >     Piotr Zarzycki
>     >
>     >     Patreon:
>     >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=xF1gfNEs6uwJ3oyQ%2BdzA4PJ0eB%2BcGmaBBvas8KVYk9c%3D&amp;reserved=0
>     >
>     >
>     >
>     >
>
>     --
>     Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=xtI3M5bsNTrNr5pz7b7cDKaWaqkcbLGrcovspTCH8xk%3D&amp;reserved=0
>
>
>
>

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

Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.
I share your concern with the precedent being set here.  I don't think the folks behind these changes should be off the hook for getting the CI steps to work again.  Otherwise, any of us can go break stuff under the rationale of making something else better and let someone else deal with the mess.

Still, certain things have to be done.  I think there is consensus that a release should be doable on a local machine or the CI server.  So, hopefully Carlos is off to not just create an RC, but also document the steps required to do this end-to-end on a local machine by actually doing it.  That made sense while waiting for Sunday to roll around to see if that gets past the timestamp issue in the SWCs.

If you have time to tweak the CI steps and see if they work to help get them working again, feel free to do so.  I will hopefully have cycles to help.   The credentials are in the private@ archives.  I recommend creating a completely new set of steps by cloning the old jobs as needed.  For example we won't need the 1a (utils) step (or probably the other utils steps) anymore.  A differently named step or two is needed to match what Carlos did for the compiler-build-tools release.

If you can help them resolve the SWC timestamp issue, I hope to see the folks who committed to restoring these steps back to working order will complete that task.

My 2 cents,
-Alex

On 3/29/20, 10:43 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:

    I guess I misunderstood. I thought we were only talking about the compiler-build-tools release.
    
    Carlos, I of course don’t mind you doing the work. I have plenty on my plate. I’m concerned with the process. Although I haven’t been following the threads closely enough to understand the whole technical debate, I did understand that Alex and others have expressed reservations (e.g. should the release actually use ant to verify the ant build). Has this debate reached a conclusion that enjoys a consensus? If not, there should probably be a vote. I don’t want to encourage a dynamic where debates are won by unilateral action.
    
    If everyone feels comfortable with Carlos releasing with mvn, then I won’t object. If there are reservations then I’d still like to give it another week, and see if an RM newbie like me can apply the process suggested by Alex.
    
    Thanks.
    
    From: Carlos Rovira<ma...@apache.org>
    Sent: Sunday, March 29, 2020 7:34 PM
    To: Apache Royale Development<ma...@royale.apache.org>
    Subject: Re: Releasing: Finally giving up
    
    Hi Yishay,
    
    I think we were all in agreement so I'll make the release. Right now we're
    voting the compiler-build-tools 1.2.0 release
    As soon as this is approved, I'll continue withe 0.9.7 release.
    
    compiler build tools 1.2.0 is done to release some small changes for
    reproducible builds and check the optional path about to release compiler
    build tools or jburg versions in the future (that should be very rare).
    
    Thanks
    
    
    El dom., 29 mar. 2020 a las 15:59, Yishay Weiss (<yi...@hotmail.com>)
    escribió:
    
    > Ok, I’m ready. What’s next? Do I need to cancel an RC? How do I login to
    > Jenkins? Where do I start?
    >
    > From: Alex Harui<ma...@adobe.com>
    > Sent: Thursday, March 26, 2020 8:50 PM
    > To: dev@royale.apache.org<ma...@royale.apache.org>; Yishay
    > Weiss<ma...@hotmail.com>
    > Subject: Re: Releasing: Finally giving up
    >
    > @Yishay Weiss
    >
    > Let's wait until the set of Maven steps are available from Chris and
    > Carlos.  Then I will try to find some cycles to help you.  Because of where
    > I live, where the schools are closed, and my kids schedule, I have good
    > weeks and bad weeks for having time for work, so it will be best to wait to
    > try a release until we have the steps and it is one of my good weeks (next
    > good week starts this Friday at 5pm my time).
    >
    > Thanks,
    > -Alex
    >
    > On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
    >
    >     Hi All,
    >
    >     I too, feel very uncomfortable participating in these threads. While
    > grateful to Carlos and Chris for their work I’m very annoyed with the tone
    > of ultimatums and doom and gloom. Alex has put in a lot of work into this
    > and I trust his concerns are technical, rather than protecting his ego as
    > has been suggested. We need to get this discussion back on technical tracks.
    >
    >     Since Chris has given up, and it looks like Carlos has as well, I
    > volunteer to start the release process from scratch next Sunday, which is
    > after Israel has switched to day light saving. I will try to do the process
    > incrementally and in parallel to my other tasks. If by the end of the week
    > it turns out the process is too cumbersome and cannot realistically be made
    > to work smoothly I will be in favor of changing the requirements to enable
    > Chris’s mvn setup to be the main release tool.
    >
    >     Thanks,
    >     Yishay
    >
    >     From: Piotr Zarzycki<ma...@gmail.com>
    >     Sent: Thursday, March 26, 2020 1:27 PM
    >     To: Apache Royale Development<ma...@royale.apache.org>
    >     Subject: Re: Releasing: Finally giving up
    >
    >     Hi All,
    >
    >     I'm member of Apache Foundation for quite some time now. I think I
    > have wrote maybe 2-3 emails during that time on members mailing list. -
    > Why? - well I'm a person which doesn't like never ending stories, stories
    > which are not end up with consensus nor action and I'm sorry but this is
    > how it looks like in most cases there. Here we are in Apache Royale project
    > where this thread ended up exactly the same - never ending story. - As PMC
    > of this project I would like to say enough! :)
    >
    >     I had hope that when Carlos and Chris try CI steps and in the process
    > they may have some issues, but they will end up in the same place as I
    > ended up where I was able to prepare RC1 in about 2h without the problem.
    > It turns out that they end up in the place where I have started, in the
    > place where I have spend 5-6 days of work to finally reach stable point.
    > They ended up frustrated in the same way as I was!
    >
    >     I really don't care now what kind of issue they have now, whether it's
    > fixable or not - I just have enough of those never ending discussions where
    > there is absolutely no results.
    >
    >     I met Chris in US in Miami and I have spend with him best time ever,
    > he is really great developer - if he is saying that he will have release
    > process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not
    > in a week - start today!
    >
    >     Please start whole work on that and make it happen. I will be the
    > first who try the process and maybe with Chris's help we will solve also
    > issue with uploading artifacts to staging area which we had.
    >
    >     Good Luck,
    >     Piotr
    >
    >     czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
    > contact@cristallium.com>> napisał(a):
    >
    >     Hi Guys,
    >
    >     I'm a lover of Flex dev guy since more than 10 years, been members of
    > Flex group on Montpellier (France) at golden age of Flex and go at all
    > conferences when Michaël Chaize came to Montpellier (and using Flex every
    > day).
    >
    >     First of all I want to thank every one of you for your hard work, and
    > congratulate you for the actual Apache Royale capabilities.
    >     With the last features (especialy datagrid), today your great work
    > make possible to use Apache Royale in business application. Of course,
    > there are bugs, but when reported, it's quickly fix, this is great.
    >
    >     Now, this is a huge opportunity but also risk for all guys like me to
    > adop Apache Royale for futur projects or use it instead of using Air when
    > it's possible.
    >     Personnaly, I first use it on my own Webs applications and perhaps for
    > my customers on little applications for the begin. My big enormous worry is
    > to use it and be alone in front of a SDK bug.
    >     Seeing new release every 1 or 2 months should certainly reassure me.
    > For now I see SDK 0.9.7 since a lot of time and this make me affraid and I
    > don't understand why there is no 0.9.8.
    >
    >     I'm speaking as an Apache Royale SDK user : I'm very sad to read these
    > debates on the subject of tools to use for making release. I don't care
    > about tools nedeed or not to build the release SDK.
    >     I would like use Apache Royale to build RAD (Rapid Application Dev)
    > Web applications and see more and more SDK features added, and participate
    > to project (like today) by reporting bug  by using my time on isolate the
    > bug and make tests cases with screenshoots to save your time in fixing it.
    >
    >     Using Reac, Bootstrap, AngularJS or other similar is a back to 80's.
    > How can I explain my customer that I need 3 ou 4 days to make thinks that
    > took me 1 day with Flex ?
    >     The big competitive advantage of Apache Royale is not only be able to
    > re-use Flex apps but is also simplicity and time saving where other SDK
    > can't do it. (I think you already know that)
    >
    >     I am convinced that all guys like me will jump using Royale when they
    > will know that there is a bug free SDK with fast evolution available.
    > (unfortunaly it's not known enough, nobody know someone working in
    > newspapers ?)
    >
    >     So please, I beg you, don't waste your time on things that are not
    > essential and like Carlos said, go forward. From outside view, Apache
    > Royale stay sticky to 0.9.7.
    >
    >     You are so close of a v1.0, I hope see it very soon and other releases
    > with bugs fix every 1, 2 or 3 months.
    >     Consider my comments as support and not criticism.
    >
    >     Thanks again for your hard work.
    >
    >     Long life and success to Apache Royale !
    >
    >     Fred
    >
    >
    >
    >     Le 26.03.2020 09:26, Carlos Rovira a écrit :
    >     Hi,
    >
    >     that's amazingly simple, so I think we should go that way without
    > doubt. I
    >     think reached this point there's a clear sense of that we need to go
    > that
    >     route.
    >
    >     We tried our best to stick with the previous process and we're all
    >     loosing lots of time. Then currently seems no more people in the
    > community
    >     was interested in this thread, event to comment a single line (here or
    > in
    >     the other users list thread), what means that or there's no more people
    >     like us in this project or people really is not interested and just
    > want us
    >     to release and go forward.
    >
    >     As previously I think most of the PMCs here (Om, Josh, Greg and me for
    >     sure), probably Yishay for his concise comments are more for this.
    >     My thinking is that the right now I think only 2 PMCs are for CI
    > Server,
    >     and other one that is uncertainly but didn't try the CI Server.
    >
    >     I think all can live together while is not a must for the rest that
    > don't
    >     want it the others option, so what's about if we release with the
    >     super-simple steps Chris proposal, and others wanting to use CI do that
    >     when is their RM turn ? (of course maintaining it and making it work
    > for
    >     his release without requiring nothing for the rest that doesn't want
    > it).
    >
    >     Release as other projects do is recommended but not required, the same
    > as
    >     the actual CI server (but this one should be less recommended since is
    > a
    >     royale-only practice not seen in any other place).
    >
    >     What's the important thing is to release, do it, and do it easily and
    > often.
    >
    >     Thanks
    >
    >
    >
    >     El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
    >     christofer.dutz@c-ware.de<ma...@c-ware.de>>)
    > escribió:
    >
    >
    >     Ok,
    >
    >     I'll write this a last time as I do feel like we're going in circles
    > and
    >     will from now on not participate in any discussion involving releasing
    > on a
    >     CI server.
    >
    >     A correct Maven release would use (There will be some additional
    > profiles
    >     to activate to include all modules)
    >
    >     1) the "mvn release:branch" call in order to create the branch and bump
    >     the version of develop to the next version.
    >     2) the "mvn release:prepare" to change the pom to the release version,
    > set
    >     the timestamp in the pom (for reproducible builds) build ... if all
    > tests
    >     are good, commit the changes, tag this commit, update the poms to the
    > next
    >     development version, commit those changes and push everything.
    >     3) the "mvn release:perform" which will checkout the tagged version
    > build
    >     everything with the "apache-release" profile turned on (Which causes
    > the
    >     source.jars, Javadoc.jars, hashes and gpg singatures to be created as
    > well
    >     as the assembly) This also deploys the built artifacts to Nexus.
    >
    >     Most of that you are already doing on the CI server however you're not
    >     letting it do all automatically (For lack of credentials)
    >
    >     But ... if you would just be doing those steps on the RM machine.
    >
    >     Chris
    >
    >
    >
    >
    >
    >     Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
    > <ma...@adobe.com.INVALID>>:
    >
    >
    >
    >         On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org
    > <ma...@apache.org>> wrote:
    >
    >             > What I want to know is what the Maven commands should be to
    >     create a
    >             > release in this "conventional process" you are referring to.
    >             >
    >
    >             If you want to know what's the conventional maven process is, I
    >     think I can
    >             ask Chris if he wants to work with me on that process, since he
    >     already did
    >             many other Apache projects, we can expect the process is what
    > is
    >     needed for
    >             us to. But just expect that will be a series of standard maven
    >     commands
    >             (prepare, release,...), so nothing strange at all (I expect).
    >
    >             Do you want us to do that?
    >
    >         Yes.  I want to know what the series of standard Maven commands
    > are.
    >     Then we can figure out how to convert them to run on the CI server.
    >
    >         -Alex
    >
    >             Thanks
    >
    >
    >             >
    >             > Maybe someone else can explain better than me.
    >             >
    >             > -Alex
    >             >
    >             > On 3/25/20, 2:22 PM, "Carlos Rovira" <
    > carlosrovira@apache.org<ma...@apache.org>>
    >     wrote:
    >             >
    >             >     Hi Alex,
    >             >
    >             >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
    >             > (<aharui@adobe.com.invalid<mailto:aharui@adobe.com.invalid
    > >>)
    >             >     escribió:
    >             >
    >             >     > Carlos,
    >             >     >
    >             >     > I'm pretty sure that part of the "conventional process"
    >     you want to
    >             > try
    >             >     > requires filling the staging repo from a local machine.
    >             >     >
    >             >
    >             >     This is what we already did. If you go to [1] will see
    > [2].
    >     That was
    >             > the
    >             >     upload of compiler to the staging repo. When trying to do
    >     the same for
    >             >     typedefs it failed when trying to fill repo from local
    >     machine. I think
    >             >     Chris or I should not take more time in trying to fix Ant
    >     scripts that
    >             > are
    >             >     failing.
    >             >
    >             >     Thanks
    >             >
    >             >     [1]
    >             >
    >
    > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840951898&amp;sdata=U8BmlIdd6ZajuOEn1jNCWlrJbAn%2BV1BQbwhsXkRc854%3D&amp;reserved=0
    >             >     [2]
    >             >
    >
    > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840951898&amp;sdata=PKLdBG1DimNg3wANGcs3cTfiR3nelEed1tBZM%2FvVU%2Bk%3D&amp;reserved=0
    >             >
    >             >
    >             >
    >             >
    >             >     >
    >             >     > --
    >             >     > Carlos Rovira
    >             >     >
    >             >
    >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840951898&amp;sdata=3uxFi47xpWG7B3m7OF%2FqniyK7yb3uUDZD4CCgaUtwPM%3D&amp;reserved=0
    >             >     >
    >             >     >
    >             >     >
    >             >     >
    >             >
    >             >
    >             >
    >
    >             --
    >             Carlos Rovira
    >
    >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=xtI3M5bsNTrNr5pz7b7cDKaWaqkcbLGrcovspTCH8xk%3D&amp;reserved=0
    >
    >
    >
    >
    >
    >
    >     --
    >
    >     Frédéric Gilli
    >
    >     mob.0668542622
    >
    >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=FmIv8VzENVjH8Lbe%2FYiZb%2BtripSYb5JG%2F5hdWvnVW9M%3D&amp;reserved=0
    >
    >     [cid:171168797bb6addd0331]<
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=FmIv8VzENVjH8Lbe%2FYiZb%2BtripSYb5JG%2F5hdWvnVW9M%3D&amp;reserved=0
    > >
    >
    >
    >
    >
    >     --
    >
    >     Piotr Zarzycki
    >
    >     Patreon:
    > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=xF1gfNEs6uwJ3oyQ%2BdzA4PJ0eB%2BcGmaBBvas8KVYk9c%3D&amp;reserved=0
    >
    >
    >
    >
    
    --
    Carlos Rovira
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C875a5f578f66433d903f08d7d408a03e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637211005840961853&amp;sdata=xtI3M5bsNTrNr5pz7b7cDKaWaqkcbLGrcovspTCH8xk%3D&amp;reserved=0
    
    


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi Yishay,

I'm in the same page. I didn't want to take over without Alex ok (that he
gives in this thread), as he said that Chris and I go ahead, I didn't want
to do nothing without you letting me do it, since you expressed that you
want to take over. As you said, ok to left it to me, I said ok. All of this
taking into consideration that others like Om, Josh, Greg....already
encourage us to do so. But although they encouraged me, I didn't want to do
without ALL people ok with me doing it.

In the other hand, the current vote to release build-tools is needed to
release 0.9.7 of the whole project.

In resume, I don't want to take over if people are not ok with me doing it.
But I started the build-tools release since I though we have all in the
same page.




El dom., 29 mar. 2020 a las 19:43, Yishay Weiss (<yi...@hotmail.com>)
escribió:

> I guess I misunderstood. I thought we were only talking about the
> compiler-build-tools release.
>
> Carlos, I of course don’t mind you doing the work. I have plenty on my
> plate. I’m concerned with the process. Although I haven’t been following
> the threads closely enough to understand the whole technical debate, I did
> understand that Alex and others have expressed reservations (e.g. should
> the release actually use ant to verify the ant build). Has this debate
> reached a conclusion that enjoys a consensus? If not, there should probably
> be a vote. I don’t want to encourage a dynamic where debates are won by
> unilateral action.
>
> If everyone feels comfortable with Carlos releasing with mvn, then I won’t
> object. If there are reservations then I’d still like to give it another
> week, and see if an RM newbie like me can apply the process suggested by
> Alex.
>
> Thanks.
>
> From: Carlos Rovira<ma...@apache.org>
> Sent: Sunday, March 29, 2020 7:34 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Releasing: Finally giving up
>
> Hi Yishay,
>
> I think we were all in agreement so I'll make the release. Right now we're
> voting the compiler-build-tools 1.2.0 release
> As soon as this is approved, I'll continue withe 0.9.7 release.
>
> compiler build tools 1.2.0 is done to release some small changes for
> reproducible builds and check the optional path about to release compiler
> build tools or jburg versions in the future (that should be very rare).
>
> Thanks
>
>
> El dom., 29 mar. 2020 a las 15:59, Yishay Weiss (<yi...@hotmail.com>)
> escribió:
>
> > Ok, I’m ready. What’s next? Do I need to cancel an RC? How do I login to
> > Jenkins? Where do I start?
> >
> > From: Alex Harui<ma...@adobe.com>
> > Sent: Thursday, March 26, 2020 8:50 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>; Yishay
> > Weiss<ma...@hotmail.com>
> > Subject: Re: Releasing: Finally giving up
> >
> > @Yishay Weiss
> >
> > Let's wait until the set of Maven steps are available from Chris and
> > Carlos.  Then I will try to find some cycles to help you.  Because of
> where
> > I live, where the schools are closed, and my kids schedule, I have good
> > weeks and bad weeks for having time for work, so it will be best to wait
> to
> > try a release until we have the steps and it is one of my good weeks
> (next
> > good week starts this Friday at 5pm my time).
> >
> > Thanks,
> > -Alex
> >
> > On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> >     Hi All,
> >
> >     I too, feel very uncomfortable participating in these threads. While
> > grateful to Carlos and Chris for their work I’m very annoyed with the
> tone
> > of ultimatums and doom and gloom. Alex has put in a lot of work into this
> > and I trust his concerns are technical, rather than protecting his ego as
> > has been suggested. We need to get this discussion back on technical
> tracks.
> >
> >     Since Chris has given up, and it looks like Carlos has as well, I
> > volunteer to start the release process from scratch next Sunday, which is
> > after Israel has switched to day light saving. I will try to do the
> process
> > incrementally and in parallel to my other tasks. If by the end of the
> week
> > it turns out the process is too cumbersome and cannot realistically be
> made
> > to work smoothly I will be in favor of changing the requirements to
> enable
> > Chris’s mvn setup to be the main release tool.
> >
> >     Thanks,
> >     Yishay
> >
> >     From: Piotr Zarzycki<ma...@gmail.com>
> >     Sent: Thursday, March 26, 2020 1:27 PM
> >     To: Apache Royale Development<ma...@royale.apache.org>
> >     Subject: Re: Releasing: Finally giving up
> >
> >     Hi All,
> >
> >     I'm member of Apache Foundation for quite some time now. I think I
> > have wrote maybe 2-3 emails during that time on members mailing list. -
> > Why? - well I'm a person which doesn't like never ending stories, stories
> > which are not end up with consensus nor action and I'm sorry but this is
> > how it looks like in most cases there. Here we are in Apache Royale
> project
> > where this thread ended up exactly the same - never ending story. - As
> PMC
> > of this project I would like to say enough! :)
> >
> >     I had hope that when Carlos and Chris try CI steps and in the process
> > they may have some issues, but they will end up in the same place as I
> > ended up where I was able to prepare RC1 in about 2h without the problem.
> > It turns out that they end up in the place where I have started, in the
> > place where I have spend 5-6 days of work to finally reach stable point.
> > They ended up frustrated in the same way as I was!
> >
> >     I really don't care now what kind of issue they have now, whether
> it's
> > fixable or not - I just have enough of those never ending discussions
> where
> > there is absolutely no results.
> >
> >     I met Chris in US in Miami and I have spend with him best time ever,
> > he is really great developer - if he is saying that he will have release
> > process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not
> > in a week - start today!
> >
> >     Please start whole work on that and make it happen. I will be the
> > first who try the process and maybe with Chris's help we will solve also
> > issue with uploading artifacts to staging area which we had.
> >
> >     Good Luck,
> >     Piotr
> >
> >     czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> > contact@cristallium.com>> napisał(a):
> >
> >     Hi Guys,
> >
> >     I'm a lover of Flex dev guy since more than 10 years, been members of
> > Flex group on Montpellier (France) at golden age of Flex and go at all
> > conferences when Michaël Chaize came to Montpellier (and using Flex every
> > day).
> >
> >     First of all I want to thank every one of you for your hard work, and
> > congratulate you for the actual Apache Royale capabilities.
> >     With the last features (especialy datagrid), today your great work
> > make possible to use Apache Royale in business application. Of course,
> > there are bugs, but when reported, it's quickly fix, this is great.
> >
> >     Now, this is a huge opportunity but also risk for all guys like me to
> > adop Apache Royale for futur projects or use it instead of using Air when
> > it's possible.
> >     Personnaly, I first use it on my own Webs applications and perhaps
> for
> > my customers on little applications for the begin. My big enormous worry
> is
> > to use it and be alone in front of a SDK bug.
> >     Seeing new release every 1 or 2 months should certainly reassure me.
> > For now I see SDK 0.9.7 since a lot of time and this make me affraid and
> I
> > don't understand why there is no 0.9.8.
> >
> >     I'm speaking as an Apache Royale SDK user : I'm very sad to read
> these
> > debates on the subject of tools to use for making release. I don't care
> > about tools nedeed or not to build the release SDK.
> >     I would like use Apache Royale to build RAD (Rapid Application Dev)
> > Web applications and see more and more SDK features added, and
> participate
> > to project (like today) by reporting bug  by using my time on isolate the
> > bug and make tests cases with screenshoots to save your time in fixing
> it.
> >
> >     Using Reac, Bootstrap, AngularJS or other similar is a back to 80's.
> > How can I explain my customer that I need 3 ou 4 days to make thinks that
> > took me 1 day with Flex ?
> >     The big competitive advantage of Apache Royale is not only be able to
> > re-use Flex apps but is also simplicity and time saving where other SDK
> > can't do it. (I think you already know that)
> >
> >     I am convinced that all guys like me will jump using Royale when they
> > will know that there is a bug free SDK with fast evolution available.
> > (unfortunaly it's not known enough, nobody know someone working in
> > newspapers ?)
> >
> >     So please, I beg you, don't waste your time on things that are not
> > essential and like Carlos said, go forward. From outside view, Apache
> > Royale stay sticky to 0.9.7.
> >
> >     You are so close of a v1.0, I hope see it very soon and other
> releases
> > with bugs fix every 1, 2 or 3 months.
> >     Consider my comments as support and not criticism.
> >
> >     Thanks again for your hard work.
> >
> >     Long life and success to Apache Royale !
> >
> >     Fred
> >
> >
> >
> >     Le 26.03.2020 09:26, Carlos Rovira a écrit :
> >     Hi,
> >
> >     that's amazingly simple, so I think we should go that way without
> > doubt. I
> >     think reached this point there's a clear sense of that we need to go
> > that
> >     route.
> >
> >     We tried our best to stick with the previous process and we're all
> >     loosing lots of time. Then currently seems no more people in the
> > community
> >     was interested in this thread, event to comment a single line (here
> or
> > in
> >     the other users list thread), what means that or there's no more
> people
> >     like us in this project or people really is not interested and just
> > want us
> >     to release and go forward.
> >
> >     As previously I think most of the PMCs here (Om, Josh, Greg and me
> for
> >     sure), probably Yishay for his concise comments are more for this.
> >     My thinking is that the right now I think only 2 PMCs are for CI
> > Server,
> >     and other one that is uncertainly but didn't try the CI Server.
> >
> >     I think all can live together while is not a must for the rest that
> > don't
> >     want it the others option, so what's about if we release with the
> >     super-simple steps Chris proposal, and others wanting to use CI do
> that
> >     when is their RM turn ? (of course maintaining it and making it work
> > for
> >     his release without requiring nothing for the rest that doesn't want
> > it).
> >
> >     Release as other projects do is recommended but not required, the
> same
> > as
> >     the actual CI server (but this one should be less recommended since
> is
> > a
> >     royale-only practice not seen in any other place).
> >
> >     What's the important thing is to release, do it, and do it easily and
> > often.
> >
> >     Thanks
> >
> >
> >
> >     El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
> >     christofer.dutz@c-ware.de<ma...@c-ware.de>>)
> > escribió:
> >
> >
> >     Ok,
> >
> >     I'll write this a last time as I do feel like we're going in circles
> > and
> >     will from now on not participate in any discussion involving
> releasing
> > on a
> >     CI server.
> >
> >     A correct Maven release would use (There will be some additional
> > profiles
> >     to activate to include all modules)
> >
> >     1) the "mvn release:branch" call in order to create the branch and
> bump
> >     the version of develop to the next version.
> >     2) the "mvn release:prepare" to change the pom to the release
> version,
> > set
> >     the timestamp in the pom (for reproducible builds) build ... if all
> > tests
> >     are good, commit the changes, tag this commit, update the poms to the
> > next
> >     development version, commit those changes and push everything.
> >     3) the "mvn release:perform" which will checkout the tagged version
> > build
> >     everything with the "apache-release" profile turned on (Which causes
> > the
> >     source.jars, Javadoc.jars, hashes and gpg singatures to be created as
> > well
> >     as the assembly) This also deploys the built artifacts to Nexus.
> >
> >     Most of that you are already doing on the CI server however you're
> not
> >     letting it do all automatically (For lack of credentials)
> >
> >     But ... if you would just be doing those steps on the RM machine.
> >
> >     Chris
> >
> >
> >
> >
> >
> >     Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
> > <ma...@adobe.com.INVALID>>:
> >
> >
> >
> >         On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org
> > <ma...@apache.org>> wrote:
> >
> >             > What I want to know is what the Maven commands should be to
> >     create a
> >             > release in this "conventional process" you are referring
> to.
> >             >
> >
> >             If you want to know what's the conventional maven process
> is, I
> >     think I can
> >             ask Chris if he wants to work with me on that process, since
> he
> >     already did
> >             many other Apache projects, we can expect the process is what
> > is
> >     needed for
> >             us to. But just expect that will be a series of standard
> maven
> >     commands
> >             (prepare, release,...), so nothing strange at all (I expect).
> >
> >             Do you want us to do that?
> >
> >         Yes.  I want to know what the series of standard Maven commands
> > are.
> >     Then we can figure out how to convert them to run on the CI server.
> >
> >         -Alex
> >
> >             Thanks
> >
> >
> >             >
> >             > Maybe someone else can explain better than me.
> >             >
> >             > -Alex
> >             >
> >             > On 3/25/20, 2:22 PM, "Carlos Rovira" <
> > carlosrovira@apache.org<ma...@apache.org>>
> >     wrote:
> >             >
> >             >     Hi Alex,
> >             >
> >             >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
> >             > (<aharui@adobe.com.invalid<mailto:aharui@adobe.com.invalid
> > >>)
> >             >     escribió:
> >             >
> >             >     > Carlos,
> >             >     >
> >             >     > I'm pretty sure that part of the "conventional
> process"
> >     you want to
> >             > try
> >             >     > requires filling the staging repo from a local
> machine.
> >             >     >
> >             >
> >             >     This is what we already did. If you go to [1] will see
> > [2].
> >     That was
> >             > the
> >             >     upload of compiler to the staging repo. When trying to
> do
> >     the same for
> >             >     typedefs it failed when trying to fill repo from local
> >     machine. I think
> >             >     Chris or I should not take more time in trying to fix
> Ant
> >     scripts that
> >             > are
> >             >     failing.
> >             >
> >             >     Thanks
> >             >
> >             >     [1]
> >             >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=SzmPqflLUwAxBCIkm%2BFn2BO8OZVJH1Gp66CVl349I3g%3D&amp;reserved=0
> >             >     [2]
> >             >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=VONdkWMhQpEGhSlVoXwFuhdnApXmrSaTnSP%2FDeH6stc%3D&amp;reserved=0
> >             >
> >             >
> >             >
> >             >
> >             >     >
> >             >     > --
> >             >     > Carlos Rovira
> >             >     >
> >             >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=jPUGE0ohIi%2BFYoKZefaob1pSsIjC4AEEjE04N27FiI0%3D&amp;reserved=0
> >             >     >
> >             >     >
> >             >     >
> >             >     >
> >             >
> >             >
> >             >
> >
> >             --
> >             Carlos Rovira
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=bkaODFbcmtjdxlibVdfQRKtIzcXImHIQ4HpKQOTgLM8%3D&amp;reserved=0
> >
> >
> >
> >
> >
> >
> >     --
> >
> >     Frédéric Gilli
> >
> >     mob.0668542622
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
> >
> >     [cid:171168797bb6addd0331]<
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
> > >
> >
> >
> >
> >
> >     --
> >
> >     Piotr Zarzycki
> >
> >     Patreon:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=j%2BLcn3n8gF9Ro8d0S5EgcHamMg42sVnJXBymeIeQEUk%3D&amp;reserved=0
> >
> >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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

RE: Releasing: Finally giving up

Posted by Yishay Weiss <yi...@hotmail.com>.
I guess I misunderstood. I thought we were only talking about the compiler-build-tools release.

Carlos, I of course don’t mind you doing the work. I have plenty on my plate. I’m concerned with the process. Although I haven’t been following the threads closely enough to understand the whole technical debate, I did understand that Alex and others have expressed reservations (e.g. should the release actually use ant to verify the ant build). Has this debate reached a conclusion that enjoys a consensus? If not, there should probably be a vote. I don’t want to encourage a dynamic where debates are won by unilateral action.

If everyone feels comfortable with Carlos releasing with mvn, then I won’t object. If there are reservations then I’d still like to give it another week, and see if an RM newbie like me can apply the process suggested by Alex.

Thanks.

From: Carlos Rovira<ma...@apache.org>
Sent: Sunday, March 29, 2020 7:34 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Releasing: Finally giving up

Hi Yishay,

I think we were all in agreement so I'll make the release. Right now we're
voting the compiler-build-tools 1.2.0 release
As soon as this is approved, I'll continue withe 0.9.7 release.

compiler build tools 1.2.0 is done to release some small changes for
reproducible builds and check the optional path about to release compiler
build tools or jburg versions in the future (that should be very rare).

Thanks


El dom., 29 mar. 2020 a las 15:59, Yishay Weiss (<yi...@hotmail.com>)
escribió:

> Ok, I’m ready. What’s next? Do I need to cancel an RC? How do I login to
> Jenkins? Where do I start?
>
> From: Alex Harui<ma...@adobe.com>
> Sent: Thursday, March 26, 2020 8:50 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>; Yishay
> Weiss<ma...@hotmail.com>
> Subject: Re: Releasing: Finally giving up
>
> @Yishay Weiss
>
> Let's wait until the set of Maven steps are available from Chris and
> Carlos.  Then I will try to find some cycles to help you.  Because of where
> I live, where the schools are closed, and my kids schedule, I have good
> weeks and bad weeks for having time for work, so it will be best to wait to
> try a release until we have the steps and it is one of my good weeks (next
> good week starts this Friday at 5pm my time).
>
> Thanks,
> -Alex
>
> On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
>     Hi All,
>
>     I too, feel very uncomfortable participating in these threads. While
> grateful to Carlos and Chris for their work I’m very annoyed with the tone
> of ultimatums and doom and gloom. Alex has put in a lot of work into this
> and I trust his concerns are technical, rather than protecting his ego as
> has been suggested. We need to get this discussion back on technical tracks.
>
>     Since Chris has given up, and it looks like Carlos has as well, I
> volunteer to start the release process from scratch next Sunday, which is
> after Israel has switched to day light saving. I will try to do the process
> incrementally and in parallel to my other tasks. If by the end of the week
> it turns out the process is too cumbersome and cannot realistically be made
> to work smoothly I will be in favor of changing the requirements to enable
> Chris’s mvn setup to be the main release tool.
>
>     Thanks,
>     Yishay
>
>     From: Piotr Zarzycki<ma...@gmail.com>
>     Sent: Thursday, March 26, 2020 1:27 PM
>     To: Apache Royale Development<ma...@royale.apache.org>
>     Subject: Re: Releasing: Finally giving up
>
>     Hi All,
>
>     I'm member of Apache Foundation for quite some time now. I think I
> have wrote maybe 2-3 emails during that time on members mailing list. -
> Why? - well I'm a person which doesn't like never ending stories, stories
> which are not end up with consensus nor action and I'm sorry but this is
> how it looks like in most cases there. Here we are in Apache Royale project
> where this thread ended up exactly the same - never ending story. - As PMC
> of this project I would like to say enough! :)
>
>     I had hope that when Carlos and Chris try CI steps and in the process
> they may have some issues, but they will end up in the same place as I
> ended up where I was able to prepare RC1 in about 2h without the problem.
> It turns out that they end up in the place where I have started, in the
> place where I have spend 5-6 days of work to finally reach stable point.
> They ended up frustrated in the same way as I was!
>
>     I really don't care now what kind of issue they have now, whether it's
> fixable or not - I just have enough of those never ending discussions where
> there is absolutely no results.
>
>     I met Chris in US in Miami and I have spend with him best time ever,
> he is really great developer - if he is saying that he will have release
> process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not
> in a week - start today!
>
>     Please start whole work on that and make it happen. I will be the
> first who try the process and maybe with Chris's help we will solve also
> issue with uploading artifacts to staging area which we had.
>
>     Good Luck,
>     Piotr
>
>     czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> contact@cristallium.com>> napisał(a):
>
>     Hi Guys,
>
>     I'm a lover of Flex dev guy since more than 10 years, been members of
> Flex group on Montpellier (France) at golden age of Flex and go at all
> conferences when Michaël Chaize came to Montpellier (and using Flex every
> day).
>
>     First of all I want to thank every one of you for your hard work, and
> congratulate you for the actual Apache Royale capabilities.
>     With the last features (especialy datagrid), today your great work
> make possible to use Apache Royale in business application. Of course,
> there are bugs, but when reported, it's quickly fix, this is great.
>
>     Now, this is a huge opportunity but also risk for all guys like me to
> adop Apache Royale for futur projects or use it instead of using Air when
> it's possible.
>     Personnaly, I first use it on my own Webs applications and perhaps for
> my customers on little applications for the begin. My big enormous worry is
> to use it and be alone in front of a SDK bug.
>     Seeing new release every 1 or 2 months should certainly reassure me.
> For now I see SDK 0.9.7 since a lot of time and this make me affraid and I
> don't understand why there is no 0.9.8.
>
>     I'm speaking as an Apache Royale SDK user : I'm very sad to read these
> debates on the subject of tools to use for making release. I don't care
> about tools nedeed or not to build the release SDK.
>     I would like use Apache Royale to build RAD (Rapid Application Dev)
> Web applications and see more and more SDK features added, and participate
> to project (like today) by reporting bug  by using my time on isolate the
> bug and make tests cases with screenshoots to save your time in fixing it.
>
>     Using Reac, Bootstrap, AngularJS or other similar is a back to 80's.
> How can I explain my customer that I need 3 ou 4 days to make thinks that
> took me 1 day with Flex ?
>     The big competitive advantage of Apache Royale is not only be able to
> re-use Flex apps but is also simplicity and time saving where other SDK
> can't do it. (I think you already know that)
>
>     I am convinced that all guys like me will jump using Royale when they
> will know that there is a bug free SDK with fast evolution available.
> (unfortunaly it's not known enough, nobody know someone working in
> newspapers ?)
>
>     So please, I beg you, don't waste your time on things that are not
> essential and like Carlos said, go forward. From outside view, Apache
> Royale stay sticky to 0.9.7.
>
>     You are so close of a v1.0, I hope see it very soon and other releases
> with bugs fix every 1, 2 or 3 months.
>     Consider my comments as support and not criticism.
>
>     Thanks again for your hard work.
>
>     Long life and success to Apache Royale !
>
>     Fred
>
>
>
>     Le 26.03.2020 09:26, Carlos Rovira a écrit :
>     Hi,
>
>     that's amazingly simple, so I think we should go that way without
> doubt. I
>     think reached this point there's a clear sense of that we need to go
> that
>     route.
>
>     We tried our best to stick with the previous process and we're all
>     loosing lots of time. Then currently seems no more people in the
> community
>     was interested in this thread, event to comment a single line (here or
> in
>     the other users list thread), what means that or there's no more people
>     like us in this project or people really is not interested and just
> want us
>     to release and go forward.
>
>     As previously I think most of the PMCs here (Om, Josh, Greg and me for
>     sure), probably Yishay for his concise comments are more for this.
>     My thinking is that the right now I think only 2 PMCs are for CI
> Server,
>     and other one that is uncertainly but didn't try the CI Server.
>
>     I think all can live together while is not a must for the rest that
> don't
>     want it the others option, so what's about if we release with the
>     super-simple steps Chris proposal, and others wanting to use CI do that
>     when is their RM turn ? (of course maintaining it and making it work
> for
>     his release without requiring nothing for the rest that doesn't want
> it).
>
>     Release as other projects do is recommended but not required, the same
> as
>     the actual CI server (but this one should be less recommended since is
> a
>     royale-only practice not seen in any other place).
>
>     What's the important thing is to release, do it, and do it easily and
> often.
>
>     Thanks
>
>
>
>     El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
>     christofer.dutz@c-ware.de<ma...@c-ware.de>>)
> escribió:
>
>
>     Ok,
>
>     I'll write this a last time as I do feel like we're going in circles
> and
>     will from now on not participate in any discussion involving releasing
> on a
>     CI server.
>
>     A correct Maven release would use (There will be some additional
> profiles
>     to activate to include all modules)
>
>     1) the "mvn release:branch" call in order to create the branch and bump
>     the version of develop to the next version.
>     2) the "mvn release:prepare" to change the pom to the release version,
> set
>     the timestamp in the pom (for reproducible builds) build ... if all
> tests
>     are good, commit the changes, tag this commit, update the poms to the
> next
>     development version, commit those changes and push everything.
>     3) the "mvn release:perform" which will checkout the tagged version
> build
>     everything with the "apache-release" profile turned on (Which causes
> the
>     source.jars, Javadoc.jars, hashes and gpg singatures to be created as
> well
>     as the assembly) This also deploys the built artifacts to Nexus.
>
>     Most of that you are already doing on the CI server however you're not
>     letting it do all automatically (For lack of credentials)
>
>     But ... if you would just be doing those steps on the RM machine.
>
>     Chris
>
>
>
>
>
>     Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
> <ma...@adobe.com.INVALID>>:
>
>
>
>         On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org
> <ma...@apache.org>> wrote:
>
>             > What I want to know is what the Maven commands should be to
>     create a
>             > release in this "conventional process" you are referring to.
>             >
>
>             If you want to know what's the conventional maven process is, I
>     think I can
>             ask Chris if he wants to work with me on that process, since he
>     already did
>             many other Apache projects, we can expect the process is what
> is
>     needed for
>             us to. But just expect that will be a series of standard maven
>     commands
>             (prepare, release,...), so nothing strange at all (I expect).
>
>             Do you want us to do that?
>
>         Yes.  I want to know what the series of standard Maven commands
> are.
>     Then we can figure out how to convert them to run on the CI server.
>
>         -Alex
>
>             Thanks
>
>
>             >
>             > Maybe someone else can explain better than me.
>             >
>             > -Alex
>             >
>             > On 3/25/20, 2:22 PM, "Carlos Rovira" <
> carlosrovira@apache.org<ma...@apache.org>>
>     wrote:
>             >
>             >     Hi Alex,
>             >
>             >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>             > (<aharui@adobe.com.invalid<mailto:aharui@adobe.com.invalid
> >>)
>             >     escribió:
>             >
>             >     > Carlos,
>             >     >
>             >     > I'm pretty sure that part of the "conventional process"
>     you want to
>             > try
>             >     > requires filling the staging repo from a local machine.
>             >     >
>             >
>             >     This is what we already did. If you go to [1] will see
> [2].
>     That was
>             > the
>             >     upload of compiler to the staging repo. When trying to do
>     the same for
>             >     typedefs it failed when trying to fill repo from local
>     machine. I think
>             >     Chris or I should not take more time in trying to fix Ant
>     scripts that
>             > are
>             >     failing.
>             >
>             >     Thanks
>             >
>             >     [1]
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=SzmPqflLUwAxBCIkm%2BFn2BO8OZVJH1Gp66CVl349I3g%3D&amp;reserved=0
>             >     [2]
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=VONdkWMhQpEGhSlVoXwFuhdnApXmrSaTnSP%2FDeH6stc%3D&amp;reserved=0
>             >
>             >
>             >
>             >
>             >     >
>             >     > --
>             >     > Carlos Rovira
>             >     >
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=jPUGE0ohIi%2BFYoKZefaob1pSsIjC4AEEjE04N27FiI0%3D&amp;reserved=0
>             >     >
>             >     >
>             >     >
>             >     >
>             >
>             >
>             >
>
>             --
>             Carlos Rovira
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=bkaODFbcmtjdxlibVdfQRKtIzcXImHIQ4HpKQOTgLM8%3D&amp;reserved=0
>
>
>
>
>
>
>     --
>
>     Frédéric Gilli
>
>     mob.0668542622
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
>
>     [cid:171168797bb6addd0331]<
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
> >
>
>
>
>
>     --
>
>     Piotr Zarzycki
>
>     Patreon:
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=j%2BLcn3n8gF9Ro8d0S5EgcHamMg42sVnJXBymeIeQEUk%3D&amp;reserved=0
>
>
>
>

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


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi Yishay,

I think we were all in agreement so I'll make the release. Right now we're
voting the compiler-build-tools 1.2.0 release
As soon as this is approved, I'll continue withe 0.9.7 release.

compiler build tools 1.2.0 is done to release some small changes for
reproducible builds and check the optional path about to release compiler
build tools or jburg versions in the future (that should be very rare).

Thanks


El dom., 29 mar. 2020 a las 15:59, Yishay Weiss (<yi...@hotmail.com>)
escribió:

> Ok, I’m ready. What’s next? Do I need to cancel an RC? How do I login to
> Jenkins? Where do I start?
>
> From: Alex Harui<ma...@adobe.com>
> Sent: Thursday, March 26, 2020 8:50 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>; Yishay
> Weiss<ma...@hotmail.com>
> Subject: Re: Releasing: Finally giving up
>
> @Yishay Weiss
>
> Let's wait until the set of Maven steps are available from Chris and
> Carlos.  Then I will try to find some cycles to help you.  Because of where
> I live, where the schools are closed, and my kids schedule, I have good
> weeks and bad weeks for having time for work, so it will be best to wait to
> try a release until we have the steps and it is one of my good weeks (next
> good week starts this Friday at 5pm my time).
>
> Thanks,
> -Alex
>
> On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
>     Hi All,
>
>     I too, feel very uncomfortable participating in these threads. While
> grateful to Carlos and Chris for their work I’m very annoyed with the tone
> of ultimatums and doom and gloom. Alex has put in a lot of work into this
> and I trust his concerns are technical, rather than protecting his ego as
> has been suggested. We need to get this discussion back on technical tracks.
>
>     Since Chris has given up, and it looks like Carlos has as well, I
> volunteer to start the release process from scratch next Sunday, which is
> after Israel has switched to day light saving. I will try to do the process
> incrementally and in parallel to my other tasks. If by the end of the week
> it turns out the process is too cumbersome and cannot realistically be made
> to work smoothly I will be in favor of changing the requirements to enable
> Chris’s mvn setup to be the main release tool.
>
>     Thanks,
>     Yishay
>
>     From: Piotr Zarzycki<ma...@gmail.com>
>     Sent: Thursday, March 26, 2020 1:27 PM
>     To: Apache Royale Development<ma...@royale.apache.org>
>     Subject: Re: Releasing: Finally giving up
>
>     Hi All,
>
>     I'm member of Apache Foundation for quite some time now. I think I
> have wrote maybe 2-3 emails during that time on members mailing list. -
> Why? - well I'm a person which doesn't like never ending stories, stories
> which are not end up with consensus nor action and I'm sorry but this is
> how it looks like in most cases there. Here we are in Apache Royale project
> where this thread ended up exactly the same - never ending story. - As PMC
> of this project I would like to say enough! :)
>
>     I had hope that when Carlos and Chris try CI steps and in the process
> they may have some issues, but they will end up in the same place as I
> ended up where I was able to prepare RC1 in about 2h without the problem.
> It turns out that they end up in the place where I have started, in the
> place where I have spend 5-6 days of work to finally reach stable point.
> They ended up frustrated in the same way as I was!
>
>     I really don't care now what kind of issue they have now, whether it's
> fixable or not - I just have enough of those never ending discussions where
> there is absolutely no results.
>
>     I met Chris in US in Miami and I have spend with him best time ever,
> he is really great developer - if he is saying that he will have release
> process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not
> in a week - start today!
>
>     Please start whole work on that and make it happen. I will be the
> first who try the process and maybe with Chris's help we will solve also
> issue with uploading artifacts to staging area which we had.
>
>     Good Luck,
>     Piotr
>
>     czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> contact@cristallium.com>> napisał(a):
>
>     Hi Guys,
>
>     I'm a lover of Flex dev guy since more than 10 years, been members of
> Flex group on Montpellier (France) at golden age of Flex and go at all
> conferences when Michaël Chaize came to Montpellier (and using Flex every
> day).
>
>     First of all I want to thank every one of you for your hard work, and
> congratulate you for the actual Apache Royale capabilities.
>     With the last features (especialy datagrid), today your great work
> make possible to use Apache Royale in business application. Of course,
> there are bugs, but when reported, it's quickly fix, this is great.
>
>     Now, this is a huge opportunity but also risk for all guys like me to
> adop Apache Royale for futur projects or use it instead of using Air when
> it's possible.
>     Personnaly, I first use it on my own Webs applications and perhaps for
> my customers on little applications for the begin. My big enormous worry is
> to use it and be alone in front of a SDK bug.
>     Seeing new release every 1 or 2 months should certainly reassure me.
> For now I see SDK 0.9.7 since a lot of time and this make me affraid and I
> don't understand why there is no 0.9.8.
>
>     I'm speaking as an Apache Royale SDK user : I'm very sad to read these
> debates on the subject of tools to use for making release. I don't care
> about tools nedeed or not to build the release SDK.
>     I would like use Apache Royale to build RAD (Rapid Application Dev)
> Web applications and see more and more SDK features added, and participate
> to project (like today) by reporting bug  by using my time on isolate the
> bug and make tests cases with screenshoots to save your time in fixing it.
>
>     Using Reac, Bootstrap, AngularJS or other similar is a back to 80's.
> How can I explain my customer that I need 3 ou 4 days to make thinks that
> took me 1 day with Flex ?
>     The big competitive advantage of Apache Royale is not only be able to
> re-use Flex apps but is also simplicity and time saving where other SDK
> can't do it. (I think you already know that)
>
>     I am convinced that all guys like me will jump using Royale when they
> will know that there is a bug free SDK with fast evolution available.
> (unfortunaly it's not known enough, nobody know someone working in
> newspapers ?)
>
>     So please, I beg you, don't waste your time on things that are not
> essential and like Carlos said, go forward. From outside view, Apache
> Royale stay sticky to 0.9.7.
>
>     You are so close of a v1.0, I hope see it very soon and other releases
> with bugs fix every 1, 2 or 3 months.
>     Consider my comments as support and not criticism.
>
>     Thanks again for your hard work.
>
>     Long life and success to Apache Royale !
>
>     Fred
>
>
>
>     Le 26.03.2020 09:26, Carlos Rovira a écrit :
>     Hi,
>
>     that's amazingly simple, so I think we should go that way without
> doubt. I
>     think reached this point there's a clear sense of that we need to go
> that
>     route.
>
>     We tried our best to stick with the previous process and we're all
>     loosing lots of time. Then currently seems no more people in the
> community
>     was interested in this thread, event to comment a single line (here or
> in
>     the other users list thread), what means that or there's no more people
>     like us in this project or people really is not interested and just
> want us
>     to release and go forward.
>
>     As previously I think most of the PMCs here (Om, Josh, Greg and me for
>     sure), probably Yishay for his concise comments are more for this.
>     My thinking is that the right now I think only 2 PMCs are for CI
> Server,
>     and other one that is uncertainly but didn't try the CI Server.
>
>     I think all can live together while is not a must for the rest that
> don't
>     want it the others option, so what's about if we release with the
>     super-simple steps Chris proposal, and others wanting to use CI do that
>     when is their RM turn ? (of course maintaining it and making it work
> for
>     his release without requiring nothing for the rest that doesn't want
> it).
>
>     Release as other projects do is recommended but not required, the same
> as
>     the actual CI server (but this one should be less recommended since is
> a
>     royale-only practice not seen in any other place).
>
>     What's the important thing is to release, do it, and do it easily and
> often.
>
>     Thanks
>
>
>
>     El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
>     christofer.dutz@c-ware.de<ma...@c-ware.de>>)
> escribió:
>
>
>     Ok,
>
>     I'll write this a last time as I do feel like we're going in circles
> and
>     will from now on not participate in any discussion involving releasing
> on a
>     CI server.
>
>     A correct Maven release would use (There will be some additional
> profiles
>     to activate to include all modules)
>
>     1) the "mvn release:branch" call in order to create the branch and bump
>     the version of develop to the next version.
>     2) the "mvn release:prepare" to change the pom to the release version,
> set
>     the timestamp in the pom (for reproducible builds) build ... if all
> tests
>     are good, commit the changes, tag this commit, update the poms to the
> next
>     development version, commit those changes and push everything.
>     3) the "mvn release:perform" which will checkout the tagged version
> build
>     everything with the "apache-release" profile turned on (Which causes
> the
>     source.jars, Javadoc.jars, hashes and gpg singatures to be created as
> well
>     as the assembly) This also deploys the built artifacts to Nexus.
>
>     Most of that you are already doing on the CI server however you're not
>     letting it do all automatically (For lack of credentials)
>
>     But ... if you would just be doing those steps on the RM machine.
>
>     Chris
>
>
>
>
>
>     Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID
> <ma...@adobe.com.INVALID>>:
>
>
>
>         On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org
> <ma...@apache.org>> wrote:
>
>             > What I want to know is what the Maven commands should be to
>     create a
>             > release in this "conventional process" you are referring to.
>             >
>
>             If you want to know what's the conventional maven process is, I
>     think I can
>             ask Chris if he wants to work with me on that process, since he
>     already did
>             many other Apache projects, we can expect the process is what
> is
>     needed for
>             us to. But just expect that will be a series of standard maven
>     commands
>             (prepare, release,...), so nothing strange at all (I expect).
>
>             Do you want us to do that?
>
>         Yes.  I want to know what the series of standard Maven commands
> are.
>     Then we can figure out how to convert them to run on the CI server.
>
>         -Alex
>
>             Thanks
>
>
>             >
>             > Maybe someone else can explain better than me.
>             >
>             > -Alex
>             >
>             > On 3/25/20, 2:22 PM, "Carlos Rovira" <
> carlosrovira@apache.org<ma...@apache.org>>
>     wrote:
>             >
>             >     Hi Alex,
>             >
>             >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>             > (<aharui@adobe.com.invalid<mailto:aharui@adobe.com.invalid
> >>)
>             >     escribió:
>             >
>             >     > Carlos,
>             >     >
>             >     > I'm pretty sure that part of the "conventional process"
>     you want to
>             > try
>             >     > requires filling the staging repo from a local machine.
>             >     >
>             >
>             >     This is what we already did. If you go to [1] will see
> [2].
>     That was
>             > the
>             >     upload of compiler to the staging repo. When trying to do
>     the same for
>             >     typedefs it failed when trying to fill repo from local
>     machine. I think
>             >     Chris or I should not take more time in trying to fix Ant
>     scripts that
>             > are
>             >     failing.
>             >
>             >     Thanks
>             >
>             >     [1]
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=SzmPqflLUwAxBCIkm%2BFn2BO8OZVJH1Gp66CVl349I3g%3D&amp;reserved=0
>             >     [2]
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=VONdkWMhQpEGhSlVoXwFuhdnApXmrSaTnSP%2FDeH6stc%3D&amp;reserved=0
>             >
>             >
>             >
>             >
>             >     >
>             >     > --
>             >     > Carlos Rovira
>             >     >
>             >
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=jPUGE0ohIi%2BFYoKZefaob1pSsIjC4AEEjE04N27FiI0%3D&amp;reserved=0
>             >     >
>             >     >
>             >     >
>             >     >
>             >
>             >
>             >
>
>             --
>             Carlos Rovira
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=bkaODFbcmtjdxlibVdfQRKtIzcXImHIQ4HpKQOTgLM8%3D&amp;reserved=0
>
>
>
>
>
>
>     --
>
>     Frédéric Gilli
>
>     mob.0668542622
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
>
>     [cid:171168797bb6addd0331]<
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
> >
>
>
>
>
>     --
>
>     Piotr Zarzycki
>
>     Patreon:
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=j%2BLcn3n8gF9Ro8d0S5EgcHamMg42sVnJXBymeIeQEUk%3D&amp;reserved=0
>
>
>
>

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

RE: Releasing: Finally giving up

Posted by Yishay Weiss <yi...@hotmail.com>.
Ok, I’m ready. What’s next? Do I need to cancel an RC? How do I login to Jenkins? Where do I start?

From: Alex Harui<ma...@adobe.com>
Sent: Thursday, March 26, 2020 8:50 PM
To: dev@royale.apache.org<ma...@royale.apache.org>; Yishay Weiss<ma...@hotmail.com>
Subject: Re: Releasing: Finally giving up

@Yishay Weiss

Let's wait until the set of Maven steps are available from Chris and Carlos.  Then I will try to find some cycles to help you.  Because of where I live, where the schools are closed, and my kids schedule, I have good weeks and bad weeks for having time for work, so it will be best to wait to try a release until we have the steps and it is one of my good weeks (next good week starts this Friday at 5pm my time).

Thanks,
-Alex

On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:

    Hi All,

    I too, feel very uncomfortable participating in these threads. While grateful to Carlos and Chris for their work I’m very annoyed with the tone of ultimatums and doom and gloom. Alex has put in a lot of work into this and I trust his concerns are technical, rather than protecting his ego as has been suggested. We need to get this discussion back on technical tracks.

    Since Chris has given up, and it looks like Carlos has as well, I volunteer to start the release process from scratch next Sunday, which is after Israel has switched to day light saving. I will try to do the process incrementally and in parallel to my other tasks. If by the end of the week it turns out the process is too cumbersome and cannot realistically be made to work smoothly I will be in favor of changing the requirements to enable Chris’s mvn setup to be the main release tool.

    Thanks,
    Yishay

    From: Piotr Zarzycki<ma...@gmail.com>
    Sent: Thursday, March 26, 2020 1:27 PM
    To: Apache Royale Development<ma...@royale.apache.org>
    Subject: Re: Releasing: Finally giving up

    Hi All,

    I'm member of Apache Foundation for quite some time now. I think I have wrote maybe 2-3 emails during that time on members mailing list. - Why? - well I'm a person which doesn't like never ending stories, stories which are not end up with consensus nor action and I'm sorry but this is how it looks like in most cases there. Here we are in Apache Royale project where this thread ended up exactly the same - never ending story. - As PMC of this project I would like to say enough! :)

    I had hope that when Carlos and Chris try CI steps and in the process they may have some issues, but they will end up in the same place as I ended up where I was able to prepare RC1 in about 2h without the problem. It turns out that they end up in the place where I have started, in the place where I have spend 5-6 days of work to finally reach stable point. They ended up frustrated in the same way as I was!

    I really don't care now what kind of issue they have now, whether it's fixable or not - I just have enough of those never ending discussions where there is absolutely no results.

    I met Chris in US in Miami and I have spend with him best time ever, he is really great developer - if he is saying that he will have release process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not in a week - start today!

    Please start whole work on that and make it happen. I will be the first who try the process and maybe with Chris's help we will solve also issue with uploading artifacts to staging area which we had.

    Good Luck,
    Piotr

    czw., 26 mar 2020 o 12:02 <co...@cristallium.com>> napisał(a):

    Hi Guys,

    I'm a lover of Flex dev guy since more than 10 years, been members of Flex group on Montpellier (France) at golden age of Flex and go at all conferences when Michaël Chaize came to Montpellier (and using Flex every day).

    First of all I want to thank every one of you for your hard work, and congratulate you for the actual Apache Royale capabilities.
    With the last features (especialy datagrid), today your great work make possible to use Apache Royale in business application. Of course, there are bugs, but when reported, it's quickly fix, this is great.

    Now, this is a huge opportunity but also risk for all guys like me to adop Apache Royale for futur projects or use it instead of using Air when it's possible.
    Personnaly, I first use it on my own Webs applications and perhaps for my customers on little applications for the begin. My big enormous worry is to use it and be alone in front of a SDK bug.
    Seeing new release every 1 or 2 months should certainly reassure me. For now I see SDK 0.9.7 since a lot of time and this make me affraid and I don't understand why there is no 0.9.8.

    I'm speaking as an Apache Royale SDK user : I'm very sad to read these debates on the subject of tools to use for making release. I don't care about tools nedeed or not to build the release SDK.
    I would like use Apache Royale to build RAD (Rapid Application Dev) Web applications and see more and more SDK features added, and participate to project (like today) by reporting bug  by using my time on isolate the bug and make tests cases with screenshoots to save your time in fixing it.

    Using Reac, Bootstrap, AngularJS or other similar is a back to 80's. How can I explain my customer that I need 3 ou 4 days to make thinks that took me 1 day with Flex ?
    The big competitive advantage of Apache Royale is not only be able to re-use Flex apps but is also simplicity and time saving where other SDK can't do it. (I think you already know that)

    I am convinced that all guys like me will jump using Royale when they will know that there is a bug free SDK with fast evolution available. (unfortunaly it's not known enough, nobody know someone working in newspapers ?)

    So please, I beg you, don't waste your time on things that are not essential and like Carlos said, go forward. From outside view, Apache Royale stay sticky to 0.9.7.

    You are so close of a v1.0, I hope see it very soon and other releases with bugs fix every 1, 2 or 3 months.
    Consider my comments as support and not criticism.

    Thanks again for your hard work.

    Long life and success to Apache Royale !

    Fred



    Le 26.03.2020 09:26, Carlos Rovira a écrit :
    Hi,

    that's amazingly simple, so I think we should go that way without doubt. I
    think reached this point there's a clear sense of that we need to go that
    route.

    We tried our best to stick with the previous process and we're all
    loosing lots of time. Then currently seems no more people in the community
    was interested in this thread, event to comment a single line (here or in
    the other users list thread), what means that or there's no more people
    like us in this project or people really is not interested and just want us
    to release and go forward.

    As previously I think most of the PMCs here (Om, Josh, Greg and me for
    sure), probably Yishay for his concise comments are more for this.
    My thinking is that the right now I think only 2 PMCs are for CI Server,
    and other one that is uncertainly but didn't try the CI Server.

    I think all can live together while is not a must for the rest that don't
    want it the others option, so what's about if we release with the
    super-simple steps Chris proposal, and others wanting to use CI do that
    when is their RM turn ? (of course maintaining it and making it work for
    his release without requiring nothing for the rest that doesn't want it).

    Release as other projects do is recommended but not required, the same as
    the actual CI server (but this one should be less recommended since is a
    royale-only practice not seen in any other place).

    What's the important thing is to release, do it, and do it easily and often.

    Thanks



    El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
    christofer.dutz@c-ware.de<ma...@c-ware.de>>) escribió:


    Ok,

    I'll write this a last time as I do feel like we're going in circles and
    will from now on not participate in any discussion involving releasing on a
    CI server.

    A correct Maven release would use (There will be some additional profiles
    to activate to include all modules)

    1) the "mvn release:branch" call in order to create the branch and bump
    the version of develop to the next version.
    2) the "mvn release:prepare" to change the pom to the release version, set
    the timestamp in the pom (for reproducible builds) build ... if all tests
    are good, commit the changes, tag this commit, update the poms to the next
    development version, commit those changes and push everything.
    3) the "mvn release:perform" which will checkout the tagged version build
    everything with the "apache-release" profile turned on (Which causes the
    source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
    as the assembly) This also deploys the built artifacts to Nexus.

    Most of that you are already doing on the CI server however you're not
    letting it do all automatically (For lack of credentials)

    But ... if you would just be doing those steps on the RM machine.

    Chris





    Am 26.03.20, 05:54 schrieb "Alex Harui" <ah...@adobe.com.INVALID>>:



        On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org>> wrote:

            > What I want to know is what the Maven commands should be to
    create a
            > release in this "conventional process" you are referring to.
            >

            If you want to know what's the conventional maven process is, I
    think I can
            ask Chris if he wants to work with me on that process, since he
    already did
            many other Apache projects, we can expect the process is what is
    needed for
            us to. But just expect that will be a series of standard maven
    commands
            (prepare, release,...), so nothing strange at all (I expect).

            Do you want us to do that?

        Yes.  I want to know what the series of standard Maven commands are.
    Then we can figure out how to convert them to run on the CI server.

        -Alex

            Thanks


            >
            > Maybe someone else can explain better than me.
            >
            > -Alex
            >
            > On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org>>
    wrote:
            >
            >     Hi Alex,
            >
            >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
            > (<ah...@adobe.com.invalid>>)
            >     escribió:
            >
            >     > Carlos,
            >     >
            >     > I'm pretty sure that part of the "conventional process"
    you want to
            > try
            >     > requires filling the staging repo from a local machine.
            >     >
            >
            >     This is what we already did. If you go to [1] will see [2].
    That was
            > the
            >     upload of compiler to the staging repo. When trying to do
    the same for
            >     typedefs it failed when trying to fill repo from local
    machine. I think
            >     Chris or I should not take more time in trying to fix Ant
    scripts that
            > are
            >     failing.
            >
            >     Thanks
            >
            >     [1]
            >
    https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=SzmPqflLUwAxBCIkm%2BFn2BO8OZVJH1Gp66CVl349I3g%3D&amp;reserved=0
            >     [2]
            >
    https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=VONdkWMhQpEGhSlVoXwFuhdnApXmrSaTnSP%2FDeH6stc%3D&amp;reserved=0
            >
            >
            >
            >
            >     >
            >     > --
            >     > Carlos Rovira
            >     >
            >
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=jPUGE0ohIi%2BFYoKZefaob1pSsIjC4AEEjE04N27FiI0%3D&amp;reserved=0
            >     >
            >     >
            >     >
            >     >
            >
            >
            >

            --
            Carlos Rovira

    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=bkaODFbcmtjdxlibVdfQRKtIzcXImHIQ4HpKQOTgLM8%3D&amp;reserved=0






    --

    Frédéric Gilli

    mob.0668542622

    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0

    [cid:171168797bb6addd0331]<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0>




    --

    Piotr Zarzycki

    Patreon: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=j%2BLcn3n8gF9Ro8d0S5EgcHamMg42sVnJXBymeIeQEUk%3D&amp;reserved=0




Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.
@Yishay Weiss

Let's wait until the set of Maven steps are available from Chris and Carlos.  Then I will try to find some cycles to help you.  Because of where I live, where the schools are closed, and my kids schedule, I have good weeks and bad weeks for having time for work, so it will be best to wait to try a release until we have the steps and it is one of my good weeks (next good week starts this Friday at 5pm my time).

Thanks,
-Alex

On 3/26/20, 5:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:

    Hi All,
    
    I too, feel very uncomfortable participating in these threads. While grateful to Carlos and Chris for their work I’m very annoyed with the tone of ultimatums and doom and gloom. Alex has put in a lot of work into this and I trust his concerns are technical, rather than protecting his ego as has been suggested. We need to get this discussion back on technical tracks.
    
    Since Chris has given up, and it looks like Carlos has as well, I volunteer to start the release process from scratch next Sunday, which is after Israel has switched to day light saving. I will try to do the process incrementally and in parallel to my other tasks. If by the end of the week it turns out the process is too cumbersome and cannot realistically be made to work smoothly I will be in favor of changing the requirements to enable Chris’s mvn setup to be the main release tool.
    
    Thanks,
    Yishay
    
    From: Piotr Zarzycki<ma...@gmail.com>
    Sent: Thursday, March 26, 2020 1:27 PM
    To: Apache Royale Development<ma...@royale.apache.org>
    Subject: Re: Releasing: Finally giving up
    
    Hi All,
    
    I'm member of Apache Foundation for quite some time now. I think I have wrote maybe 2-3 emails during that time on members mailing list. - Why? - well I'm a person which doesn't like never ending stories, stories which are not end up with consensus nor action and I'm sorry but this is how it looks like in most cases there. Here we are in Apache Royale project where this thread ended up exactly the same - never ending story. - As PMC of this project I would like to say enough! :)
    
    I had hope that when Carlos and Chris try CI steps and in the process they may have some issues, but they will end up in the same place as I ended up where I was able to prepare RC1 in about 2h without the problem. It turns out that they end up in the place where I have started, in the place where I have spend 5-6 days of work to finally reach stable point. They ended up frustrated in the same way as I was!
    
    I really don't care now what kind of issue they have now, whether it's fixable or not - I just have enough of those never ending discussions where there is absolutely no results.
    
    I met Chris in US in Miami and I have spend with him best time ever, he is really great developer - if he is saying that he will have release process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not in a week - start today!
    
    Please start whole work on that and make it happen. I will be the first who try the process and maybe with Chris's help we will solve also issue with uploading artifacts to staging area which we had.
    
    Good Luck,
    Piotr
    
    czw., 26 mar 2020 o 12:02 <co...@cristallium.com>> napisał(a):
    
    Hi Guys,
    
    I'm a lover of Flex dev guy since more than 10 years, been members of Flex group on Montpellier (France) at golden age of Flex and go at all conferences when Michaël Chaize came to Montpellier (and using Flex every day).
    
    First of all I want to thank every one of you for your hard work, and congratulate you for the actual Apache Royale capabilities.
    With the last features (especialy datagrid), today your great work make possible to use Apache Royale in business application. Of course, there are bugs, but when reported, it's quickly fix, this is great.
    
    Now, this is a huge opportunity but also risk for all guys like me to adop Apache Royale for futur projects or use it instead of using Air when it's possible.
    Personnaly, I first use it on my own Webs applications and perhaps for my customers on little applications for the begin. My big enormous worry is to use it and be alone in front of a SDK bug.
    Seeing new release every 1 or 2 months should certainly reassure me. For now I see SDK 0.9.7 since a lot of time and this make me affraid and I don't understand why there is no 0.9.8.
    
    I'm speaking as an Apache Royale SDK user : I'm very sad to read these debates on the subject of tools to use for making release. I don't care about tools nedeed or not to build the release SDK.
    I would like use Apache Royale to build RAD (Rapid Application Dev) Web applications and see more and more SDK features added, and participate to project (like today) by reporting bug  by using my time on isolate the bug and make tests cases with screenshoots to save your time in fixing it.
    
    Using Reac, Bootstrap, AngularJS or other similar is a back to 80's. How can I explain my customer that I need 3 ou 4 days to make thinks that took me 1 day with Flex ?
    The big competitive advantage of Apache Royale is not only be able to re-use Flex apps but is also simplicity and time saving where other SDK can't do it. (I think you already know that)
    
    I am convinced that all guys like me will jump using Royale when they will know that there is a bug free SDK with fast evolution available. (unfortunaly it's not known enough, nobody know someone working in newspapers ?)
    
    So please, I beg you, don't waste your time on things that are not essential and like Carlos said, go forward. From outside view, Apache Royale stay sticky to 0.9.7.
    
    You are so close of a v1.0, I hope see it very soon and other releases with bugs fix every 1, 2 or 3 months.
    Consider my comments as support and not criticism.
    
    Thanks again for your hard work.
    
    Long life and success to Apache Royale !
    
    Fred
    
    
    
    Le 26.03.2020 09:26, Carlos Rovira a écrit :
    Hi,
    
    that's amazingly simple, so I think we should go that way without doubt. I
    think reached this point there's a clear sense of that we need to go that
    route.
    
    We tried our best to stick with the previous process and we're all
    loosing lots of time. Then currently seems no more people in the community
    was interested in this thread, event to comment a single line (here or in
    the other users list thread), what means that or there's no more people
    like us in this project or people really is not interested and just want us
    to release and go forward.
    
    As previously I think most of the PMCs here (Om, Josh, Greg and me for
    sure), probably Yishay for his concise comments are more for this.
    My thinking is that the right now I think only 2 PMCs are for CI Server,
    and other one that is uncertainly but didn't try the CI Server.
    
    I think all can live together while is not a must for the rest that don't
    want it the others option, so what's about if we release with the
    super-simple steps Chris proposal, and others wanting to use CI do that
    when is their RM turn ? (of course maintaining it and making it work for
    his release without requiring nothing for the rest that doesn't want it).
    
    Release as other projects do is recommended but not required, the same as
    the actual CI server (but this one should be less recommended since is a
    royale-only practice not seen in any other place).
    
    What's the important thing is to release, do it, and do it easily and often.
    
    Thanks
    
    
    
    El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
    christofer.dutz@c-ware.de<ma...@c-ware.de>>) escribió:
    
    
    Ok,
    
    I'll write this a last time as I do feel like we're going in circles and
    will from now on not participate in any discussion involving releasing on a
    CI server.
    
    A correct Maven release would use (There will be some additional profiles
    to activate to include all modules)
    
    1) the "mvn release:branch" call in order to create the branch and bump
    the version of develop to the next version.
    2) the "mvn release:prepare" to change the pom to the release version, set
    the timestamp in the pom (for reproducible builds) build ... if all tests
    are good, commit the changes, tag this commit, update the poms to the next
    development version, commit those changes and push everything.
    3) the "mvn release:perform" which will checkout the tagged version build
    everything with the "apache-release" profile turned on (Which causes the
    source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
    as the assembly) This also deploys the built artifacts to Nexus.
    
    Most of that you are already doing on the CI server however you're not
    letting it do all automatically (For lack of credentials)
    
    But ... if you would just be doing those steps on the RM machine.
    
    Chris
    
    
    
    
    
    Am 26.03.20, 05:54 schrieb "Alex Harui" <ah...@adobe.com.INVALID>>:
    
    
    
        On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org>> wrote:
    
            > What I want to know is what the Maven commands should be to
    create a
            > release in this "conventional process" you are referring to.
            >
    
            If you want to know what's the conventional maven process is, I
    think I can
            ask Chris if he wants to work with me on that process, since he
    already did
            many other Apache projects, we can expect the process is what is
    needed for
            us to. But just expect that will be a series of standard maven
    commands
            (prepare, release,...), so nothing strange at all (I expect).
    
            Do you want us to do that?
    
        Yes.  I want to know what the series of standard Maven commands are.
    Then we can figure out how to convert them to run on the CI server.
    
        -Alex
    
            Thanks
    
    
            >
            > Maybe someone else can explain better than me.
            >
            > -Alex
            >
            > On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org>>
    wrote:
            >
            >     Hi Alex,
            >
            >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
            > (<ah...@adobe.com.invalid>>)
            >     escribió:
            >
            >     > Carlos,
            >     >
            >     > I'm pretty sure that part of the "conventional process"
    you want to
            > try
            >     > requires filling the staging repo from a local machine.
            >     >
            >
            >     This is what we already did. If you go to [1] will see [2].
    That was
            > the
            >     upload of compiler to the staging repo. When trying to do
    the same for
            >     typedefs it failed when trying to fill repo from local
    machine. I think
            >     Chris or I should not take more time in trying to fix Ant
    scripts that
            > are
            >     failing.
            >
            >     Thanks
            >
            >     [1]
            >
    https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=SzmPqflLUwAxBCIkm%2BFn2BO8OZVJH1Gp66CVl349I3g%3D&amp;reserved=0
            >     [2]
            >
    https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=VONdkWMhQpEGhSlVoXwFuhdnApXmrSaTnSP%2FDeH6stc%3D&amp;reserved=0
            >
            >
            >
            >
            >     >
            >     > --
            >     > Carlos Rovira
            >     >
            >
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931371038&amp;sdata=jPUGE0ohIi%2BFYoKZefaob1pSsIjC4AEEjE04N27FiI0%3D&amp;reserved=0
            >     >
            >     >
            >     >
            >     >
            >
            >
            >
    
            --
            Carlos Rovira
    
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=bkaODFbcmtjdxlibVdfQRKtIzcXImHIQ4HpKQOTgLM8%3D&amp;reserved=0
    
    
    
    
    
    
    --
    
    Frédéric Gilli
    
    mob.0668542622
    
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0
    
    [cid:171168797bb6addd0331]<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cristallium.com&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=F0YC6%2BzeeQf2GjI0JMStw2pKYsezejwjTRdaUU%2FEYu0%3D&amp;reserved=0>
    
    
    
    
    --
    
    Piotr Zarzycki
    
    Patreon: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C2be5b8cd20c049e2a23608d7d17f0daf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208215931381031&amp;sdata=j%2BLcn3n8gF9Ro8d0S5EgcHamMg42sVnJXBymeIeQEUk%3D&amp;reserved=0
    
    


Re: Releasing: Finally giving up

Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Yishay,

I would say - great some time ago, but now - We will have again bunch of
emails with same questions on the list which were asked and debated here,
again and again. It end up in the same place with loosed energy. However I
hope guys won't wait but start working in parallel on new stuff - I'm sorry
but I don't believe in a an old process anymore - not after what I'm
reading here.

Thanks,
Piotr

czw., 26 mar 2020 o 13:13 Yishay Weiss <yi...@hotmail.com> napisał(a):

> Hi All,
>
> I too, feel very uncomfortable participating in these threads. While
> grateful to Carlos and Chris for their work I’m very annoyed with the tone
> of ultimatums and doom and gloom. Alex has put in a lot of work into this
> and I trust his concerns are technical, rather than protecting his ego as
> has been suggested. We need to get this discussion back on technical tracks.
>
> Since Chris has given up, and it looks like Carlos has as well, I
> volunteer to start the release process from scratch next Sunday, which is
> after Israel has switched to day light saving. I will try to do the process
> incrementally and in parallel to my other tasks. If by the end of the week
> it turns out the process is too cumbersome and cannot realistically be made
> to work smoothly I will be in favor of changing the requirements to enable
> Chris’s mvn setup to be the main release tool.
>
> Thanks,
> Yishay
>
> From: Piotr Zarzycki<ma...@gmail.com>
> Sent: Thursday, March 26, 2020 1:27 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Releasing: Finally giving up
>
> Hi All,
>
> I'm member of Apache Foundation for quite some time now. I think I have
> wrote maybe 2-3 emails during that time on members mailing list. - Why? -
> well I'm a person which doesn't like never ending stories, stories which
> are not end up with consensus nor action and I'm sorry but this is how it
> looks like in most cases there. Here we are in Apache Royale project where
> this thread ended up exactly the same - never ending story. - As PMC of
> this project I would like to say enough! :)
>
> I had hope that when Carlos and Chris try CI steps and in the process they
> may have some issues, but they will end up in the same place as I ended up
> where I was able to prepare RC1 in about 2h without the problem. It turns
> out that they end up in the place where I have started, in the place where
> I have spend 5-6 days of work to finally reach stable point. They ended up
> frustrated in the same way as I was!
>
> I really don't care now what kind of issue they have now, whether it's
> fixable or not - I just have enough of those never ending discussions where
> there is absolutely no results.
>
> I met Chris in US in Miami and I have spend with him best time ever, he is
> really great developer - if he is saying that he will have release process
> in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not in a week
> - start today!
>
> Please start whole work on that and make it happen. I will be the first
> who try the process and maybe with Chris's help we will solve also issue
> with uploading artifacts to staging area which we had.
>
> Good Luck,
> Piotr
>
> czw., 26 mar 2020 o 12:02 <contact@cristallium.com<mailto:
> contact@cristallium.com>> napisał(a):
>
> Hi Guys,
>
> I'm a lover of Flex dev guy since more than 10 years, been members of Flex
> group on Montpellier (France) at golden age of Flex and go at all
> conferences when Michaël Chaize came to Montpellier (and using Flex every
> day).
>
> First of all I want to thank every one of you for your hard work, and
> congratulate you for the actual Apache Royale capabilities.
> With the last features (especialy datagrid), today your great work make
> possible to use Apache Royale in business application. Of course, there are
> bugs, but when reported, it's quickly fix, this is great.
>
> Now, this is a huge opportunity but also risk for all guys like me to adop
> Apache Royale for futur projects or use it instead of using Air when it's
> possible.
> Personnaly, I first use it on my own Webs applications and perhaps for my
> customers on little applications for the begin. My big enormous worry is to
> use it and be alone in front of a SDK bug.
> Seeing new release every 1 or 2 months should certainly reassure me. For
> now I see SDK 0.9.7 since a lot of time and this make me affraid and I
> don't understand why there is no 0.9.8.
>
> I'm speaking as an Apache Royale SDK user : I'm very sad to read these
> debates on the subject of tools to use for making release. I don't care
> about tools nedeed or not to build the release SDK.
> I would like use Apache Royale to build RAD (Rapid Application Dev) Web
> applications and see more and more SDK features added, and participate to
> project (like today) by reporting bug  by using my time on isolate the bug
> and make tests cases with screenshoots to save your time in fixing it.
>
> Using Reac, Bootstrap, AngularJS or other similar is a back to 80's. How
> can I explain my customer that I need 3 ou 4 days to make thinks that took
> me 1 day with Flex ?
> The big competitive advantage of Apache Royale is not only be able to
> re-use Flex apps but is also simplicity and time saving where other SDK
> can't do it. (I think you already know that)
>
> I am convinced that all guys like me will jump using Royale when they will
> know that there is a bug free SDK with fast evolution available.
> (unfortunaly it's not known enough, nobody know someone working in
> newspapers ?)
>
> So please, I beg you, don't waste your time on things that are not
> essential and like Carlos said, go forward. From outside view, Apache
> Royale stay sticky to 0.9.7.
>
> You are so close of a v1.0, I hope see it very soon and other releases
> with bugs fix every 1, 2 or 3 months.
> Consider my comments as support and not criticism.
>
> Thanks again for your hard work.
>
> Long life and success to Apache Royale !
>
> Fred
>
>
>
> Le 26.03.2020 09:26, Carlos Rovira a écrit :
> Hi,
>
> that's amazingly simple, so I think we should go that way without doubt. I
> think reached this point there's a clear sense of that we need to go that
> route.
>
> We tried our best to stick with the previous process and we're all
> loosing lots of time. Then currently seems no more people in the community
> was interested in this thread, event to comment a single line (here or in
> the other users list thread), what means that or there's no more people
> like us in this project or people really is not interested and just want us
> to release and go forward.
>
> As previously I think most of the PMCs here (Om, Josh, Greg and me for
> sure), probably Yishay for his concise comments are more for this.
> My thinking is that the right now I think only 2 PMCs are for CI Server,
> and other one that is uncertainly but didn't try the CI Server.
>
> I think all can live together while is not a must for the rest that don't
> want it the others option, so what's about if we release with the
> super-simple steps Chris proposal, and others wanting to use CI do that
> when is their RM turn ? (of course maintaining it and making it work for
> his release without requiring nothing for the rest that doesn't want it).
>
> Release as other projects do is recommended but not required, the same as
> the actual CI server (but this one should be less recommended since is a
> royale-only practice not seen in any other place).
>
> What's the important thing is to release, do it, and do it easily and
> often.
>
> Thanks
>
>
>
> El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
> christofer.dutz@c-ware.de<ma...@c-ware.de>>) escribió:
>
>
> Ok,
>
> I'll write this a last time as I do feel like we're going in circles and
> will from now on not participate in any discussion involving releasing on a
> CI server.
>
> A correct Maven release would use (There will be some additional profiles
> to activate to include all modules)
>
> 1) the "mvn release:branch" call in order to create the branch and bump
> the version of develop to the next version.
> 2) the "mvn release:prepare" to change the pom to the release version, set
> the timestamp in the pom (for reproducible builds) build ... if all tests
> are good, commit the changes, tag this commit, update the poms to the next
> development version, commit those changes and push everything.
> 3) the "mvn release:perform" which will checkout the tagged version build
> everything with the "apache-release" profile turned on (Which causes the
> source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
> as the assembly) This also deploys the built artifacts to Nexus.
>
> Most of that you are already doing on the CI server however you're not
> letting it do all automatically (For lack of credentials)
>
> But ... if you would just be doing those steps on the RM machine.
>
> Chris
>
>
>
>
>
> Am 26.03.20, 05:54 schrieb "Alex Harui" <aharui@adobe.com.INVALID<mailto:
> aharui@adobe.com.INVALID>>:
>
>
>
>     On 3/25/20, 4:46 PM, "Carlos Rovira" <carlosrovira@apache.org<mailto:
> carlosrovira@apache.org>> wrote:
>
>         > What I want to know is what the Maven commands should be to
> create a
>         > release in this "conventional process" you are referring to.
>         >
>
>         If you want to know what's the conventional maven process is, I
> think I can
>         ask Chris if he wants to work with me on that process, since he
> already did
>         many other Apache projects, we can expect the process is what is
> needed for
>         us to. But just expect that will be a series of standard maven
> commands
>         (prepare, release,...), so nothing strange at all (I expect).
>
>         Do you want us to do that?
>
>     Yes.  I want to know what the series of standard Maven commands are.
> Then we can figure out how to convert them to run on the CI server.
>
>     -Alex
>
>         Thanks
>
>
>         >
>         > Maybe someone else can explain better than me.
>         >
>         > -Alex
>         >
>         > On 3/25/20, 2:22 PM, "Carlos Rovira" <carlosrovira@apache.org
> <ma...@apache.org>>
> wrote:
>         >
>         >     Hi Alex,
>         >
>         >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>         > (<ah...@adobe.com.invalid>>)
>         >     escribió:
>         >
>         >     > Carlos,
>         >     >
>         >     > I'm pretty sure that part of the "conventional process"
> you want to
>         > try
>         >     > requires filling the staging repo from a local machine.
>         >     >
>         >
>         >     This is what we already did. If you go to [1] will see [2].
> That was
>         > the
>         >     upload of compiler to the staging repo. When trying to do
> the same for
>         >     typedefs it failed when trying to fill repo from local
> machine. I think
>         >     Chris or I should not take more time in trying to fix Ant
> scripts that
>         > are
>         >     failing.
>         >
>         >     Thanks
>         >
>         >     [1]
>         >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
>         >     [2]
>         >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
>         >
>         >
>         >
>         >
>         >     >
>         >     > --
>         >     > Carlos Rovira
>         >     >
>         >
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>         >     >
>         >     >
>         >     >
>         >     >
>         >
>         >
>         >
>
>         --
>         Carlos Rovira
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>
>
>
>
>
>
> --
>
> Frédéric Gilli
>
> mob.0668542622
>
> http://www.cristallium.com
>
> [cid:171168797bb6addd0331]<http://www.cristallium.com>
>
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: https://www.patreon.com/piotrzarzycki
>
>

-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

RE: Releasing: Finally giving up

Posted by Yishay Weiss <yi...@hotmail.com>.
Hi All,

I too, feel very uncomfortable participating in these threads. While grateful to Carlos and Chris for their work I’m very annoyed with the tone of ultimatums and doom and gloom. Alex has put in a lot of work into this and I trust his concerns are technical, rather than protecting his ego as has been suggested. We need to get this discussion back on technical tracks.

Since Chris has given up, and it looks like Carlos has as well, I volunteer to start the release process from scratch next Sunday, which is after Israel has switched to day light saving. I will try to do the process incrementally and in parallel to my other tasks. If by the end of the week it turns out the process is too cumbersome and cannot realistically be made to work smoothly I will be in favor of changing the requirements to enable Chris’s mvn setup to be the main release tool.

Thanks,
Yishay

From: Piotr Zarzycki<ma...@gmail.com>
Sent: Thursday, March 26, 2020 1:27 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Releasing: Finally giving up

Hi All,

I'm member of Apache Foundation for quite some time now. I think I have wrote maybe 2-3 emails during that time on members mailing list. - Why? - well I'm a person which doesn't like never ending stories, stories which are not end up with consensus nor action and I'm sorry but this is how it looks like in most cases there. Here we are in Apache Royale project where this thread ended up exactly the same - never ending story. - As PMC of this project I would like to say enough! :)

I had hope that when Carlos and Chris try CI steps and in the process they may have some issues, but they will end up in the same place as I ended up where I was able to prepare RC1 in about 2h without the problem. It turns out that they end up in the place where I have started, in the place where I have spend 5-6 days of work to finally reach stable point. They ended up frustrated in the same way as I was!

I really don't care now what kind of issue they have now, whether it's fixable or not - I just have enough of those never ending discussions where there is absolutely no results.

I met Chris in US in Miami and I have spend with him best time ever, he is really great developer - if he is saying that he will have release process in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not in a week - start today!

Please start whole work on that and make it happen. I will be the first who try the process and maybe with Chris's help we will solve also issue with uploading artifacts to staging area which we had.

Good Luck,
Piotr

czw., 26 mar 2020 o 12:02 <co...@cristallium.com>> napisał(a):

Hi Guys,

I'm a lover of Flex dev guy since more than 10 years, been members of Flex group on Montpellier (France) at golden age of Flex and go at all conferences when Michaël Chaize came to Montpellier (and using Flex every day).

First of all I want to thank every one of you for your hard work, and congratulate you for the actual Apache Royale capabilities.
With the last features (especialy datagrid), today your great work make possible to use Apache Royale in business application. Of course, there are bugs, but when reported, it's quickly fix, this is great.

Now, this is a huge opportunity but also risk for all guys like me to adop Apache Royale for futur projects or use it instead of using Air when it's possible.
Personnaly, I first use it on my own Webs applications and perhaps for my customers on little applications for the begin. My big enormous worry is to use it and be alone in front of a SDK bug.
Seeing new release every 1 or 2 months should certainly reassure me. For now I see SDK 0.9.7 since a lot of time and this make me affraid and I don't understand why there is no 0.9.8.

I'm speaking as an Apache Royale SDK user : I'm very sad to read these debates on the subject of tools to use for making release. I don't care about tools nedeed or not to build the release SDK.
I would like use Apache Royale to build RAD (Rapid Application Dev) Web applications and see more and more SDK features added, and participate to project (like today) by reporting bug  by using my time on isolate the bug and make tests cases with screenshoots to save your time in fixing it.

Using Reac, Bootstrap, AngularJS or other similar is a back to 80's. How can I explain my customer that I need 3 ou 4 days to make thinks that took me 1 day with Flex ?
The big competitive advantage of Apache Royale is not only be able to re-use Flex apps but is also simplicity and time saving where other SDK can't do it. (I think you already know that)

I am convinced that all guys like me will jump using Royale when they will know that there is a bug free SDK with fast evolution available. (unfortunaly it's not known enough, nobody know someone working in newspapers ?)

So please, I beg you, don't waste your time on things that are not essential and like Carlos said, go forward. From outside view, Apache Royale stay sticky to 0.9.7.

You are so close of a v1.0, I hope see it very soon and other releases with bugs fix every 1, 2 or 3 months.
Consider my comments as support and not criticism.

Thanks again for your hard work.

Long life and success to Apache Royale !

Fred



Le 26.03.2020 09:26, Carlos Rovira a écrit :
Hi,

that's amazingly simple, so I think we should go that way without doubt. I
think reached this point there's a clear sense of that we need to go that
route.

We tried our best to stick with the previous process and we're all
loosing lots of time. Then currently seems no more people in the community
was interested in this thread, event to comment a single line (here or in
the other users list thread), what means that or there's no more people
like us in this project or people really is not interested and just want us
to release and go forward.

As previously I think most of the PMCs here (Om, Josh, Greg and me for
sure), probably Yishay for his concise comments are more for this.
My thinking is that the right now I think only 2 PMCs are for CI Server,
and other one that is uncertainly but didn't try the CI Server.

I think all can live together while is not a must for the rest that don't
want it the others option, so what's about if we release with the
super-simple steps Chris proposal, and others wanting to use CI do that
when is their RM turn ? (of course maintaining it and making it work for
his release without requiring nothing for the rest that doesn't want it).

Release as other projects do is recommended but not required, the same as
the actual CI server (but this one should be less recommended since is a
royale-only practice not seen in any other place).

What's the important thing is to release, do it, and do it easily and often.

Thanks



El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
christofer.dutz@c-ware.de<ma...@c-ware.de>>) escribió:


Ok,

I'll write this a last time as I do feel like we're going in circles and
will from now on not participate in any discussion involving releasing on a
CI server.

A correct Maven release would use (There will be some additional profiles
to activate to include all modules)

1) the "mvn release:branch" call in order to create the branch and bump
the version of develop to the next version.
2) the "mvn release:prepare" to change the pom to the release version, set
the timestamp in the pom (for reproducible builds) build ... if all tests
are good, commit the changes, tag this commit, update the poms to the next
development version, commit those changes and push everything.
3) the "mvn release:perform" which will checkout the tagged version build
everything with the "apache-release" profile turned on (Which causes the
source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
as the assembly) This also deploys the built artifacts to Nexus.

Most of that you are already doing on the CI server however you're not
letting it do all automatically (For lack of credentials)

But ... if you would just be doing those steps on the RM machine.

Chris





Am 26.03.20, 05:54 schrieb "Alex Harui" <ah...@adobe.com.INVALID>>:



    On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org>> wrote:

        > What I want to know is what the Maven commands should be to
create a
        > release in this "conventional process" you are referring to.
        >

        If you want to know what's the conventional maven process is, I
think I can
        ask Chris if he wants to work with me on that process, since he
already did
        many other Apache projects, we can expect the process is what is
needed for
        us to. But just expect that will be a series of standard maven
commands
        (prepare, release,...), so nothing strange at all (I expect).

        Do you want us to do that?

    Yes.  I want to know what the series of standard Maven commands are.
Then we can figure out how to convert them to run on the CI server.

    -Alex

        Thanks


        >
        > Maybe someone else can explain better than me.
        >
        > -Alex
        >
        > On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org>>
wrote:
        >
        >     Hi Alex,
        >
        >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
        > (<ah...@adobe.com.invalid>>)
        >     escribió:
        >
        >     > Carlos,
        >     >
        >     > I'm pretty sure that part of the "conventional process"
you want to
        > try
        >     > requires filling the staging repo from a local machine.
        >     >
        >
        >     This is what we already did. If you go to [1] will see [2].
That was
        > the
        >     upload of compiler to the staging repo. When trying to do
the same for
        >     typedefs it failed when trying to fill repo from local
machine. I think
        >     Chris or I should not take more time in trying to fix Ant
scripts that
        > are
        >     failing.
        >
        >     Thanks
        >
        >     [1]
        >
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
        >     [2]
        >
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
        >
        >
        >
        >
        >     >
        >     > --
        >     > Carlos Rovira
        >     >
        >
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
        >     >
        >     >
        >     >
        >     >
        >
        >
        >

        --
        Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0






--

Frédéric Gilli

mob.0668542622

http://www.cristallium.com

[cid:171168797bb6addd0331]<http://www.cristallium.com>




--

Piotr Zarzycki

Patreon: https://www.patreon.com/piotrzarzycki


Re: Releasing: Finally giving up

Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi All,

I'm member of Apache Foundation for quite some time now. I think I have
wrote maybe 2-3 emails during that time on members mailing list. - Why? -
well I'm a person which doesn't like never ending stories, stories which
are not end up with consensus nor action and I'm sorry but this is how it
looks like in most cases there. Here we are in Apache Royale project where
this thread ended up exactly the same - never ending story. - As PMC of
this project I would like to say enough! :)

I had hope that when Carlos and Chris try CI steps and in the process they
may have some issues, but they will end up in the same place as I ended up
where I was able to prepare RC1 in about 2h without the problem. It turns
out that they end up in the place where I have started, in the place where
I have spend 5-6 days of work to finally reach stable point. They ended up
frustrated in the same way as I was!

I really don't care now what kind of issue they have now, whether it's
fixable or not - I just have enough of those never ending discussions where
there is absolutely no results.

I met Chris in US in Miami and I have spend with him best time ever, he is
really great developer - if he is saying that he will have release process
in 3-4 steps on my machine - I'm +1 make it so. Not tomorrow, not in a week
- start today!

Please start whole work on that and make it happen. I will be the first who
try the process and maybe with Chris's help we will solve also issue with
uploading artifacts to staging area which we had.

Good Luck,
Piotr

czw., 26 mar 2020 o 12:02 <co...@cristallium.com> napisał(a):

> Hi Guys,
>
> I'm a lover of Flex dev guy since more than 10 years, been members of Flex group on Montpellier (France) at golden age of Flex and go at all conferences when Michaël Chaize came to Montpellier (and using Flex every day).
>
> First of all I want to thank every one of you for your hard work, and congratulate you for the actual Apache Royale capabilities.
> With the last features (especialy datagrid), today your great work make possible to use Apache Royale in business application. Of course, there are bugs, but when reported, it's quickly fix, this is great.
>
> Now, this is a huge opportunity but also risk for all guys like me to adop Apache Royale for futur projects or use it instead of using Air when it's possible.
> Personnaly, I first use it on my own Webs applications and perhaps for my customers on little applications for the begin. My big enormous worry is to use it and be alone in front of a SDK bug.
> Seeing new release every 1 or 2 months should certainly reassure me. For now I see SDK 0.9.7 since a lot of time and this make me affraid and I don't understand why there is no 0.9.8.
>
> I'm speaking as an Apache Royale SDK user : I'm very sad to read these debates on the subject of tools to use for making release. I don't care about tools nedeed or not to build the release SDK.
> I would like use Apache Royale to build RAD (Rapid Application Dev) Web applications and see more and more SDK features added, and participate to project (like today) by reporting bug  by using my time on isolate the bug and make tests cases with screenshoots to save your time in fixing it.
>
> Using Reac, Bootstrap, AngularJS or other similar is a back to 80's. How can I explain my customer that I need 3 ou 4 days to make thinks that took me 1 day with Flex ?
> The big competitive advantage of Apache Royale is not only be able to re-use Flex apps but is also simplicity and time saving where other SDK can't do it. (I think you already know that)
>
> I am convinced that all guys like me will jump using Royale when they will know that there is a bug free SDK with fast evolution available. (unfortunaly it's not known enough, nobody know someone working in newspapers ?)
>
> So please, I beg you, don't waste your time on things that are not essential and like Carlos said, go forward. From outside view, Apache Royale stay sticky to 0.9.7.
>
> You are so close of a v1.0, I hope see it very soon and other releases with bugs fix every 1, 2 or 3 months.
> Consider my comments as support and not criticism.
>
> Thanks again for your hard work.
>
> Long life and success to Apache Royale !
>
> Fred
>
>
>
> Le 26.03.2020 09:26, Carlos Rovira a écrit :
>
> Hi,
>
> that's amazingly simple, so I think we should go that way without doubt. I
> think reached this point there's a clear sense of that we need to go that
> route.
>
> We tried our best to stick with the previous process and we're all
> loosing lots of time. Then currently seems no more people in the community
> was interested in this thread, event to comment a single line (here or in
> the other users list thread), what means that or there's no more people
> like us in this project or people really is not interested and just want us
> to release and go forward.
>
> As previously I think most of the PMCs here (Om, Josh, Greg and me for
> sure), probably Yishay for his concise comments are more for this.
> My thinking is that the right now I think only 2 PMCs are for CI Server,
> and other one that is uncertainly but didn't try the CI Server.
>
> I think all can live together while is not a must for the rest that don't
> want it the others option, so what's about if we release with the
> super-simple steps Chris proposal, and others wanting to use CI do that
> when is their RM turn ? (of course maintaining it and making it work for
> his release without requiring nothing for the rest that doesn't want it).
>
> Release as other projects do is recommended but not required, the same as
> the actual CI server (but this one should be less recommended since is a
> royale-only practice not seen in any other place).
>
> What's the important thing is to release, do it, and do it easily and
> often.
>
> Thanks
>
>
>
> El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
> christofer.dutz@c-ware.de>) escribió:
>
> Ok,
>
> I'll write this a last time as I do feel like we're going in circles and
> will from now on not participate in any discussion involving releasing on a
> CI server.
>
> A correct Maven release would use (There will be some additional profiles
> to activate to include all modules)
>
> 1) the "mvn release:branch" call in order to create the branch and bump
> the version of develop to the next version.
> 2) the "mvn release:prepare" to change the pom to the release version, set
> the timestamp in the pom (for reproducible builds) build ... if all tests
> are good, commit the changes, tag this commit, update the poms to the next
> development version, commit those changes and push everything.
> 3) the "mvn release:perform" which will checkout the tagged version build
> everything with the "apache-release" profile turned on (Which causes the
> source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
> as the assembly) This also deploys the built artifacts to Nexus.
>
> Most of that you are already doing on the CI server however you're not
> letting it do all automatically (For lack of credentials)
>
> But ... if you would just be doing those steps on the RM machine.
>
> Chris
>
>
>
>
>
> Am 26.03.20, 05:54 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
>
>
>
>     On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>
>         > What I want to know is what the Maven commands should be to
> create a
>         > release in this "conventional process" you are referring to.
>         >
>
>         If you want to know what's the conventional maven process is, I
> think I can
>         ask Chris if he wants to work with me on that process, since he
> already did
>         many other Apache projects, we can expect the process is what is
> needed for
>         us to. But just expect that will be a series of standard maven
> commands
>         (prepare, release,...), so nothing strange at all (I expect).
>
>         Do you want us to do that?
>
>     Yes.  I want to know what the series of standard Maven commands are.
> Then we can figure out how to convert them to run on the CI server.
>
>     -Alex
>
>         Thanks
>
>
>         >
>         > Maybe someone else can explain better than me.
>         >
>         > -Alex
>         >
>         > On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org>
> wrote:
>         >
>         >     Hi Alex,
>         >
>         >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>         > (<ah...@adobe.com.invalid>)
>         >     escribió:
>         >
>         >     > Carlos,
>         >     >
>         >     > I'm pretty sure that part of the "conventional process"
> you want to
>         > try
>         >     > requires filling the staging repo from a local machine.
>         >     >
>         >
>         >     This is what we already did. If you go to [1] will see [2].
> That was
>         > the
>         >     upload of compiler to the staging repo. When trying to do
> the same for
>         >     typedefs it failed when trying to fill repo from local
> machine. I think
>         >     Chris or I should not take more time in trying to fix Ant
> scripts that
>         > are
>         >     failing.
>         >
>         >     Thanks
>         >
>         >     [1]
>         >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
>         >     [2]
>         >
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
>         >
>         >
>         >
>         >
>         >     >
>         >     > --
>         >     > Carlos Rovira
>         >     >
>         >
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>         >     >
>         >     >
>         >     >
>         >     >
>         >
>         >
>         >
>
>         --
>         Carlos Rovira
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>
>
>
>
>
>
> --
>
> Frédéric Gilli
>
> mob.0668542622
>
> http://www.cristallium.com
>
> <http://www.cristallium.com>
>
>
>
>

-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Releasing: Finally giving up

Posted by co...@cristallium.com.
Hi Guys,

I'm a lover of Flex dev guy since more than 10 years, been members of
Flex group on Montpellier (France) at golden age of Flex and go at all
conferences when Michaël Chaize came to Montpellier (and using Flex
every day).

First of all I want to thank every one of you for your hard work, and
congratulate you for the actual Apache Royale capabilities.
With the last features (especialy datagrid), today your great work make
possible to use Apache Royale in business application. Of course, there
are bugs, but when reported, it's quickly fix, this is great.

Now, this is a huge opportunity but also risk for all guys like me to
adop Apache Royale for futur projects or use it instead of using Air
when it's possible.
Personnaly, I first use it on my own Webs applications and perhaps for
my customers on little applications for the begin. My big enormous worry
is to use it and be alone in front of a SDK bug. 
Seeing new release every 1 or 2 months should certainly reassure me. For
now I see SDK 0.9.7 since a lot of time and this make me affraid and I
don't understand why there is no 0.9.8.

I'm speaking as an Apache Royale SDK user : I'm very sad to read these
debates on the subject of tools to use for making release. I don't care
about tools nedeed or not to build the release SDK.
I would like use Apache Royale to build RAD (Rapid Application Dev) Web
applications and see more and more SDK features added, and participate
to project (like today) by reporting bug  by using my time on isolate
the bug and make tests cases with screenshoots to save your time in
fixing it. 

Using Reac, Bootstrap, AngularJS or other similar is a back to 80's. How
can I explain my customer that I need 3 ou 4 days to make thinks that
took me 1 day with Flex ? 
The big competitive advantage of Apache Royale is not only be able to
re-use Flex apps but is also simplicity and time saving where other SDK
can't do it. (I think you already know that)

I am convinced that all guys like me will jump using Royale when they
will know that there is a bug free SDK with fast evolution available.
(unfortunaly it's not known enough, nobody know someone working in
newspapers ?) 

So please, I beg you, don't waste your time on things that are not
essential and like Carlos said, go forward. From outside view, Apache
Royale stay sticky to 0.9.7. 

You are so close of a v1.0, I hope see it very soon and other releases
with bugs fix every 1, 2 or 3 months.
Consider my comments as support and not criticism.

Thanks again for your hard work.

Long life and success to Apache Royale !

Fred

Le 26.03.2020 09:26, Carlos Rovira a écrit :

> Hi,
> 
> that's amazingly simple, so I think we should go that way without doubt. I
> think reached this point there's a clear sense of that we need to go that
> route.
> 
> We tried our best to stick with the previous process and we're all
> loosing lots of time. Then currently seems no more people in the community
> was interested in this thread, event to comment a single line (here or in
> the other users list thread), what means that or there's no more people
> like us in this project or people really is not interested and just want us
> to release and go forward.
> 
> As previously I think most of the PMCs here (Om, Josh, Greg and me for
> sure), probably Yishay for his concise comments are more for this.
> My thinking is that the right now I think only 2 PMCs are for CI Server,
> and other one that is uncertainly but didn't try the CI Server.
> 
> I think all can live together while is not a must for the rest that don't
> want it the others option, so what's about if we release with the
> super-simple steps Chris proposal, and others wanting to use CI do that
> when is their RM turn ? (of course maintaining it and making it work for
> his release without requiring nothing for the rest that doesn't want it).
> 
> Release as other projects do is recommended but not required, the same as
> the actual CI server (but this one should be less recommended since is a
> royale-only practice not seen in any other place).
> 
> What's the important thing is to release, do it, and do it easily and often.
> 
> Thanks
> 
> El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
> christofer.dutz@c-ware.de>) escribió:
> 
>> Ok,
>> 
>> I'll write this a last time as I do feel like we're going in circles and
>> will from now on not participate in any discussion involving releasing on a
>> CI server.
>> 
>> A correct Maven release would use (There will be some additional profiles
>> to activate to include all modules)
>> 
>> 1) the "mvn release:branch" call in order to create the branch and bump
>> the version of develop to the next version.
>> 2) the "mvn release:prepare" to change the pom to the release version, set
>> the timestamp in the pom (for reproducible builds) build ... if all tests
>> are good, commit the changes, tag this commit, update the poms to the next
>> development version, commit those changes and push everything.
>> 3) the "mvn release:perform" which will checkout the tagged version build
>> everything with the "apache-release" profile turned on (Which causes the
>> source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
>> as the assembly) This also deploys the built artifacts to Nexus.
>> 
>> Most of that you are already doing on the CI server however you're not
>> letting it do all automatically (For lack of credentials)
>> 
>> But ... if you would just be doing those steps on the RM machine.
>> 
>> Chris
>> 
>> Am 26.03.20, 05:54 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
>> 
>> On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>> 
>>> What I want to know is what the Maven commands should be to
>> create a
>>> release in this "conventional process" you are referring to.
>>> 
>> 
>> If you want to know what's the conventional maven process is, I
>> think I can
>> ask Chris if he wants to work with me on that process, since he
>> already did
>> many other Apache projects, we can expect the process is what is
>> needed for
>> us to. But just expect that will be a series of standard maven
>> commands
>> (prepare, release,...), so nothing strange at all (I expect).
>> 
>> Do you want us to do that?
>> 
>> Yes.  I want to know what the series of standard Maven commands are.
>> Then we can figure out how to convert them to run on the CI server.
>> 
>> -Alex
>> 
>> Thanks
>> 
>>> 
>>> Maybe someone else can explain better than me.
>>> 
>>> -Alex
>>> 
>>> On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org>
>> wrote:
>>> 
>>> Hi Alex,
>>> 
>>> El mié., 25 mar. 2020 a las 21:26, Alex Harui
>>> (<ah...@adobe.com.invalid>)
>>> escribió:
>>> 
>>>> Carlos,
>>>>
>>>> I'm pretty sure that part of the "conventional process"
>> you want to
>>> try
>>>> requires filling the staging repo from a local machine.
>>>>
>>> 
>>> This is what we already did. If you go to [1] will see [2].
>> That was
>>> the
>>> upload of compiler to the staging repo. When trying to do
>> the same for
>>> typedefs it failed when trying to fill repo from local
>> machine. I think
>>> Chris or I should not take more time in trying to fix Ant
>> scripts that
>>> are
>>> failing.
>>> 
>>> Thanks
>>> 
>>> [1]
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
>>> [2]
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
>>> 
>>> 
>>> 
>>> 
>>>>
>>>> --
>>>> Carlos Rovira
>>>>
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>>>>
>>>>
>>>>
>>>>
>>> 
>>> 
>>> 
>> 
>> --
>> Carlos Rovira
>> 
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0

-- 
Frédéric Gilli 

mob.0668542622

http://www.cristallium.com

 [1]

 

Links:
------
[1] http://www.cristallium.com

Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.
Chris and Carlos, please actually produce a wiki page with the list of Maven commands.  I'm sorry, but don't think it will be as amazingly simple as you stated.  So do it!  Maybe Chris first to document the steps in a wiki page, then Carlos next to prove that Chris didn't miss anything in the documentation.  Also, please make sure that the parameters used to produce the artifacts includes the plugins and options for creating a reproducible binary.  Don't worry about if it actually matches anything right now.  I think I've explained why that is on another thread.

Like I said, the test is that the staging repo will have the same set of files as the 0.9.6 release (other than any new SWCs and with a different version number.

I think there will be more commands than just release:prepare and release:perform, calling set-property on things.  It is a lot of typing for the RM, prone to typing errors, which is why it was automated in Ant scripts and CI steps.

I would actually love to be wrong about this, because then I think we could reduce the set of CI steps to match as well.  As I've written many times, most of the CI steps just do the minimum Maven commands to build the release artifacts using the Maven poms we had in the past.

So go for it, and let us know when the final list of Maven commands is ready.

Don't worry about the Ant artifacts either for now.  Just get the Maven staging repo ready.  The Ant steps already know how to pull the Maven source artifact from staging and build the Ant artifacts.  I'm still unclear why it will ever make sense to drive that portion from Maven.  I have yet to see a technical explanation of how we can validate that Ant can use the build.xml files to create the Ant artifacts without actually running Ant, but that can wait until after we get the set of Maven commands for the Maven artifacts first.

Thanks,
-Alex

On 3/26/20, 1:26 AM, "Carlos Rovira" <ca...@apache.org> wrote:

    Hi,
    
    that's amazingly simple, so I think we should go that way without doubt. I
    think reached this point there's a clear sense of that we need to go that
    route.
    
    We tried our best to stick with the previous process and we're all
    loosing lots of time. Then currently seems no more people in the community
    was interested in this thread, event to comment a single line (here or in
    the other users list thread), what means that or there's no more people
    like us in this project or people really is not interested and just want us
    to release and go forward.
    
    As previously I think most of the PMCs here (Om, Josh, Greg and me for
    sure), probably Yishay for his concise comments are more for this.
    My thinking is that the right now I think only 2 PMCs are for CI Server,
    and other one that is uncertainly but didn't try the CI Server.
    
    I think all can live together while is not a must for the rest that don't
    want it the others option, so what's about if we release with the
    super-simple steps Chris proposal, and others wanting to use CI do that
    when is their RM turn ? (of course maintaining it and making it work for
    his release without requiring nothing for the rest that doesn't want it).
    
    Release as other projects do is recommended but not required, the same as
    the actual CI server (but this one should be less recommended since is a
    royale-only practice not seen in any other place).
    
    What's the important thing is to release, do it, and do it easily and often.
    
    Thanks
    
    
    
    El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
    christofer.dutz@c-ware.de>) escribió:
    
    > Ok,
    >
    > I'll write this a last time as I do feel like we're going in circles and
    > will from now on not participate in any discussion involving releasing on a
    > CI server.
    >
    > A correct Maven release would use (There will be some additional profiles
    > to activate to include all modules)
    >
    > 1) the "mvn release:branch" call in order to create the branch and bump
    > the version of develop to the next version.
    > 2) the "mvn release:prepare" to change the pom to the release version, set
    > the timestamp in the pom (for reproducible builds) build ... if all tests
    > are good, commit the changes, tag this commit, update the poms to the next
    > development version, commit those changes and push everything.
    > 3) the "mvn release:perform" which will checkout the tagged version build
    > everything with the "apache-release" profile turned on (Which causes the
    > source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
    > as the assembly) This also deploys the built artifacts to Nexus.
    >
    > Most of that you are already doing on the CI server however you're not
    > letting it do all automatically (For lack of credentials)
    >
    > But ... if you would just be doing those steps on the RM machine.
    >
    > Chris
    >
    >
    >
    >
    >
    > Am 26.03.20, 05:54 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
    >
    >
    >
    >     On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org> wrote:
    >
    >         > What I want to know is what the Maven commands should be to
    > create a
    >         > release in this "conventional process" you are referring to.
    >         >
    >
    >         If you want to know what's the conventional maven process is, I
    > think I can
    >         ask Chris if he wants to work with me on that process, since he
    > already did
    >         many other Apache projects, we can expect the process is what is
    > needed for
    >         us to. But just expect that will be a series of standard maven
    > commands
    >         (prepare, release,...), so nothing strange at all (I expect).
    >
    >         Do you want us to do that?
    >
    >     Yes.  I want to know what the series of standard Maven commands are.
    > Then we can figure out how to convert them to run on the CI server.
    >
    >     -Alex
    >
    >         Thanks
    >
    >
    >         >
    >         > Maybe someone else can explain better than me.
    >         >
    >         > -Alex
    >         >
    >         > On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org>
    > wrote:
    >         >
    >         >     Hi Alex,
    >         >
    >         >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
    >         > (<ah...@adobe.com.invalid>)
    >         >     escribió:
    >         >
    >         >     > Carlos,
    >         >     >
    >         >     > I'm pretty sure that part of the "conventional process"
    > you want to
    >         > try
    >         >     > requires filling the staging repo from a local machine.
    >         >     >
    >         >
    >         >     This is what we already did. If you go to [1] will see [2].
    > That was
    >         > the
    >         >     upload of compiler to the staging repo. When trying to do
    > the same for
    >         >     typedefs it failed when trying to fill repo from local
    > machine. I think
    >         >     Chris or I should not take more time in trying to fix Ant
    > scripts that
    >         > are
    >         >     failing.
    >         >
    >         >     Thanks
    >         >
    >         >     [1]
    >         >
    > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C52c9a29e54a9447502a608d7d15f6d7e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208080098996954&amp;sdata=u6gKxmAvurfd%2FeqZuuQKjQPjzhaQe8C2D9Y8H3muS90%3D&amp;reserved=0
    >         >     [2]
    >         >
    > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C52c9a29e54a9447502a608d7d15f6d7e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208080098996954&amp;sdata=n2yCWxI1vqrKMYihl3PtyEqNAwKjk9G24JQMhFJaiNY%3D&amp;reserved=0
    >         >
    >         >
    >         >
    >         >
    >         >     >
    >         >     > --
    >         >     > Carlos Rovira
    >         >     >
    >         >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C52c9a29e54a9447502a608d7d15f6d7e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208080098996954&amp;sdata=8TI9LM0zCVzPV3NSeJRgEzmvyvMIfensPcK3l4mKWBo%3D&amp;reserved=0
    >         >     >
    >         >     >
    >         >     >
    >         >     >
    >         >
    >         >
    >         >
    >
    >         --
    >         Carlos Rovira
    >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C52c9a29e54a9447502a608d7d15f6d7e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208080098996954&amp;sdata=8TI9LM0zCVzPV3NSeJRgEzmvyvMIfensPcK3l4mKWBo%3D&amp;reserved=0
    >
    >
    >
    >
    >
    
    -- 
    Carlos Rovira
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C52c9a29e54a9447502a608d7d15f6d7e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637208080098996954&amp;sdata=8TI9LM0zCVzPV3NSeJRgEzmvyvMIfensPcK3l4mKWBo%3D&amp;reserved=0
    


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi,

that's amazingly simple, so I think we should go that way without doubt. I
think reached this point there's a clear sense of that we need to go that
route.

We tried our best to stick with the previous process and we're all
loosing lots of time. Then currently seems no more people in the community
was interested in this thread, event to comment a single line (here or in
the other users list thread), what means that or there's no more people
like us in this project or people really is not interested and just want us
to release and go forward.

As previously I think most of the PMCs here (Om, Josh, Greg and me for
sure), probably Yishay for his concise comments are more for this.
My thinking is that the right now I think only 2 PMCs are for CI Server,
and other one that is uncertainly but didn't try the CI Server.

I think all can live together while is not a must for the rest that don't
want it the others option, so what's about if we release with the
super-simple steps Chris proposal, and others wanting to use CI do that
when is their RM turn ? (of course maintaining it and making it work for
his release without requiring nothing for the rest that doesn't want it).

Release as other projects do is recommended but not required, the same as
the actual CI server (but this one should be less recommended since is a
royale-only practice not seen in any other place).

What's the important thing is to release, do it, and do it easily and often.

Thanks



El jue., 26 mar. 2020 a las 8:24, Christofer Dutz (<
christofer.dutz@c-ware.de>) escribió:

> Ok,
>
> I'll write this a last time as I do feel like we're going in circles and
> will from now on not participate in any discussion involving releasing on a
> CI server.
>
> A correct Maven release would use (There will be some additional profiles
> to activate to include all modules)
>
> 1) the "mvn release:branch" call in order to create the branch and bump
> the version of develop to the next version.
> 2) the "mvn release:prepare" to change the pom to the release version, set
> the timestamp in the pom (for reproducible builds) build ... if all tests
> are good, commit the changes, tag this commit, update the poms to the next
> development version, commit those changes and push everything.
> 3) the "mvn release:perform" which will checkout the tagged version build
> everything with the "apache-release" profile turned on (Which causes the
> source.jars, Javadoc.jars, hashes and gpg singatures to be created as well
> as the assembly) This also deploys the built artifacts to Nexus.
>
> Most of that you are already doing on the CI server however you're not
> letting it do all automatically (For lack of credentials)
>
> But ... if you would just be doing those steps on the RM machine.
>
> Chris
>
>
>
>
>
> Am 26.03.20, 05:54 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
>
>
>
>     On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>
>         > What I want to know is what the Maven commands should be to
> create a
>         > release in this "conventional process" you are referring to.
>         >
>
>         If you want to know what's the conventional maven process is, I
> think I can
>         ask Chris if he wants to work with me on that process, since he
> already did
>         many other Apache projects, we can expect the process is what is
> needed for
>         us to. But just expect that will be a series of standard maven
> commands
>         (prepare, release,...), so nothing strange at all (I expect).
>
>         Do you want us to do that?
>
>     Yes.  I want to know what the series of standard Maven commands are.
> Then we can figure out how to convert them to run on the CI server.
>
>     -Alex
>
>         Thanks
>
>
>         >
>         > Maybe someone else can explain better than me.
>         >
>         > -Alex
>         >
>         > On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org>
> wrote:
>         >
>         >     Hi Alex,
>         >
>         >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
>         > (<ah...@adobe.com.invalid>)
>         >     escribió:
>         >
>         >     > Carlos,
>         >     >
>         >     > I'm pretty sure that part of the "conventional process"
> you want to
>         > try
>         >     > requires filling the staging repo from a local machine.
>         >     >
>         >
>         >     This is what we already did. If you go to [1] will see [2].
> That was
>         > the
>         >     upload of compiler to the staging repo. When trying to do
> the same for
>         >     typedefs it failed when trying to fill repo from local
> machine. I think
>         >     Chris or I should not take more time in trying to fix Ant
> scripts that
>         > are
>         >     failing.
>         >
>         >     Thanks
>         >
>         >     [1]
>         >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
>         >     [2]
>         >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
>         >
>         >
>         >
>         >
>         >     >
>         >     > --
>         >     > Carlos Rovira
>         >     >
>         >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>         >     >
>         >     >
>         >     >
>         >     >
>         >
>         >
>         >
>
>         --
>         Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
>
>
>
>
>

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

Re: Releasing: Finally giving up

Posted by Christofer Dutz <ch...@c-ware.de>.
Ok, 

I'll write this a last time as I do feel like we're going in circles and will from now on not participate in any discussion involving releasing on a CI server.

A correct Maven release would use (There will be some additional profiles to activate to include all modules)

1) the "mvn release:branch" call in order to create the branch and bump the version of develop to the next version.
2) the "mvn release:prepare" to change the pom to the release version, set the timestamp in the pom (for reproducible builds) build ... if all tests are good, commit the changes, tag this commit, update the poms to the next development version, commit those changes and push everything.
3) the "mvn release:perform" which will checkout the tagged version build everything with the "apache-release" profile turned on (Which causes the source.jars, Javadoc.jars, hashes and gpg singatures to be created as well as the assembly) This also deploys the built artifacts to Nexus.

Most of that you are already doing on the CI server however you're not letting it do all automatically (For lack of credentials)

But ... if you would just be doing those steps on the RM machine.

Chris





Am 26.03.20, 05:54 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:

    
    
    On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org> wrote:
        
        > What I want to know is what the Maven commands should be to create a
        > release in this "conventional process" you are referring to.
        >
        
        If you want to know what's the conventional maven process is, I think I can
        ask Chris if he wants to work with me on that process, since he already did
        many other Apache projects, we can expect the process is what is needed for
        us to. But just expect that will be a series of standard maven commands
        (prepare, release,...), so nothing strange at all (I expect).
        
        Do you want us to do that?
    
    Yes.  I want to know what the series of standard Maven commands are.  Then we can figure out how to convert them to run on the CI server.
    
    -Alex
        
        Thanks
        
        
        >
        > Maybe someone else can explain better than me.
        >
        > -Alex
        >
        > On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org> wrote:
        >
        >     Hi Alex,
        >
        >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
        > (<ah...@adobe.com.invalid>)
        >     escribió:
        >
        >     > Carlos,
        >     >
        >     > I'm pretty sure that part of the "conventional process" you want to
        > try
        >     > requires filling the staging repo from a local machine.
        >     >
        >
        >     This is what we already did. If you go to [1] will see [2]. That was
        > the
        >     upload of compiler to the staging repo. When trying to do the same for
        >     typedefs it failed when trying to fill repo from local machine. I think
        >     Chris or I should not take more time in trying to fix Ant scripts that
        > are
        >     failing.
        >
        >     Thanks
        >
        >     [1]
        > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
        >     [2]
        > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
        >
        >
        >
        >
        >     >
        >     > --
        >     > Carlos Rovira
        >     >
        > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
        >     >
        >     >
        >     >
        >     >
        >
        >
        >
        
        -- 
        Carlos Rovira
        https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
        
    
    


Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.

On 3/25/20, 4:46 PM, "Carlos Rovira" <ca...@apache.org> wrote:
    
    > What I want to know is what the Maven commands should be to create a
    > release in this "conventional process" you are referring to.
    >
    
    If you want to know what's the conventional maven process is, I think I can
    ask Chris if he wants to work with me on that process, since he already did
    many other Apache projects, we can expect the process is what is needed for
    us to. But just expect that will be a series of standard maven commands
    (prepare, release,...), so nothing strange at all (I expect).
    
    Do you want us to do that?

Yes.  I want to know what the series of standard Maven commands are.  Then we can figure out how to convert them to run on the CI server.

-Alex
    
    Thanks
    
    
    >
    > Maybe someone else can explain better than me.
    >
    > -Alex
    >
    > On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org> wrote:
    >
    >     Hi Alex,
    >
    >     El mié., 25 mar. 2020 a las 21:26, Alex Harui
    > (<ah...@adobe.com.invalid>)
    >     escribió:
    >
    >     > Carlos,
    >     >
    >     > I'm pretty sure that part of the "conventional process" you want to
    > try
    >     > requires filling the staging repo from a local machine.
    >     >
    >
    >     This is what we already did. If you go to [1] will see [2]. That was
    > the
    >     upload of compiler to the staging repo. When trying to do the same for
    >     typedefs it failed when trying to fill repo from local machine. I think
    >     Chris or I should not take more time in trying to fix Ant scripts that
    > are
    >     failing.
    >
    >     Thanks
    >
    >     [1]
    > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&amp;reserved=0
    >     [2]
    > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&amp;reserved=0
    >
    >
    >
    >
    >     >
    >     > --
    >     > Carlos Rovira
    >     >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
    >     >
    >     >
    >     >
    >     >
    >
    >
    >
    
    -- 
    Carlos Rovira
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&amp;sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&amp;reserved=0
    


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
 Hi Alex,

El mié., 25 mar. 2020 a las 22:43, Alex Harui (<ah...@adobe.com.invalid>)
escribió:

> Carlos,
>
> When I wrote "from a local machine" that means to use whatever computer
> you want to use and not the CI server or steps.  ç


maybe I there's a communication problem, but what I said is that I used my
local machine not the CI Server (since is what the step required) to do the
staging for step 007 email commands, and while that worked for compiler, It
didn't for typedefs.


> What I want to know is what the Maven commands should be to create a
> release in this "conventional process" you are referring to.
>

If you want to know what's the conventional maven process is, I think I can
ask Chris if he wants to work with me on that process, since he already did
many other Apache projects, we can expect the process is what is needed for
us to. But just expect that will be a series of standard maven commands
(prepare, release,...), so nothing strange at all (I expect).

Do you want us to do that?

Thanks


>
> Maybe someone else can explain better than me.
>
> -Alex
>
> On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>
>     Hi Alex,
>
>     El mié., 25 mar. 2020 a las 21:26, Alex Harui
> (<ah...@adobe.com.invalid>)
>     escribió:
>
>     > Carlos,
>     >
>     > I'm pretty sure that part of the "conventional process" you want to
> try
>     > requires filling the staging repo from a local machine.
>     >
>
>     This is what we already did. If you go to [1] will see [2]. That was
> the
>     upload of compiler to the staging repo. When trying to do the same for
>     typedefs it failed when trying to fill repo from local machine. I think
>     Chris or I should not take more time in trying to fix Ant scripts that
> are
>     failing.
>
>     Thanks
>
>     [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2c3d44a188fa4d48de6208d7d1029468%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207681319693950&amp;sdata=TUrFSD0DLQzYs32p2qnzKOl7OLSGLt45sneONbtUnBQ%3D&amp;reserved=0
>     [2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2c3d44a188fa4d48de6208d7d1029468%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207681319693950&amp;sdata=DKffSbD1IJkCejOgCaV6qu%2FWRvR%2B1nh5p05%2Fex0Zmfg%3D&amp;reserved=0
>
>
>
>
>     >
>     > --
>     > Carlos Rovira
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2c3d44a188fa4d48de6208d7d1029468%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207681319693950&amp;sdata=H%2BzsfxujvhNDFfQzBT%2BVJG26as70%2BjpZLfCSS%2BCP6kc%3D&amp;reserved=0
>     >
>     >
>     >
>     >
>
>
>

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

Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.
Carlos,

When I wrote "from a local machine" that means to use whatever computer you want to use and not the CI server or steps.  What I want to know is what the Maven commands should be to create a release in this "conventional process" you are referring to.

Maybe someone else can explain better than me.

-Alex

On 3/25/20, 2:22 PM, "Carlos Rovira" <ca...@apache.org> wrote:

    Hi Alex,
    
    El mié., 25 mar. 2020 a las 21:26, Alex Harui (<ah...@adobe.com.invalid>)
    escribió:
    
    > Carlos,
    >
    > I'm pretty sure that part of the "conventional process" you want to try
    > requires filling the staging repo from a local machine.
    >
    
    This is what we already did. If you go to [1] will see [2]. That was the
    upload of compiler to the staging repo. When trying to do the same for
    typedefs it failed when trying to fill repo from local machine. I think
    Chris or I should not take more time in trying to fix Ant scripts that are
    failing.
    
    Thanks
    
    [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&amp;data=02%7C01%7Caharui%40adobe.com%7C2c3d44a188fa4d48de6208d7d1029468%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207681319693950&amp;sdata=TUrFSD0DLQzYs32p2qnzKOl7OLSGLt45sneONbtUnBQ%3D&amp;reserved=0
    [2] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&amp;data=02%7C01%7Caharui%40adobe.com%7C2c3d44a188fa4d48de6208d7d1029468%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207681319693950&amp;sdata=DKffSbD1IJkCejOgCaV6qu%2FWRvR%2B1nh5p05%2Fex0Zmfg%3D&amp;reserved=0
    
    
    
    
    >
    > --
    > Carlos Rovira
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2c3d44a188fa4d48de6208d7d1029468%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207681319693950&amp;sdata=H%2BzsfxujvhNDFfQzBT%2BVJG26as70%2BjpZLfCSS%2BCP6kc%3D&amp;reserved=0
    >
    >
    >
    >
    


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,

El mié., 25 mar. 2020 a las 21:26, Alex Harui (<ah...@adobe.com.invalid>)
escribió:

> Carlos,
>
> I'm pretty sure that part of the "conventional process" you want to try
> requires filling the staging repo from a local machine.
>

This is what we already did. If you go to [1] will see [2]. That was the
upload of compiler to the staging repo. When trying to do the same for
typedefs it failed when trying to fill repo from local machine. I think
Chris or I should not take more time in trying to fix Ant scripts that are
failing.

Thanks

[1] https://repository.apache.org/#stagingRepositories
[2] https://imgur.com/a/w4az7pD




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

Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.
Carlos,

I'm pretty sure that part of the "conventional process" you want to try requires filling the staging repo from a local machine.  I am suggesting that Chris and/or you do exactly that and document the steps and have someone else try those steps, so we can understand what that portion of the "conventional process" looks like.  Then it might be more clear what needs to be done to get it work on the CI server.

-Alex

On 3/25/20, 1:16 PM, "Carlos Rovira" <ca...@apache.org> wrote:

     Hi Alex,
    
    El mié., 25 mar. 2020 a las 20:37, Alex Harui (<ah...@adobe.com.invalid>)
    escribió:
    
    > But as I suggested in my previous post, it might help to first come up
    > with the set of maven commands required to reproduce (using your local
    > machine) the same number of files with the same names (other than the
    > version portion) that were in 0.9.6.
    >
    
    I think we're done what the process required. If there's other things we
    need to do, those are not in the current process, so I think is your
    responsibility to update that to make it work to prove that the process is
    valid. I think you can't expect Chris or I invest more time in the process
    when we are exposing all the problems behind it. I think we did our best,
    and now is the turn of others to try it, or as I already proposed lets us
    do a release with a more conventional process that does not try to do all
    that steps, that we think are not necessary, based on the rest of hundreds
    and hundreds of Apache projects.
    
    Hope you can understand it.
    
    Thanks
    
    -- 
    Carlos Rovira
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C467696ba4ee245a5f09108d7d0f957f1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207641651664238&amp;sdata=HdyvFUveH6nxvIkp%2FSyPyzfkfTQ6TJHTtN24GZC0vjs%3D&amp;reserved=0
    


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
 Hi Alex,

El mié., 25 mar. 2020 a las 20:37, Alex Harui (<ah...@adobe.com.invalid>)
escribió:

> But as I suggested in my previous post, it might help to first come up
> with the set of maven commands required to reproduce (using your local
> machine) the same number of files with the same names (other than the
> version portion) that were in 0.9.6.
>

I think we're done what the process required. If there's other things we
need to do, those are not in the current process, so I think is your
responsibility to update that to make it work to prove that the process is
valid. I think you can't expect Chris or I invest more time in the process
when we are exposing all the problems behind it. I think we did our best,
and now is the turn of others to try it, or as I already proposed lets us
do a release with a more conventional process that does not try to do all
that steps, that we think are not necessary, based on the rest of hundreds
and hundreds of Apache projects.

Hope you can understand it.

Thanks

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

Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.
IMO, reproducible binaries are useful for more than building artifacts on a remote machine.  I think enough folks agree that they produced plugins for Maven to help with reproducibility.  When I introduced it to Royale, it wasn't just to solve the CI build issue, it was to set us up for the future, in case signed binaries become required for installation for security/anti-malware reasons.

But as I suggested in my previous post, it might help to first come up with the set of maven commands required to reproduce (using your local machine) the same number of files with the same names (other than the version portion) that were in 0.9.6.
  
-Alex

On 3/25/20, 12:28 PM, "Christofer Dutz" <ch...@c-ware.de> wrote:

    Hi Alex,
    
    this is again under the premise that releases "must" be done on the CI server, which I would personally like to question.
    
    Royale is, as far as I know, the only project insisting on this. 
    
    If you build the release on your machine you don't have to check if this is really what you build on your machine.
    
    Chris
    
    
    
    Am 25.03.20, 19:23 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
    
        That has nothing to do with the Ant build of release artifacts.  That is just using Ant to run command line commands to download and verify Maven release artifacts.  I'm pretty sure you can just look at the steps and type them in manually at the command line and you'll get the same results.
        
        AFAICT, the problem is that the reproducible binaries generated by Maven aren't reproducible.    It could be an issue when the US and Europe have different daylight savings time settings.  When we saw it work, we were not at one of those transition points.  So maybe it is best to just wait until Sunday.  But it did work for me in the US and Piotr in EU.
        
        Proposals for better ways to have an RM verify artifacts built on a remote machine are welcome.  Testing reproducible binaries was the only way I could think of and implement.
        
        -Alex
        
        On 3/25/20, 11:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
        
            Hi Alex,
            
            after run CI Server 007 we get this email:
            
            From the royale-typedefs repo:
            1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7
            -DskipTests=true
            This will download the artifacts then unzip and compile the source artifact.
            2. Validate that the compiled artifacts match the downloaded artifacts.
            3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign
            -Drelease.version=0.9.7
            This will PGP sign the source ZIP and compiled JARs
            4. Then run ant -f releasesteps.xml Release_Step_007_Upload
            -Drelease.version=0.9.7
            This will upload the signed artifacts to Maven Release Staging. Do not
            "Close" the staging repository until the other repos have been added.
            
            This is what is failing from sub step 007-1, so as part of the step, I'm
            downloading with ant and building, signing and then uploading (Or steps
            should allow me to do that, but is failing)
            
            A part from that I don't think we really want a solution where of breaking
            steps event more. What we're requesting is remove steps.
            
            
            
            
            El mié., 25 mar. 2020 a las 18:54, Alex Harui (<ah...@adobe.com.invalid>)
            escribió:
            
            > I'm sorry, I must have missed something.  Where was Ant involved in any of
            > the problems reported so far?  AFAICT, it was all Maven plugins driving our
            > compiler and we couldn't get reproducible binaries.
            >
            > I suggested in one reply that Chris fills a staging repo using his local
            > machine just to make sure we know what Maven commands need to be run to
            > generate all of the Maven artifacts.   And that would validate the claim
            > that it is really doable in two or three steps.  A partial verification of
            > validity is to check that the same set of files was produced as in 0.9.6
            > (there might be some new SWCs though).
            >
            > Then someone else (maybe Carlos) would download all of the artifacts, run
            > the same steps, download the new artifacts and verify that the binary
            > match.  Then we can work on splitting those steps into chunks for the CI
            > server.
            >
            > -Alex
            >
            >
            > On 3/25/20, 10:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
            >
            >     We imposed ourselves a need to release building with two build systems.
            >     That's the biggest issue and that's a requirement of this PMC.
            >     That's what makes the need of the actual CI steps and the complex and
            >     intricate process.
            >
            >     For the rest of Apache a release is:
            >
            >     "For an *Apache* project, that means any publication outside the
            >     development community, defined as individuals actively participating in
            >     development or following the dev list. More narrowly, an official
            > *Apache
            >     release* is one which has been endorsed as an "act of the Foundation"
            > by a
            >     PMC."
            >
            >     That means that we can release with ANT, with Maven, or any other build
            >     systems as part of the process, and even try what we're doing of
            > trying to
            >     build with n build systems and try to check all is ok with the
            > artifacts
            >     generated by all that build systems and check all of them...but if
            > that's
            >     what we want, I personally will left this wagon, and wish you the best
            > of
            >     lucks in the process.
            >
            >     Chris and I proposed to just use Maven *for release* (so please, I
            > expect
            >     no body starts to say we are throwing away ANT from the project for
            >     building, please....we are just discussing release here).
            >
            >     What do you think about to try to release just with Maven? If can do
            > in the
            >     next day or two and get the release published...will that work for
            > you? I
            >     think we don't need anything more, and I'm sure our users will be
            > happy too.
            >
            >     And yes, people wanting then to build with Ant or with Maven will be
            > able
            >     to do so... :-)
            >
            >     Thanks
            >
            >     Carlos
            >
            >
            >     [1]
            > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease-publishing.html&amp;data=02%7C01%7Caharui%40adobe.com%7C2686c84c4497421753d408d7d0f2bc4c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207613278446831&amp;sdata=gkyY1LLl6N77RV7aUCPibF355zPc158YXa4xnXogDvk%3D&amp;reserved=0
            >
            >
            >
            >     El mié., 25 mar. 2020 a las 17:46, Christofer Dutz (<
            >     christofer.dutz@c-ware.de>) escribió:
            >
            >     > Hi Yiashay,
            >     >
            >     > I agree ... but I didn't create Maven ... haven't even provided a
            > single
            >     > PR to it ;-)
            >     > I think my only noticeable contribution was that they changed their
            >     > website to forbid the usage of "maven-{something}-plugin" to Apache
            > Maven
            >     > Core modules (It initially said Apache Maven Plugins which would have
            >     > applied for maven-flex-plugin and maven-plc4x-plugin)
            >     >
            >     > I think you should focus not on the process, but the bases a process
            >     > should cover.
            >     >
            >     > Focus on what you want to be provided or ensured by any process, no
            > matter
            >     > which tool it is based on.
            >     >
            >     > That's what I created the google doc for.
            >     >
            >     > If you decide to loosen the requirement on sticking 100% to the
            > existing
            >     > process I am more than willing to help.
            >     > However if you stick to the current process, it doesn't make any
            > sense for
            >     > me to do so.
            >     >
            >     > Looking forward to a productive discussion,
            >     >
            >     > Chris
            >     >
            >     >
            >     > Am 25.03.20, 17:36 schrieb "Yishay Weiss" <yi...@hotmail.com>:
            >     >
            >     >     I think the focus should be to agree on the requirements.
            > Whether an
            >     > RM uses the tool created by Chris or Alex can be a matter of choice.
            >     >
            >     >     From: Carlos Rovira<ma...@apache.org>
            >     >     Sent: Wednesday, March 25, 2020 5:18 PM
            >     >     To: Apache Royale Development<ma...@royale.apache.org>
            >     >     Subject: Re: Releasing: Finally giving up
            >     >
            >     >     Hi,
            >     >
            >     >     first of all, many thanks for all the time invested by Chris this
            >     > days. We
            >     >     almost didn't have any normal life this latest 2'5 days, but as
            > well
            >     > many
            >     >     other work (spliced in many hours in the several previous days)
            > was
            >     >     prepared to start this release, so for a person out side this
            > project,
            >     > I
            >     >     think we all should thanks a lot his dedications. The good
            > output is
            >     > that
            >     >     process was streamlined, removing unneeded params to enter and
            > fixing
            >     > many
            >     >     bugs over the place. That only can be performed by a good
            > specialist in
            >     >     build systems like Chris, I just could be a companion to execute
            > steps
            >     > and
            >     >     try to be trained in the process.
            >     >
            >     >     About me: I must to say that I tried hard to make this work, but
            > I must
            >     >     assume I don't have the skills to do it (what is normal, since
            > if an
            >     > expert
            >     >     in build stuff like Chris can't do it, I don't think any other
            > one
            >     > could do
            >     >     it, and less me). The good point is that I know I have a great a
            > deep
            >     >     knowledge about the overall process, and while in November I
            > could
            >     >     envision, something of what I could see this days, now I have a
            > clear
            >     >     knowledge of all of it (taking into account that we just go
            > through
            >     >     compiler and typedefs and not framework, that could be, due to
            > size, a
            >     > much
            >     >     bigger challenge...)
            >     >
            >     >     About the process: I must say that the initial intention was so
            > good,
            >     > and I
            >     >     think we all want the premise offered thanks to Alex. The
            > reality I
            >     > think
            >     >     is defeating the premise, and we should all see the reality with
            > clear
            >     >     sight and without worrying about egos but just looking and what
            > the
            >     > project
            >     >     need.
            >     >
            >     >     Since the CI process involves so many steps, manual commands in
            > CI
            >     > steps,
            >     >     and...manual commands in local machine. One of the most annoying
            >     > things is
            >     >     the CI server hanging lots of time (the Java agent exits and that
            >     > means you
            >     >     must reboot in order the system working all again without
            > problems).
            >     > The
            >     >     final problem is that you as a RM will fail some times in doing
            > what
            >     > the
            >     >     process needs (indicated in emails), and although you are
            > trained a
            >     > lot in
            >     >     how to do the project you will found stuck in some situations
            > where you
            >     >     simple don't know what to do.
            >     >
            >     >     (For example I forgot or did a bad step that makes me rollover
            > things
            >     > in
            >     >     succeed steps, so I had to roll back versions in the compiler,
            > but
            >     > since I
            >     >     was doing a tools release too, I didn't have into account that I
            > need
            >     > to
            >     >     roll back versions in tools too. It's clear as Chris notice
            > that, but
            >     > not
            >     >     for me at all. So we all should know with this example that the
            >     > process is
            >     >     not automatic at all. If just involve 2-3 steps, that would be
            >     > manageable,
            >     >     but we are talking of 13 steps with 32 manual steps (until step
            > 7),
            >     > plus
            >     >     maybe other 30 or so commands until step 13?)...hope you
            > understand the
            >     >     challenge here and that is nothing easy for any of us.
            >     >
            >     >     What I mean, and my advice, from someone that loves this project
            > and
            >     > want
            >     >     it to make it shine: We should try to simple focus in what's
            > important.
            >     >     Chris is offering a way that ensures release done simple and
            > easily. My
            >     >     take is that we can't afford to go this way more time, since the
            >     > project
            >     >     will see his existence threatened. We're here many years here,
            > and this
            >     >     actual problem is a big one. It's clear that we have a problem
            > if we
            >     > can
            >     >     release every month (or two month) with a process that is easy
            > for
            >     > everyone
            >     >     and requires not a great training to do so, and will require
            > some few
            >     >     commands and operations to be done. We simply can't release, and
            > we can
            >     >     rely in a process that is so fragile, to make every change we do
            > in the
            >     >     future will break it.
            >     >
            >     >     The fact is that we didn't get so many people jumping to Royale
            > and the
            >     >     ones with an eye on this project can finally gone if we continue
            >     > trying to
            >     >     force things that we don't need. We can release just with maven
            > in few
            >     >     steps, that's a fact, and we don't really need to make things in
            > the
            >     > actual
            >     >     way. If we do is because we're forcing it, but nobody cares, and
            > my
            >     > vision
            >     >     is that will cost the project.
            >     >
            >     >     We simplify the build Maven process to make it more reliable,
            > that
            >     > break
            >     >     the release process in November. The build process has priority
            > over
            >     > the
            >     >     release process, since lots of users depend on them (royale
            > devs, and
            >     >     users). The release process is important in the project context
            > to
            >     > offer
            >     >     the bits to the public as a tag or point in time.
            >     >
            >     >     We simply can't put the release process to the service of the
            > build
            >     > process
            >     >     and make all of that stop in time to not break a fragile release
            >     > process.
            >     >     That's not an option for an open source project. The release
            > process
            >     > is at
            >     >     the service of the rest (people, builds, code....)
            >     >
            >     >     I'd want people here to rethink all of this since:
            >     >
            >     >
            >     >        - We can't afford this project not to release easily monthly
            > (or
            >     > every 2
            >     >        months) for anyone here (and I mean all people here that
            > wants to
            >     > be an RM).
            >     >        - We can't afford so many hours invested to release, or to
            > maintain
            >     > a
            >     >        process that is very, very, very difficult to operate,
            > fragile and
            >     > easy to
            >     >        break.
            >     >
            >     >
            >     >     The motivations are:
            >     >
            >     >
            >     >        1. Although the process was designed and done with very good
            >     > intentions,
            >     >        the final product does not match the premise. "To make the
            > Release
            >     > process
            >     >        affordable and reliable for each RM"
            >     >        2. The CI server steps needs you to work on you local
            > machine, what
            >     >        defeats the premise to work just in the CI server.
            >     >        3. The actual process involve 13 steps instead of something
            > more
            >     >        manageable like 2-3
            >     >        4. The actual process involve many manual commands in the CI
            > server
            >     >        splitter through the 13 steps (1 to 5 commands for each step
            >     > depending on
            >     >        the step)
            >     >        5. The actual process involve many manual commands in your
            > local
            >     > machine
            >     >        splittled every 3 steps. So you need to use your local
            > machine what
            >     > defeats
            >     >        entirely the CI steps to not need the RM to configure his
            > machine.
            >     > This
            >     >        happens in steps 3 and 7 (and fo sure later in frameworks
            > part).
            >     >        6. The CI server use to hang the Jenkins java agent process
            > that
            >     >        involves a reboot, what make all the process highly
            > cumbersome. You
            >     > can
            >     >        easily get to reboot CI server 1-2 times while doing the
            > first 3
            >     > steps.
            >     >        7. If you fail in some step (because you simply fail since
            > you're
            >     > human,
            >     >        or the hangs and things happening make you loose the track of
            > what
            >     > you're
            >     >        doing and make something that provoke the fail) you need to
            >     > rollback, and
            >     >        know how to operate to restore al the process, crossing
            > fingers to
            >     > expect
            >     >        all goes well, rolling back versions, removing release branch,
            >     > removing
            >     >        tags,...)
            >     >        8. In the end, If you finally get all the process to work,
            > since is
            >     >        very, very fragile, is very possible that some updates in the
            >     > future make
            >     >        it fail again, and the fix will required more and more hours
            > of
            >     >        experimented people, patience, and testing.
            >     >
            >     >     About time. For people trained in the process, (and I think I
            > get very
            >     >     trained this days). Steps 1 to 6-7 is about 1h and 30' to 2h. I
            > think
            >     >     getting to step 13 and taking into account that framework is
            > much more
            >     > code
            >     >     and time to build, I expect the global process is about 2h or
            > maybe
            >     > more.
            >     >     So we are talking about 3'5 to 4h, of all this complicated
            > process with
            >     >     lots of opportunities to fail in some of the ways already
            > commented.
            >     >
            >     >     We have the opportunity now: Chris wanted to use the project for
            > PCL4X
            >     > to
            >     >     build IoT apps. I think that's a huge opportunity for Royale.
            > He's
            >     > giving
            >     >     up to use whatever other frontend tech (React, Angular, Vue,...).
            >     >
            >     >     So all this is making Royale to continue moving backwards
            > instead to
            >     >     conquer new positions. I have clear that this is not the way to
            > go,
            >     > and if
            >     >     the rest of the team wants to continue forcing all of this. I
            > just can
            >     > do
            >     >     anything but start thinking in other options, a fork or
            > something that
            >     >     ensure we are not loosing more for the years to come.
            >     >
            >     >     I still hope all of you try to think well on all of this. Remove
            > egos,
            >     >     since is not about you and me, is about just Apache Royale, and
            > nobody
            >     > out
            >     >     there cares who or what did this or that. Is just a matter of
            > what we
            >     > want
            >     >     for Royale, since people will just see what the project can do
            > for him.
            >     >
            >     >     Hope this long email could make you think, and hope you all will
            >     > comment to
            >     >     have clear our positions and have clear what we can expect in
            > this
            >     >     problematic releasing problem, since is what will make us get
            > more
            >     > traction
            >     >     or in reverse, end loosing more users and maybe die in the way.
            >     >
            >     >     Thanks
            >     >
            >     >     Carlos
            >     >
            >     >
            >     >
            >     >
            >     >
            >     >
            >     >
            >     >
            >     >
            >     >     El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
            >     >     christofer.dutz@c-ware.de>) escribió:
            >     >
            >     >     > Hi all,
            >     >     >
            >     >     > after 3-4 days of some times 10-16 hours of working on getting
            > the
            >     >     > “process” running, I’m finally giving up.
            >     >     > We managed to fix a lot of issues in the way the steps were
            > setup and
            >     >     > managed to get to step 7 however there’s no getting past that.
            >     >     >
            >     >     > The problem are the reproducible builds.
            >     >     >
            >     >     > While for the java part I think we have all bases covered,
            > however I
            >     > can’t
            >     >     > see however how I can fix the compiler to actually produce
            >     > reproducible
            >     >     > builds.
            >     >     >
            >     >     > We are passing in the timestamp (slightly different format,
            > however
            >     > still
            >     >     > correct as we also adjusted the format-string). When building
            >     > locally, the
            >     >     > timestamp is exactly as the timestamp string tells the
            > compiler. On
            >     > the CI
            >     >     > however there’s this 60 minute offset. I have explicitly set
            > the
            >     > time-zone
            >     >     > wherever I found time-zone relevant code to UTC (Which is the
            >     > general best
            >     >     > practice for date stuff). However the offset didn’t change. So
            > I am
            >     >     > completely out of ideas what could be causing this. If it
            > really is
            >     > the
            >     >     > Summertime in the US, well I don’t know how to fix it (perhaps
            > setup
            >     > a rule
            >     >     > to not release in this time).
            >     >     >
            >     >     > Besides that, there are still differences in the library SWF:
            >     >     >
            >     >     >   *   As I mentioned yesterday, the node typedef contains a
            > “net”
            >     > object
            >     >     > definition in the local build and a “http” one on the CI server
            >     > version.
            >     >     >   *   In other modules it’s simply the order of items
            > generated. I
            >     > guess
            >     >     > it’s a similar issue as the one I fixed in the build-tools,
            > but I
            >     > have no
            >     >     > idea how to fix it in the compiler
            >     >     >
            >     >     > So in the end I’m giving up … I think the “process” is now way
            > more
            >     > stable
            >     >     > than before, but it’s still a really fragile construct. Today
            > Greg,
            >     > Carlos
            >     >     > and I did it together via Zoom and still we had to re-do some
            > steps
            >     > because
            >     >     > one little preparation was missed.
            >     >     >
            >     >     > I would strongly doubt that the reproducible builds really
            > built
            >     > globally
            >     >     > reproducible builds in the past … perhaps it worked in a narrow
            >     > corridor of
            >     >     > time-zones and OS/Java versions (I did use java 1.8), but I
            > simply
            >     > can’t
            >     >     > believe it ever was 100% reproducible.
            >     >     >
            >     >     > So as long as this reproducibility is a requirement, I guess
            > we’re
            >     > done. I
            >     >     > do understand what it’s used for in this context, however I
            > think
            >     > it’s just
            >     >     > not working.
            >     >     >
            >     >     > The other option would be to simply release with maven, which
            > would
            >     > have
            >     >     > been a 1-2 hour experience for all modules.
            >     >     >
            >     >     > I do agree that if the steps work and all preconditions would
            > be
            >     > checked
            >     >     > (which they currently are not) it is very easy to break the
            >     > “process”. And
            >     >     > it involves running 13 jobs … but as far as I got it also the
            >     > execution of
            >     >     > 32 manual commands for everything till step 7
            >     >     > 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
            >     >     >
            >     >     > So as long as we’re forced to stick to this process … I guess
            >     > someone else
            >     >     > will have to do it.
            >     >     >
            >     >     > Please feel free to revert any changes I did in the last few
            > months.
            >     >     >
            >     >     > Signing off,
            >     >     > Chris
            >     >     >
            >     >     > PS: You really should make this ApacheRoyaleCI guy a committer
            >     > considering
            >     >     > the amount of emails he’s writing ;-)
            >     >     >
            >     >     >
            >     >     >
            >     >
            >     >     --
            >     >     Carlos Rovira
            >     >
            > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2686c84c4497421753d408d7d0f2bc4c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207613278446831&amp;sdata=NJkoMDYFaGyS0R69%2BKwrgSCJ44Lo0c34g9u2eOsizHs%3D&amp;reserved=0
            >     >
            >     >
            >     >
            >     >
            >
            >     --
            >     Carlos Rovira
            >
            > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2686c84c4497421753d408d7d0f2bc4c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207613278446831&amp;sdata=NJkoMDYFaGyS0R69%2BKwrgSCJ44Lo0c34g9u2eOsizHs%3D&amp;reserved=0
            >
            >
            >
            
            -- 
            Carlos Rovira
            https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C2686c84c4497421753d408d7d0f2bc4c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207613278446831&amp;sdata=NJkoMDYFaGyS0R69%2BKwrgSCJ44Lo0c34g9u2eOsizHs%3D&amp;reserved=0
            
        
        
    
    


Re: Releasing: Finally giving up

Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Alex,

this is again under the premise that releases "must" be done on the CI server, which I would personally like to question.

Royale is, as far as I know, the only project insisting on this. 

If you build the release on your machine you don't have to check if this is really what you build on your machine.

Chris



Am 25.03.20, 19:23 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:

    That has nothing to do with the Ant build of release artifacts.  That is just using Ant to run command line commands to download and verify Maven release artifacts.  I'm pretty sure you can just look at the steps and type them in manually at the command line and you'll get the same results.
    
    AFAICT, the problem is that the reproducible binaries generated by Maven aren't reproducible.    It could be an issue when the US and Europe have different daylight savings time settings.  When we saw it work, we were not at one of those transition points.  So maybe it is best to just wait until Sunday.  But it did work for me in the US and Piotr in EU.
    
    Proposals for better ways to have an RM verify artifacts built on a remote machine are welcome.  Testing reproducible binaries was the only way I could think of and implement.
    
    -Alex
    
    On 3/25/20, 11:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
    
        Hi Alex,
        
        after run CI Server 007 we get this email:
        
        From the royale-typedefs repo:
        1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7
        -DskipTests=true
        This will download the artifacts then unzip and compile the source artifact.
        2. Validate that the compiled artifacts match the downloaded artifacts.
        3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign
        -Drelease.version=0.9.7
        This will PGP sign the source ZIP and compiled JARs
        4. Then run ant -f releasesteps.xml Release_Step_007_Upload
        -Drelease.version=0.9.7
        This will upload the signed artifacts to Maven Release Staging. Do not
        "Close" the staging repository until the other repos have been added.
        
        This is what is failing from sub step 007-1, so as part of the step, I'm
        downloading with ant and building, signing and then uploading (Or steps
        should allow me to do that, but is failing)
        
        A part from that I don't think we really want a solution where of breaking
        steps event more. What we're requesting is remove steps.
        
        
        
        
        El mié., 25 mar. 2020 a las 18:54, Alex Harui (<ah...@adobe.com.invalid>)
        escribió:
        
        > I'm sorry, I must have missed something.  Where was Ant involved in any of
        > the problems reported so far?  AFAICT, it was all Maven plugins driving our
        > compiler and we couldn't get reproducible binaries.
        >
        > I suggested in one reply that Chris fills a staging repo using his local
        > machine just to make sure we know what Maven commands need to be run to
        > generate all of the Maven artifacts.   And that would validate the claim
        > that it is really doable in two or three steps.  A partial verification of
        > validity is to check that the same set of files was produced as in 0.9.6
        > (there might be some new SWCs though).
        >
        > Then someone else (maybe Carlos) would download all of the artifacts, run
        > the same steps, download the new artifacts and verify that the binary
        > match.  Then we can work on splitting those steps into chunks for the CI
        > server.
        >
        > -Alex
        >
        >
        > On 3/25/20, 10:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
        >
        >     We imposed ourselves a need to release building with two build systems.
        >     That's the biggest issue and that's a requirement of this PMC.
        >     That's what makes the need of the actual CI steps and the complex and
        >     intricate process.
        >
        >     For the rest of Apache a release is:
        >
        >     "For an *Apache* project, that means any publication outside the
        >     development community, defined as individuals actively participating in
        >     development or following the dev list. More narrowly, an official
        > *Apache
        >     release* is one which has been endorsed as an "act of the Foundation"
        > by a
        >     PMC."
        >
        >     That means that we can release with ANT, with Maven, or any other build
        >     systems as part of the process, and even try what we're doing of
        > trying to
        >     build with n build systems and try to check all is ok with the
        > artifacts
        >     generated by all that build systems and check all of them...but if
        > that's
        >     what we want, I personally will left this wagon, and wish you the best
        > of
        >     lucks in the process.
        >
        >     Chris and I proposed to just use Maven *for release* (so please, I
        > expect
        >     no body starts to say we are throwing away ANT from the project for
        >     building, please....we are just discussing release here).
        >
        >     What do you think about to try to release just with Maven? If can do
        > in the
        >     next day or two and get the release published...will that work for
        > you? I
        >     think we don't need anything more, and I'm sure our users will be
        > happy too.
        >
        >     And yes, people wanting then to build with Ant or with Maven will be
        > able
        >     to do so... :-)
        >
        >     Thanks
        >
        >     Carlos
        >
        >
        >     [1]
        > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease-publishing.html&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=dsxwqItfcgSIUYZMYzgMziBunHmiBgubwQfiHAsaovA%3D&amp;reserved=0
        >
        >
        >
        >     El mié., 25 mar. 2020 a las 17:46, Christofer Dutz (<
        >     christofer.dutz@c-ware.de>) escribió:
        >
        >     > Hi Yiashay,
        >     >
        >     > I agree ... but I didn't create Maven ... haven't even provided a
        > single
        >     > PR to it ;-)
        >     > I think my only noticeable contribution was that they changed their
        >     > website to forbid the usage of "maven-{something}-plugin" to Apache
        > Maven
        >     > Core modules (It initially said Apache Maven Plugins which would have
        >     > applied for maven-flex-plugin and maven-plc4x-plugin)
        >     >
        >     > I think you should focus not on the process, but the bases a process
        >     > should cover.
        >     >
        >     > Focus on what you want to be provided or ensured by any process, no
        > matter
        >     > which tool it is based on.
        >     >
        >     > That's what I created the google doc for.
        >     >
        >     > If you decide to loosen the requirement on sticking 100% to the
        > existing
        >     > process I am more than willing to help.
        >     > However if you stick to the current process, it doesn't make any
        > sense for
        >     > me to do so.
        >     >
        >     > Looking forward to a productive discussion,
        >     >
        >     > Chris
        >     >
        >     >
        >     > Am 25.03.20, 17:36 schrieb "Yishay Weiss" <yi...@hotmail.com>:
        >     >
        >     >     I think the focus should be to agree on the requirements.
        > Whether an
        >     > RM uses the tool created by Chris or Alex can be a matter of choice.
        >     >
        >     >     From: Carlos Rovira<ma...@apache.org>
        >     >     Sent: Wednesday, March 25, 2020 5:18 PM
        >     >     To: Apache Royale Development<ma...@royale.apache.org>
        >     >     Subject: Re: Releasing: Finally giving up
        >     >
        >     >     Hi,
        >     >
        >     >     first of all, many thanks for all the time invested by Chris this
        >     > days. We
        >     >     almost didn't have any normal life this latest 2'5 days, but as
        > well
        >     > many
        >     >     other work (spliced in many hours in the several previous days)
        > was
        >     >     prepared to start this release, so for a person out side this
        > project,
        >     > I
        >     >     think we all should thanks a lot his dedications. The good
        > output is
        >     > that
        >     >     process was streamlined, removing unneeded params to enter and
        > fixing
        >     > many
        >     >     bugs over the place. That only can be performed by a good
        > specialist in
        >     >     build systems like Chris, I just could be a companion to execute
        > steps
        >     > and
        >     >     try to be trained in the process.
        >     >
        >     >     About me: I must to say that I tried hard to make this work, but
        > I must
        >     >     assume I don't have the skills to do it (what is normal, since
        > if an
        >     > expert
        >     >     in build stuff like Chris can't do it, I don't think any other
        > one
        >     > could do
        >     >     it, and less me). The good point is that I know I have a great a
        > deep
        >     >     knowledge about the overall process, and while in November I
        > could
        >     >     envision, something of what I could see this days, now I have a
        > clear
        >     >     knowledge of all of it (taking into account that we just go
        > through
        >     >     compiler and typedefs and not framework, that could be, due to
        > size, a
        >     > much
        >     >     bigger challenge...)
        >     >
        >     >     About the process: I must say that the initial intention was so
        > good,
        >     > and I
        >     >     think we all want the premise offered thanks to Alex. The
        > reality I
        >     > think
        >     >     is defeating the premise, and we should all see the reality with
        > clear
        >     >     sight and without worrying about egos but just looking and what
        > the
        >     > project
        >     >     need.
        >     >
        >     >     Since the CI process involves so many steps, manual commands in
        > CI
        >     > steps,
        >     >     and...manual commands in local machine. One of the most annoying
        >     > things is
        >     >     the CI server hanging lots of time (the Java agent exits and that
        >     > means you
        >     >     must reboot in order the system working all again without
        > problems).
        >     > The
        >     >     final problem is that you as a RM will fail some times in doing
        > what
        >     > the
        >     >     process needs (indicated in emails), and although you are
        > trained a
        >     > lot in
        >     >     how to do the project you will found stuck in some situations
        > where you
        >     >     simple don't know what to do.
        >     >
        >     >     (For example I forgot or did a bad step that makes me rollover
        > things
        >     > in
        >     >     succeed steps, so I had to roll back versions in the compiler,
        > but
        >     > since I
        >     >     was doing a tools release too, I didn't have into account that I
        > need
        >     > to
        >     >     roll back versions in tools too. It's clear as Chris notice
        > that, but
        >     > not
        >     >     for me at all. So we all should know with this example that the
        >     > process is
        >     >     not automatic at all. If just involve 2-3 steps, that would be
        >     > manageable,
        >     >     but we are talking of 13 steps with 32 manual steps (until step
        > 7),
        >     > plus
        >     >     maybe other 30 or so commands until step 13?)...hope you
        > understand the
        >     >     challenge here and that is nothing easy for any of us.
        >     >
        >     >     What I mean, and my advice, from someone that loves this project
        > and
        >     > want
        >     >     it to make it shine: We should try to simple focus in what's
        > important.
        >     >     Chris is offering a way that ensures release done simple and
        > easily. My
        >     >     take is that we can't afford to go this way more time, since the
        >     > project
        >     >     will see his existence threatened. We're here many years here,
        > and this
        >     >     actual problem is a big one. It's clear that we have a problem
        > if we
        >     > can
        >     >     release every month (or two month) with a process that is easy
        > for
        >     > everyone
        >     >     and requires not a great training to do so, and will require
        > some few
        >     >     commands and operations to be done. We simply can't release, and
        > we can
        >     >     rely in a process that is so fragile, to make every change we do
        > in the
        >     >     future will break it.
        >     >
        >     >     The fact is that we didn't get so many people jumping to Royale
        > and the
        >     >     ones with an eye on this project can finally gone if we continue
        >     > trying to
        >     >     force things that we don't need. We can release just with maven
        > in few
        >     >     steps, that's a fact, and we don't really need to make things in
        > the
        >     > actual
        >     >     way. If we do is because we're forcing it, but nobody cares, and
        > my
        >     > vision
        >     >     is that will cost the project.
        >     >
        >     >     We simplify the build Maven process to make it more reliable,
        > that
        >     > break
        >     >     the release process in November. The build process has priority
        > over
        >     > the
        >     >     release process, since lots of users depend on them (royale
        > devs, and
        >     >     users). The release process is important in the project context
        > to
        >     > offer
        >     >     the bits to the public as a tag or point in time.
        >     >
        >     >     We simply can't put the release process to the service of the
        > build
        >     > process
        >     >     and make all of that stop in time to not break a fragile release
        >     > process.
        >     >     That's not an option for an open source project. The release
        > process
        >     > is at
        >     >     the service of the rest (people, builds, code....)
        >     >
        >     >     I'd want people here to rethink all of this since:
        >     >
        >     >
        >     >        - We can't afford this project not to release easily monthly
        > (or
        >     > every 2
        >     >        months) for anyone here (and I mean all people here that
        > wants to
        >     > be an RM).
        >     >        - We can't afford so many hours invested to release, or to
        > maintain
        >     > a
        >     >        process that is very, very, very difficult to operate,
        > fragile and
        >     > easy to
        >     >        break.
        >     >
        >     >
        >     >     The motivations are:
        >     >
        >     >
        >     >        1. Although the process was designed and done with very good
        >     > intentions,
        >     >        the final product does not match the premise. "To make the
        > Release
        >     > process
        >     >        affordable and reliable for each RM"
        >     >        2. The CI server steps needs you to work on you local
        > machine, what
        >     >        defeats the premise to work just in the CI server.
        >     >        3. The actual process involve 13 steps instead of something
        > more
        >     >        manageable like 2-3
        >     >        4. The actual process involve many manual commands in the CI
        > server
        >     >        splitter through the 13 steps (1 to 5 commands for each step
        >     > depending on
        >     >        the step)
        >     >        5. The actual process involve many manual commands in your
        > local
        >     > machine
        >     >        splittled every 3 steps. So you need to use your local
        > machine what
        >     > defeats
        >     >        entirely the CI steps to not need the RM to configure his
        > machine.
        >     > This
        >     >        happens in steps 3 and 7 (and fo sure later in frameworks
        > part).
        >     >        6. The CI server use to hang the Jenkins java agent process
        > that
        >     >        involves a reboot, what make all the process highly
        > cumbersome. You
        >     > can
        >     >        easily get to reboot CI server 1-2 times while doing the
        > first 3
        >     > steps.
        >     >        7. If you fail in some step (because you simply fail since
        > you're
        >     > human,
        >     >        or the hangs and things happening make you loose the track of
        > what
        >     > you're
        >     >        doing and make something that provoke the fail) you need to
        >     > rollback, and
        >     >        know how to operate to restore al the process, crossing
        > fingers to
        >     > expect
        >     >        all goes well, rolling back versions, removing release branch,
        >     > removing
        >     >        tags,...)
        >     >        8. In the end, If you finally get all the process to work,
        > since is
        >     >        very, very fragile, is very possible that some updates in the
        >     > future make
        >     >        it fail again, and the fix will required more and more hours
        > of
        >     >        experimented people, patience, and testing.
        >     >
        >     >     About time. For people trained in the process, (and I think I
        > get very
        >     >     trained this days). Steps 1 to 6-7 is about 1h and 30' to 2h. I
        > think
        >     >     getting to step 13 and taking into account that framework is
        > much more
        >     > code
        >     >     and time to build, I expect the global process is about 2h or
        > maybe
        >     > more.
        >     >     So we are talking about 3'5 to 4h, of all this complicated
        > process with
        >     >     lots of opportunities to fail in some of the ways already
        > commented.
        >     >
        >     >     We have the opportunity now: Chris wanted to use the project for
        > PCL4X
        >     > to
        >     >     build IoT apps. I think that's a huge opportunity for Royale.
        > He's
        >     > giving
        >     >     up to use whatever other frontend tech (React, Angular, Vue,...).
        >     >
        >     >     So all this is making Royale to continue moving backwards
        > instead to
        >     >     conquer new positions. I have clear that this is not the way to
        > go,
        >     > and if
        >     >     the rest of the team wants to continue forcing all of this. I
        > just can
        >     > do
        >     >     anything but start thinking in other options, a fork or
        > something that
        >     >     ensure we are not loosing more for the years to come.
        >     >
        >     >     I still hope all of you try to think well on all of this. Remove
        > egos,
        >     >     since is not about you and me, is about just Apache Royale, and
        > nobody
        >     > out
        >     >     there cares who or what did this or that. Is just a matter of
        > what we
        >     > want
        >     >     for Royale, since people will just see what the project can do
        > for him.
        >     >
        >     >     Hope this long email could make you think, and hope you all will
        >     > comment to
        >     >     have clear our positions and have clear what we can expect in
        > this
        >     >     problematic releasing problem, since is what will make us get
        > more
        >     > traction
        >     >     or in reverse, end loosing more users and maybe die in the way.
        >     >
        >     >     Thanks
        >     >
        >     >     Carlos
        >     >
        >     >
        >     >
        >     >
        >     >
        >     >
        >     >
        >     >
        >     >
        >     >     El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
        >     >     christofer.dutz@c-ware.de>) escribió:
        >     >
        >     >     > Hi all,
        >     >     >
        >     >     > after 3-4 days of some times 10-16 hours of working on getting
        > the
        >     >     > “process” running, I’m finally giving up.
        >     >     > We managed to fix a lot of issues in the way the steps were
        > setup and
        >     >     > managed to get to step 7 however there’s no getting past that.
        >     >     >
        >     >     > The problem are the reproducible builds.
        >     >     >
        >     >     > While for the java part I think we have all bases covered,
        > however I
        >     > can’t
        >     >     > see however how I can fix the compiler to actually produce
        >     > reproducible
        >     >     > builds.
        >     >     >
        >     >     > We are passing in the timestamp (slightly different format,
        > however
        >     > still
        >     >     > correct as we also adjusted the format-string). When building
        >     > locally, the
        >     >     > timestamp is exactly as the timestamp string tells the
        > compiler. On
        >     > the CI
        >     >     > however there’s this 60 minute offset. I have explicitly set
        > the
        >     > time-zone
        >     >     > wherever I found time-zone relevant code to UTC (Which is the
        >     > general best
        >     >     > practice for date stuff). However the offset didn’t change. So
        > I am
        >     >     > completely out of ideas what could be causing this. If it
        > really is
        >     > the
        >     >     > Summertime in the US, well I don’t know how to fix it (perhaps
        > setup
        >     > a rule
        >     >     > to not release in this time).
        >     >     >
        >     >     > Besides that, there are still differences in the library SWF:
        >     >     >
        >     >     >   *   As I mentioned yesterday, the node typedef contains a
        > “net”
        >     > object
        >     >     > definition in the local build and a “http” one on the CI server
        >     > version.
        >     >     >   *   In other modules it’s simply the order of items
        > generated. I
        >     > guess
        >     >     > it’s a similar issue as the one I fixed in the build-tools,
        > but I
        >     > have no
        >     >     > idea how to fix it in the compiler
        >     >     >
        >     >     > So in the end I’m giving up … I think the “process” is now way
        > more
        >     > stable
        >     >     > than before, but it’s still a really fragile construct. Today
        > Greg,
        >     > Carlos
        >     >     > and I did it together via Zoom and still we had to re-do some
        > steps
        >     > because
        >     >     > one little preparation was missed.
        >     >     >
        >     >     > I would strongly doubt that the reproducible builds really
        > built
        >     > globally
        >     >     > reproducible builds in the past … perhaps it worked in a narrow
        >     > corridor of
        >     >     > time-zones and OS/Java versions (I did use java 1.8), but I
        > simply
        >     > can’t
        >     >     > believe it ever was 100% reproducible.
        >     >     >
        >     >     > So as long as this reproducibility is a requirement, I guess
        > we’re
        >     > done. I
        >     >     > do understand what it’s used for in this context, however I
        > think
        >     > it’s just
        >     >     > not working.
        >     >     >
        >     >     > The other option would be to simply release with maven, which
        > would
        >     > have
        >     >     > been a 1-2 hour experience for all modules.
        >     >     >
        >     >     > I do agree that if the steps work and all preconditions would
        > be
        >     > checked
        >     >     > (which they currently are not) it is very easy to break the
        >     > “process”. And
        >     >     > it involves running 13 jobs … but as far as I got it also the
        >     > execution of
        >     >     > 32 manual commands for everything till step 7
        >     >     > 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
        >     >     >
        >     >     > So as long as we’re forced to stick to this process … I guess
        >     > someone else
        >     >     > will have to do it.
        >     >     >
        >     >     > Please feel free to revert any changes I did in the last few
        > months.
        >     >     >
        >     >     > Signing off,
        >     >     > Chris
        >     >     >
        >     >     > PS: You really should make this ApacheRoyaleCI guy a committer
        >     > considering
        >     >     > the amount of emails he’s writing ;-)
        >     >     >
        >     >     >
        >     >     >
        >     >
        >     >     --
        >     >     Carlos Rovira
        >     >
        > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=yfDv5ocD5wFYvpuHrY2OUyw0tUpc3NZzbzbkaBF35aI%3D&amp;reserved=0
        >     >
        >     >
        >     >
        >     >
        >
        >     --
        >     Carlos Rovira
        >
        > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=yfDv5ocD5wFYvpuHrY2OUyw0tUpc3NZzbzbkaBF35aI%3D&amp;reserved=0
        >
        >
        >
        
        -- 
        Carlos Rovira
        https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=yfDv5ocD5wFYvpuHrY2OUyw0tUpc3NZzbzbkaBF35aI%3D&amp;reserved=0
        
    
    


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi, Alex

El mié., 25 mar. 2020 a las 19:23, Alex Harui (<ah...@adobe.com.invalid>)
escribió:

> That has nothing to do with the Ant build of release artifacts.  That is
> just using Ant to run command line commands to download and verify Maven
> release artifacts.  I'm pretty sure you can just look at the steps and type
> them in manually at the command line and you'll get the same results.
>

As I said, this requested step from the CI Server failed for me, so I could
not sign and then upload. Is what we're trying to say.

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

Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.
Reproducible builds for Royale is certainly new.  There could be bugs in North vs South hemispheres.  Don't know.  Volunteers are welcome to improve this portion of our code.

I believe one (maybe the only one) of the challenges is to figure out how to choose a timestamp that can be used in the SWCs for at least those needing to reproduce the SWCs.  The ZipEntry used in the SWC does not contain a timezone so I think there are some challenges to that.

You can try building the SWCs using the timestamps used in the daily builds and see if you also see time skews and propose solutions.

-Alex 

On 3/25/20, 1:28 PM, "Greg Dove" <gr...@gmail.com> wrote:

     'It could be an issue when the US and Europe have different daylight
    savings time settings.....  When we saw it work, we were not at one of
    those transition points.'
    
    Southern hemisphere and northern hemisphere differences pivot by 2 hours
    through these transition gaps, which are typically 2 weeks or 1 week when
    the application or non-application of DST is aligned between the two
    countries being compared.
    For the majority of the year DST is not aligned. The end of each transition
    results in things being 2 hours different from whatever was 'normal'
    before.
    
    If the nature of this problem is as-described, which seems to require DST
    alignment, does that mean the timestamp issues might be present most of the
    time for someone south of the equator and perhaps only work in the
    'transitions' when DST 'settings' are briefly aligned?
    So far, I know this hasn't been a problem, with Royale having had no RM
    from southern climes, iirc. So I'm just asking mainly to clarify my
    understanding of the problem itself. If the answer is "I'm not sure, try it
    and see" I am not at that point yet :)
    
    If, however, there is something specific that I can investigate about
    timestamp issues, I am happy to try.
    
    
    On Thu, Mar 26, 2020 at 7:23 AM Alex Harui <ah...@adobe.com.invalid> wrote:
    
    > That has nothing to do with the Ant build of release artifacts.  That is
    > just using Ant to run command line commands to download and verify Maven
    > release artifacts.  I'm pretty sure you can just look at the steps and type
    > them in manually at the command line and you'll get the same results.
    >
    > AFAICT, the problem is that the reproducible binaries generated by Maven
    > aren't reproducible.    It could be an issue when the US and Europe have
    > different daylight savings time settings.  When we saw it work, we were not
    > at one of those transition points.  So maybe it is best to just wait until
    > Sunday.  But it did work for me in the US and Piotr in EU.
    >
    > Proposals for better ways to have an RM verify artifacts built on a remote
    > machine are welcome.  Testing reproducible binaries was the only way I
    > could think of and implement.
    >
    > -Alex
    >
    > On 3/25/20, 11:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
    >
    >     Hi Alex,
    >
    >     after run CI Server 007 we get this email:
    >
    >     From the royale-typedefs repo:
    >     1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7
    >     -DskipTests=true
    >     This will download the artifacts then unzip and compile the source
    > artifact.
    >     2. Validate that the compiled artifacts match the downloaded artifacts.
    >     3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign
    >     -Drelease.version=0.9.7
    >     This will PGP sign the source ZIP and compiled JARs
    >     4. Then run ant -f releasesteps.xml Release_Step_007_Upload
    >     -Drelease.version=0.9.7
    >     This will upload the signed artifacts to Maven Release Staging. Do not
    >     "Close" the staging repository until the other repos have been added.
    >
    >     This is what is failing from sub step 007-1, so as part of the step,
    > I'm
    >     downloading with ant and building, signing and then uploading (Or steps
    >     should allow me to do that, but is failing)
    >
    >     A part from that I don't think we really want a solution where of
    > breaking
    >     steps event more. What we're requesting is remove steps.
    >
    >
    >
    >
    >     El mié., 25 mar. 2020 a las 18:54, Alex Harui
    > (<ah...@adobe.com.invalid>)
    >     escribió:
    >
    >     > I'm sorry, I must have missed something.  Where was Ant involved in
    > any of
    >     > the problems reported so far?  AFAICT, it was all Maven plugins
    > driving our
    >     > compiler and we couldn't get reproducible binaries.
    >     >
    >     > I suggested in one reply that Chris fills a staging repo using his
    > local
    >     > machine just to make sure we know what Maven commands need to be run
    > to
    >     > generate all of the Maven artifacts.   And that would validate the
    > claim
    >     > that it is really doable in two or three steps.  A partial
    > verification of
    >     > validity is to check that the same set of files was produced as in
    > 0.9.6
    >     > (there might be some new SWCs though).
    >     >
    >     > Then someone else (maybe Carlos) would download all of the
    > artifacts, run
    >     > the same steps, download the new artifacts and verify that the binary
    >     > match.  Then we can work on splitting those steps into chunks for
    > the CI
    >     > server.
    >     >
    >     > -Alex
    >     >
    >     >
    >     > On 3/25/20, 10:13 AM, "Carlos Rovira" <ca...@apache.org>
    > wrote:
    >     >
    >     >     We imposed ourselves a need to release building with two build
    > systems.
    >     >     That's the biggest issue and that's a requirement of this PMC.
    >     >     That's what makes the need of the actual CI steps and the
    > complex and
    >     >     intricate process.
    >     >
    >     >     For the rest of Apache a release is:
    >     >
    >     >     "For an *Apache* project, that means any publication outside the
    >     >     development community, defined as individuals actively
    > participating in
    >     >     development or following the dev list. More narrowly, an official
    >     > *Apache
    >     >     release* is one which has been endorsed as an "act of the
    > Foundation"
    >     > by a
    >     >     PMC."
    >     >
    >     >     That means that we can release with ANT, with Maven, or any
    > other build
    >     >     systems as part of the process, and even try what we're doing of
    >     > trying to
    >     >     build with n build systems and try to check all is ok with the
    >     > artifacts
    >     >     generated by all that build systems and check all of them...but
    > if
    >     > that's
    >     >     what we want, I personally will left this wagon, and wish you
    > the best
    >     > of
    >     >     lucks in the process.
    >     >
    >     >     Chris and I proposed to just use Maven *for release* (so please,
    > I
    >     > expect
    >     >     no body starts to say we are throwing away ANT from the project
    > for
    >     >     building, please....we are just discussing release here).
    >     >
    >     >     What do you think about to try to release just with Maven? If
    > can do
    >     > in the
    >     >     next day or two and get the release published...will that work
    > for
    >     > you? I
    >     >     think we don't need anything more, and I'm sure our users will be
    >     > happy too.
    >     >
    >     >     And yes, people wanting then to build with Ant or with Maven
    > will be
    >     > able
    >     >     to do so... :-)
    >     >
    >     >     Thanks
    >     >
    >     >     Carlos
    >     >
    >     >
    >     >     [1]
    >     >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease-publishing.html&amp;data=02%7C01%7Caharui%40adobe.com%7Cb1c95c1197c14265c8f108d7d0fb1a60%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207649212793116&amp;sdata=opSfHujMlruvaYspE7k81C%2BVkQ%2BpetRQCU15%2Fl%2F9zzE%3D&amp;reserved=0
    >     >
    >     >
    >     >
    >     >     El mié., 25 mar. 2020 a las 17:46, Christofer Dutz (<
    >     >     christofer.dutz@c-ware.de>) escribió:
    >     >
    >     >     > Hi Yiashay,
    >     >     >
    >     >     > I agree ... but I didn't create Maven ... haven't even
    > provided a
    >     > single
    >     >     > PR to it ;-)
    >     >     > I think my only noticeable contribution was that they changed
    > their
    >     >     > website to forbid the usage of "maven-{something}-plugin" to
    > Apache
    >     > Maven
    >     >     > Core modules (It initially said Apache Maven Plugins which
    > would have
    >     >     > applied for maven-flex-plugin and maven-plc4x-plugin)
    >     >     >
    >     >     > I think you should focus not on the process, but the bases a
    > process
    >     >     > should cover.
    >     >     >
    >     >     > Focus on what you want to be provided or ensured by any
    > process, no
    >     > matter
    >     >     > which tool it is based on.
    >     >     >
    >     >     > That's what I created the google doc for.
    >     >     >
    >     >     > If you decide to loosen the requirement on sticking 100% to the
    >     > existing
    >     >     > process I am more than willing to help.
    >     >     > However if you stick to the current process, it doesn't make
    > any
    >     > sense for
    >     >     > me to do so.
    >     >     >
    >     >     > Looking forward to a productive discussion,
    >     >     >
    >     >     > Chris
    >     >     >
    >     >     >
    >     >     > Am 25.03.20, 17:36 schrieb "Yishay Weiss" <
    > yishayjobs@hotmail.com>:
    >     >     >
    >     >     >     I think the focus should be to agree on the requirements.
    >     > Whether an
    >     >     > RM uses the tool created by Chris or Alex can be a matter of
    > choice.
    >     >     >
    >     >     >     From: Carlos Rovira<ma...@apache.org>
    >     >     >     Sent: Wednesday, March 25, 2020 5:18 PM
    >     >     >     To: Apache Royale Development<mailto:dev@royale.apache.org
    > >
    >     >     >     Subject: Re: Releasing: Finally giving up
    >     >     >
    >     >     >     Hi,
    >     >     >
    >     >     >     first of all, many thanks for all the time invested by
    > Chris this
    >     >     > days. We
    >     >     >     almost didn't have any normal life this latest 2'5 days,
    > but as
    >     > well
    >     >     > many
    >     >     >     other work (spliced in many hours in the several previous
    > days)
    >     > was
    >     >     >     prepared to start this release, so for a person out side
    > this
    >     > project,
    >     >     > I
    >     >     >     think we all should thanks a lot his dedications. The good
    >     > output is
    >     >     > that
    >     >     >     process was streamlined, removing unneeded params to enter
    > and
    >     > fixing
    >     >     > many
    >     >     >     bugs over the place. That only can be performed by a good
    >     > specialist in
    >     >     >     build systems like Chris, I just could be a companion to
    > execute
    >     > steps
    >     >     > and
    >     >     >     try to be trained in the process.
    >     >     >
    >     >     >     About me: I must to say that I tried hard to make this
    > work, but
    >     > I must
    >     >     >     assume I don't have the skills to do it (what is normal,
    > since
    >     > if an
    >     >     > expert
    >     >     >     in build stuff like Chris can't do it, I don't think any
    > other
    >     > one
    >     >     > could do
    >     >     >     it, and less me). The good point is that I know I have a
    > great a
    >     > deep
    >     >     >     knowledge about the overall process, and while in November
    > I
    >     > could
    >     >     >     envision, something of what I could see this days, now I
    > have a
    >     > clear
    >     >     >     knowledge of all of it (taking into account that we just go
    >     > through
    >     >     >     compiler and typedefs and not framework, that could be,
    > due to
    >     > size, a
    >     >     > much
    >     >     >     bigger challenge...)
    >     >     >
    >     >     >     About the process: I must say that the initial intention
    > was so
    >     > good,
    >     >     > and I
    >     >     >     think we all want the premise offered thanks to Alex. The
    >     > reality I
    >     >     > think
    >     >     >     is defeating the premise, and we should all see the
    > reality with
    >     > clear
    >     >     >     sight and without worrying about egos but just looking and
    > what
    >     > the
    >     >     > project
    >     >     >     need.
    >     >     >
    >     >     >     Since the CI process involves so many steps, manual
    > commands in
    >     > CI
    >     >     > steps,
    >     >     >     and...manual commands in local machine. One of the most
    > annoying
    >     >     > things is
    >     >     >     the CI server hanging lots of time (the Java agent exits
    > and that
    >     >     > means you
    >     >     >     must reboot in order the system working all again without
    >     > problems).
    >     >     > The
    >     >     >     final problem is that you as a RM will fail some times in
    > doing
    >     > what
    >     >     > the
    >     >     >     process needs (indicated in emails), and although you are
    >     > trained a
    >     >     > lot in
    >     >     >     how to do the project you will found stuck in some
    > situations
    >     > where you
    >     >     >     simple don't know what to do.
    >     >     >
    >     >     >     (For example I forgot or did a bad step that makes me
    > rollover
    >     > things
    >     >     > in
    >     >     >     succeed steps, so I had to roll back versions in the
    > compiler,
    >     > but
    >     >     > since I
    >     >     >     was doing a tools release too, I didn't have into account
    > that I
    >     > need
    >     >     > to
    >     >     >     roll back versions in tools too. It's clear as Chris notice
    >     > that, but
    >     >     > not
    >     >     >     for me at all. So we all should know with this example
    > that the
    >     >     > process is
    >     >     >     not automatic at all. If just involve 2-3 steps, that
    > would be
    >     >     > manageable,
    >     >     >     but we are talking of 13 steps with 32 manual steps (until
    > step
    >     > 7),
    >     >     > plus
    >     >     >     maybe other 30 or so commands until step 13?)...hope you
    >     > understand the
    >     >     >     challenge here and that is nothing easy for any of us.
    >     >     >
    >     >     >     What I mean, and my advice, from someone that loves this
    > project
    >     > and
    >     >     > want
    >     >     >     it to make it shine: We should try to simple focus in
    > what's
    >     > important.
    >     >     >     Chris is offering a way that ensures release done simple
    > and
    >     > easily. My
    >     >     >     take is that we can't afford to go this way more time,
    > since the
    >     >     > project
    >     >     >     will see his existence threatened. We're here many years
    > here,
    >     > and this
    >     >     >     actual problem is a big one. It's clear that we have a
    > problem
    >     > if we
    >     >     > can
    >     >     >     release every month (or two month) with a process that is
    > easy
    >     > for
    >     >     > everyone
    >     >     >     and requires not a great training to do so, and will
    > require
    >     > some few
    >     >     >     commands and operations to be done. We simply can't
    > release, and
    >     > we can
    >     >     >     rely in a process that is so fragile, to make every change
    > we do
    >     > in the
    >     >     >     future will break it.
    >     >     >
    >     >     >     The fact is that we didn't get so many people jumping to
    > Royale
    >     > and the
    >     >     >     ones with an eye on this project can finally gone if we
    > continue
    >     >     > trying to
    >     >     >     force things that we don't need. We can release just with
    > maven
    >     > in few
    >     >     >     steps, that's a fact, and we don't really need to make
    > things in
    >     > the
    >     >     > actual
    >     >     >     way. If we do is because we're forcing it, but nobody
    > cares, and
    >     > my
    >     >     > vision
    >     >     >     is that will cost the project.
    >     >     >
    >     >     >     We simplify the build Maven process to make it more
    > reliable,
    >     > that
    >     >     > break
    >     >     >     the release process in November. The build process has
    > priority
    >     > over
    >     >     > the
    >     >     >     release process, since lots of users depend on them (royale
    >     > devs, and
    >     >     >     users). The release process is important in the project
    > context
    >     > to
    >     >     > offer
    >     >     >     the bits to the public as a tag or point in time.
    >     >     >
    >     >     >     We simply can't put the release process to the service of
    > the
    >     > build
    >     >     > process
    >     >     >     and make all of that stop in time to not break a fragile
    > release
    >     >     > process.
    >     >     >     That's not an option for an open source project. The
    > release
    >     > process
    >     >     > is at
    >     >     >     the service of the rest (people, builds, code....)
    >     >     >
    >     >     >     I'd want people here to rethink all of this since:
    >     >     >
    >     >     >
    >     >     >        - We can't afford this project not to release easily
    > monthly
    >     > (or
    >     >     > every 2
    >     >     >        months) for anyone here (and I mean all people here that
    >     > wants to
    >     >     > be an RM).
    >     >     >        - We can't afford so many hours invested to release, or
    > to
    >     > maintain
    >     >     > a
    >     >     >        process that is very, very, very difficult to operate,
    >     > fragile and
    >     >     > easy to
    >     >     >        break.
    >     >     >
    >     >     >
    >     >     >     The motivations are:
    >     >     >
    >     >     >
    >     >     >        1. Although the process was designed and done with very
    > good
    >     >     > intentions,
    >     >     >        the final product does not match the premise. "To make
    > the
    >     > Release
    >     >     > process
    >     >     >        affordable and reliable for each RM"
    >     >     >        2. The CI server steps needs you to work on you local
    >     > machine, what
    >     >     >        defeats the premise to work just in the CI server.
    >     >     >        3. The actual process involve 13 steps instead of
    > something
    >     > more
    >     >     >        manageable like 2-3
    >     >     >        4. The actual process involve many manual commands in
    > the CI
    >     > server
    >     >     >        splitter through the 13 steps (1 to 5 commands for each
    > step
    >     >     > depending on
    >     >     >        the step)
    >     >     >        5. The actual process involve many manual commands in
    > your
    >     > local
    >     >     > machine
    >     >     >        splittled every 3 steps. So you need to use your local
    >     > machine what
    >     >     > defeats
    >     >     >        entirely the CI steps to not need the RM to configure
    > his
    >     > machine.
    >     >     > This
    >     >     >        happens in steps 3 and 7 (and fo sure later in
    > frameworks
    >     > part).
    >     >     >        6. The CI server use to hang the Jenkins java agent
    > process
    >     > that
    >     >     >        involves a reboot, what make all the process highly
    >     > cumbersome. You
    >     >     > can
    >     >     >        easily get to reboot CI server 1-2 times while doing the
    >     > first 3
    >     >     > steps.
    >     >     >        7. If you fail in some step (because you simply fail
    > since
    >     > you're
    >     >     > human,
    >     >     >        or the hangs and things happening make you loose the
    > track of
    >     > what
    >     >     > you're
    >     >     >        doing and make something that provoke the fail) you
    > need to
    >     >     > rollback, and
    >     >     >        know how to operate to restore al the process, crossing
    >     > fingers to
    >     >     > expect
    >     >     >        all goes well, rolling back versions, removing release
    > branch,
    >     >     > removing
    >     >     >        tags,...)
    >     >     >        8. In the end, If you finally get all the process to
    > work,
    >     > since is
    >     >     >        very, very fragile, is very possible that some updates
    > in the
    >     >     > future make
    >     >     >        it fail again, and the fix will required more and more
    > hours
    >     > of
    >     >     >        experimented people, patience, and testing.
    >     >     >
    >     >     >     About time. For people trained in the process, (and I
    > think I
    >     > get very
    >     >     >     trained this days). Steps 1 to 6-7 is about 1h and 30' to
    > 2h. I
    >     > think
    >     >     >     getting to step 13 and taking into account that framework
    > is
    >     > much more
    >     >     > code
    >     >     >     and time to build, I expect the global process is about 2h
    > or
    >     > maybe
    >     >     > more.
    >     >     >     So we are talking about 3'5 to 4h, of all this complicated
    >     > process with
    >     >     >     lots of opportunities to fail in some of the ways already
    >     > commented.
    >     >     >
    >     >     >     We have the opportunity now: Chris wanted to use the
    > project for
    >     > PCL4X
    >     >     > to
    >     >     >     build IoT apps. I think that's a huge opportunity for
    > Royale.
    >     > He's
    >     >     > giving
    >     >     >     up to use whatever other frontend tech (React, Angular,
    > Vue,...).
    >     >     >
    >     >     >     So all this is making Royale to continue moving backwards
    >     > instead to
    >     >     >     conquer new positions. I have clear that this is not the
    > way to
    >     > go,
    >     >     > and if
    >     >     >     the rest of the team wants to continue forcing all of
    > this. I
    >     > just can
    >     >     > do
    >     >     >     anything but start thinking in other options, a fork or
    >     > something that
    >     >     >     ensure we are not loosing more for the years to come.
    >     >     >
    >     >     >     I still hope all of you try to think well on all of this.
    > Remove
    >     > egos,
    >     >     >     since is not about you and me, is about just Apache
    > Royale, and
    >     > nobody
    >     >     > out
    >     >     >     there cares who or what did this or that. Is just a matter
    > of
    >     > what we
    >     >     > want
    >     >     >     for Royale, since people will just see what the project
    > can do
    >     > for him.
    >     >     >
    >     >     >     Hope this long email could make you think, and hope you
    > all will
    >     >     > comment to
    >     >     >     have clear our positions and have clear what we can expect
    > in
    >     > this
    >     >     >     problematic releasing problem, since is what will make us
    > get
    >     > more
    >     >     > traction
    >     >     >     or in reverse, end loosing more users and maybe die in the
    > way.
    >     >     >
    >     >     >     Thanks
    >     >     >
    >     >     >     Carlos
    >     >     >
    >     >     >
    >     >     >
    >     >     >
    >     >     >
    >     >     >
    >     >     >
    >     >     >
    >     >     >
    >     >     >     El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
    >     >     >     christofer.dutz@c-ware.de>) escribió:
    >     >     >
    >     >     >     > Hi all,
    >     >     >     >
    >     >     >     > after 3-4 days of some times 10-16 hours of working on
    > getting
    >     > the
    >     >     >     > “process” running, I’m finally giving up.
    >     >     >     > We managed to fix a lot of issues in the way the steps
    > were
    >     > setup and
    >     >     >     > managed to get to step 7 however there’s no getting past
    > that.
    >     >     >     >
    >     >     >     > The problem are the reproducible builds.
    >     >     >     >
    >     >     >     > While for the java part I think we have all bases
    > covered,
    >     > however I
    >     >     > can’t
    >     >     >     > see however how I can fix the compiler to actually
    > produce
    >     >     > reproducible
    >     >     >     > builds.
    >     >     >     >
    >     >     >     > We are passing in the timestamp (slightly different
    > format,
    >     > however
    >     >     > still
    >     >     >     > correct as we also adjusted the format-string). When
    > building
    >     >     > locally, the
    >     >     >     > timestamp is exactly as the timestamp string tells the
    >     > compiler. On
    >     >     > the CI
    >     >     >     > however there’s this 60 minute offset. I have explicitly
    > set
    >     > the
    >     >     > time-zone
    >     >     >     > wherever I found time-zone relevant code to UTC (Which
    > is the
    >     >     > general best
    >     >     >     > practice for date stuff). However the offset didn’t
    > change. So
    >     > I am
    >     >     >     > completely out of ideas what could be causing this. If it
    >     > really is
    >     >     > the
    >     >     >     > Summertime in the US, well I don’t know how to fix it
    > (perhaps
    >     > setup
    >     >     > a rule
    >     >     >     > to not release in this time).
    >     >     >     >
    >     >     >     > Besides that, there are still differences in the library
    > SWF:
    >     >     >     >
    >     >     >     >   *   As I mentioned yesterday, the node typedef
    > contains a
    >     > “net”
    >     >     > object
    >     >     >     > definition in the local build and a “http” one on the CI
    > server
    >     >     > version.
    >     >     >     >   *   In other modules it’s simply the order of items
    >     > generated. I
    >     >     > guess
    >     >     >     > it’s a similar issue as the one I fixed in the
    > build-tools,
    >     > but I
    >     >     > have no
    >     >     >     > idea how to fix it in the compiler
    >     >     >     >
    >     >     >     > So in the end I’m giving up … I think the “process” is
    > now way
    >     > more
    >     >     > stable
    >     >     >     > than before, but it’s still a really fragile construct.
    > Today
    >     > Greg,
    >     >     > Carlos
    >     >     >     > and I did it together via Zoom and still we had to re-do
    > some
    >     > steps
    >     >     > because
    >     >     >     > one little preparation was missed.
    >     >     >     >
    >     >     >     > I would strongly doubt that the reproducible builds
    > really
    >     > built
    >     >     > globally
    >     >     >     > reproducible builds in the past … perhaps it worked in a
    > narrow
    >     >     > corridor of
    >     >     >     > time-zones and OS/Java versions (I did use java 1.8),
    > but I
    >     > simply
    >     >     > can’t
    >     >     >     > believe it ever was 100% reproducible.
    >     >     >     >
    >     >     >     > So as long as this reproducibility is a requirement, I
    > guess
    >     > we’re
    >     >     > done. I
    >     >     >     > do understand what it’s used for in this context,
    > however I
    >     > think
    >     >     > it’s just
    >     >     >     > not working.
    >     >     >     >
    >     >     >     > The other option would be to simply release with maven,
    > which
    >     > would
    >     >     > have
    >     >     >     > been a 1-2 hour experience for all modules.
    >     >     >     >
    >     >     >     > I do agree that if the steps work and all preconditions
    > would
    >     > be
    >     >     > checked
    >     >     >     > (which they currently are not) it is very easy to break
    > the
    >     >     > “process”. And
    >     >     >     > it involves running 13 jobs … but as far as I got it
    > also the
    >     >     > execution of
    >     >     >     > 32 manual commands for everything till step 7
    >     >     >     > 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
    >     >     >     >
    >     >     >     > So as long as we’re forced to stick to this process … I
    > guess
    >     >     > someone else
    >     >     >     > will have to do it.
    >     >     >     >
    >     >     >     > Please feel free to revert any changes I did in the last
    > few
    >     > months.
    >     >     >     >
    >     >     >     > Signing off,
    >     >     >     > Chris
    >     >     >     >
    >     >     >     > PS: You really should make this ApacheRoyaleCI guy a
    > committer
    >     >     > considering
    >     >     >     > the amount of emails he’s writing ;-)
    >     >     >     >
    >     >     >     >
    >     >     >     >
    >     >     >
    >     >     >     --
    >     >     >     Carlos Rovira
    >     >     >
    >     >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Cb1c95c1197c14265c8f108d7d0fb1a60%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207649212793116&amp;sdata=lxjLZ3YoajhMOkYejA%2F6xHc2MSarS5GHPjAjegHBEbo%3D&amp;reserved=0
    >     >     >
    >     >     >
    >     >     >
    >     >     >
    >     >
    >     >     --
    >     >     Carlos Rovira
    >     >
    >     >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Cb1c95c1197c14265c8f108d7d0fb1a60%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207649212793116&amp;sdata=lxjLZ3YoajhMOkYejA%2F6xHc2MSarS5GHPjAjegHBEbo%3D&amp;reserved=0
    >     >
    >     >
    >     >
    >
    >     --
    >     Carlos Rovira
    >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Cb1c95c1197c14265c8f108d7d0fb1a60%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207649212803104&amp;sdata=t16zVFxgX1BqviC0jpofZfgqCcu10ZZ5B4b6Mfv0uCk%3D&amp;reserved=0
    >
    >
    >
    


Re: Releasing: Finally giving up

Posted by Greg Dove <gr...@gmail.com>.
 'It could be an issue when the US and Europe have different daylight
savings time settings.....  When we saw it work, we were not at one of
those transition points.'

Southern hemisphere and northern hemisphere differences pivot by 2 hours
through these transition gaps, which are typically 2 weeks or 1 week when
the application or non-application of DST is aligned between the two
countries being compared.
For the majority of the year DST is not aligned. The end of each transition
results in things being 2 hours different from whatever was 'normal'
before.

If the nature of this problem is as-described, which seems to require DST
alignment, does that mean the timestamp issues might be present most of the
time for someone south of the equator and perhaps only work in the
'transitions' when DST 'settings' are briefly aligned?
So far, I know this hasn't been a problem, with Royale having had no RM
from southern climes, iirc. So I'm just asking mainly to clarify my
understanding of the problem itself. If the answer is "I'm not sure, try it
and see" I am not at that point yet :)

If, however, there is something specific that I can investigate about
timestamp issues, I am happy to try.


On Thu, Mar 26, 2020 at 7:23 AM Alex Harui <ah...@adobe.com.invalid> wrote:

> That has nothing to do with the Ant build of release artifacts.  That is
> just using Ant to run command line commands to download and verify Maven
> release artifacts.  I'm pretty sure you can just look at the steps and type
> them in manually at the command line and you'll get the same results.
>
> AFAICT, the problem is that the reproducible binaries generated by Maven
> aren't reproducible.    It could be an issue when the US and Europe have
> different daylight savings time settings.  When we saw it work, we were not
> at one of those transition points.  So maybe it is best to just wait until
> Sunday.  But it did work for me in the US and Piotr in EU.
>
> Proposals for better ways to have an RM verify artifacts built on a remote
> machine are welcome.  Testing reproducible binaries was the only way I
> could think of and implement.
>
> -Alex
>
> On 3/25/20, 11:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
>     Hi Alex,
>
>     after run CI Server 007 we get this email:
>
>     From the royale-typedefs repo:
>     1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7
>     -DskipTests=true
>     This will download the artifacts then unzip and compile the source
> artifact.
>     2. Validate that the compiled artifacts match the downloaded artifacts.
>     3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign
>     -Drelease.version=0.9.7
>     This will PGP sign the source ZIP and compiled JARs
>     4. Then run ant -f releasesteps.xml Release_Step_007_Upload
>     -Drelease.version=0.9.7
>     This will upload the signed artifacts to Maven Release Staging. Do not
>     "Close" the staging repository until the other repos have been added.
>
>     This is what is failing from sub step 007-1, so as part of the step,
> I'm
>     downloading with ant and building, signing and then uploading (Or steps
>     should allow me to do that, but is failing)
>
>     A part from that I don't think we really want a solution where of
> breaking
>     steps event more. What we're requesting is remove steps.
>
>
>
>
>     El mié., 25 mar. 2020 a las 18:54, Alex Harui
> (<ah...@adobe.com.invalid>)
>     escribió:
>
>     > I'm sorry, I must have missed something.  Where was Ant involved in
> any of
>     > the problems reported so far?  AFAICT, it was all Maven plugins
> driving our
>     > compiler and we couldn't get reproducible binaries.
>     >
>     > I suggested in one reply that Chris fills a staging repo using his
> local
>     > machine just to make sure we know what Maven commands need to be run
> to
>     > generate all of the Maven artifacts.   And that would validate the
> claim
>     > that it is really doable in two or three steps.  A partial
> verification of
>     > validity is to check that the same set of files was produced as in
> 0.9.6
>     > (there might be some new SWCs though).
>     >
>     > Then someone else (maybe Carlos) would download all of the
> artifacts, run
>     > the same steps, download the new artifacts and verify that the binary
>     > match.  Then we can work on splitting those steps into chunks for
> the CI
>     > server.
>     >
>     > -Alex
>     >
>     >
>     > On 3/25/20, 10:13 AM, "Carlos Rovira" <ca...@apache.org>
> wrote:
>     >
>     >     We imposed ourselves a need to release building with two build
> systems.
>     >     That's the biggest issue and that's a requirement of this PMC.
>     >     That's what makes the need of the actual CI steps and the
> complex and
>     >     intricate process.
>     >
>     >     For the rest of Apache a release is:
>     >
>     >     "For an *Apache* project, that means any publication outside the
>     >     development community, defined as individuals actively
> participating in
>     >     development or following the dev list. More narrowly, an official
>     > *Apache
>     >     release* is one which has been endorsed as an "act of the
> Foundation"
>     > by a
>     >     PMC."
>     >
>     >     That means that we can release with ANT, with Maven, or any
> other build
>     >     systems as part of the process, and even try what we're doing of
>     > trying to
>     >     build with n build systems and try to check all is ok with the
>     > artifacts
>     >     generated by all that build systems and check all of them...but
> if
>     > that's
>     >     what we want, I personally will left this wagon, and wish you
> the best
>     > of
>     >     lucks in the process.
>     >
>     >     Chris and I proposed to just use Maven *for release* (so please,
> I
>     > expect
>     >     no body starts to say we are throwing away ANT from the project
> for
>     >     building, please....we are just discussing release here).
>     >
>     >     What do you think about to try to release just with Maven? If
> can do
>     > in the
>     >     next day or two and get the release published...will that work
> for
>     > you? I
>     >     think we don't need anything more, and I'm sure our users will be
>     > happy too.
>     >
>     >     And yes, people wanting then to build with Ant or with Maven
> will be
>     > able
>     >     to do so... :-)
>     >
>     >     Thanks
>     >
>     >     Carlos
>     >
>     >
>     >     [1]
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease-publishing.html&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=dsxwqItfcgSIUYZMYzgMziBunHmiBgubwQfiHAsaovA%3D&amp;reserved=0
>     >
>     >
>     >
>     >     El mié., 25 mar. 2020 a las 17:46, Christofer Dutz (<
>     >     christofer.dutz@c-ware.de>) escribió:
>     >
>     >     > Hi Yiashay,
>     >     >
>     >     > I agree ... but I didn't create Maven ... haven't even
> provided a
>     > single
>     >     > PR to it ;-)
>     >     > I think my only noticeable contribution was that they changed
> their
>     >     > website to forbid the usage of "maven-{something}-plugin" to
> Apache
>     > Maven
>     >     > Core modules (It initially said Apache Maven Plugins which
> would have
>     >     > applied for maven-flex-plugin and maven-plc4x-plugin)
>     >     >
>     >     > I think you should focus not on the process, but the bases a
> process
>     >     > should cover.
>     >     >
>     >     > Focus on what you want to be provided or ensured by any
> process, no
>     > matter
>     >     > which tool it is based on.
>     >     >
>     >     > That's what I created the google doc for.
>     >     >
>     >     > If you decide to loosen the requirement on sticking 100% to the
>     > existing
>     >     > process I am more than willing to help.
>     >     > However if you stick to the current process, it doesn't make
> any
>     > sense for
>     >     > me to do so.
>     >     >
>     >     > Looking forward to a productive discussion,
>     >     >
>     >     > Chris
>     >     >
>     >     >
>     >     > Am 25.03.20, 17:36 schrieb "Yishay Weiss" <
> yishayjobs@hotmail.com>:
>     >     >
>     >     >     I think the focus should be to agree on the requirements.
>     > Whether an
>     >     > RM uses the tool created by Chris or Alex can be a matter of
> choice.
>     >     >
>     >     >     From: Carlos Rovira<ma...@apache.org>
>     >     >     Sent: Wednesday, March 25, 2020 5:18 PM
>     >     >     To: Apache Royale Development<mailto:dev@royale.apache.org
> >
>     >     >     Subject: Re: Releasing: Finally giving up
>     >     >
>     >     >     Hi,
>     >     >
>     >     >     first of all, many thanks for all the time invested by
> Chris this
>     >     > days. We
>     >     >     almost didn't have any normal life this latest 2'5 days,
> but as
>     > well
>     >     > many
>     >     >     other work (spliced in many hours in the several previous
> days)
>     > was
>     >     >     prepared to start this release, so for a person out side
> this
>     > project,
>     >     > I
>     >     >     think we all should thanks a lot his dedications. The good
>     > output is
>     >     > that
>     >     >     process was streamlined, removing unneeded params to enter
> and
>     > fixing
>     >     > many
>     >     >     bugs over the place. That only can be performed by a good
>     > specialist in
>     >     >     build systems like Chris, I just could be a companion to
> execute
>     > steps
>     >     > and
>     >     >     try to be trained in the process.
>     >     >
>     >     >     About me: I must to say that I tried hard to make this
> work, but
>     > I must
>     >     >     assume I don't have the skills to do it (what is normal,
> since
>     > if an
>     >     > expert
>     >     >     in build stuff like Chris can't do it, I don't think any
> other
>     > one
>     >     > could do
>     >     >     it, and less me). The good point is that I know I have a
> great a
>     > deep
>     >     >     knowledge about the overall process, and while in November
> I
>     > could
>     >     >     envision, something of what I could see this days, now I
> have a
>     > clear
>     >     >     knowledge of all of it (taking into account that we just go
>     > through
>     >     >     compiler and typedefs and not framework, that could be,
> due to
>     > size, a
>     >     > much
>     >     >     bigger challenge...)
>     >     >
>     >     >     About the process: I must say that the initial intention
> was so
>     > good,
>     >     > and I
>     >     >     think we all want the premise offered thanks to Alex. The
>     > reality I
>     >     > think
>     >     >     is defeating the premise, and we should all see the
> reality with
>     > clear
>     >     >     sight and without worrying about egos but just looking and
> what
>     > the
>     >     > project
>     >     >     need.
>     >     >
>     >     >     Since the CI process involves so many steps, manual
> commands in
>     > CI
>     >     > steps,
>     >     >     and...manual commands in local machine. One of the most
> annoying
>     >     > things is
>     >     >     the CI server hanging lots of time (the Java agent exits
> and that
>     >     > means you
>     >     >     must reboot in order the system working all again without
>     > problems).
>     >     > The
>     >     >     final problem is that you as a RM will fail some times in
> doing
>     > what
>     >     > the
>     >     >     process needs (indicated in emails), and although you are
>     > trained a
>     >     > lot in
>     >     >     how to do the project you will found stuck in some
> situations
>     > where you
>     >     >     simple don't know what to do.
>     >     >
>     >     >     (For example I forgot or did a bad step that makes me
> rollover
>     > things
>     >     > in
>     >     >     succeed steps, so I had to roll back versions in the
> compiler,
>     > but
>     >     > since I
>     >     >     was doing a tools release too, I didn't have into account
> that I
>     > need
>     >     > to
>     >     >     roll back versions in tools too. It's clear as Chris notice
>     > that, but
>     >     > not
>     >     >     for me at all. So we all should know with this example
> that the
>     >     > process is
>     >     >     not automatic at all. If just involve 2-3 steps, that
> would be
>     >     > manageable,
>     >     >     but we are talking of 13 steps with 32 manual steps (until
> step
>     > 7),
>     >     > plus
>     >     >     maybe other 30 or so commands until step 13?)...hope you
>     > understand the
>     >     >     challenge here and that is nothing easy for any of us.
>     >     >
>     >     >     What I mean, and my advice, from someone that loves this
> project
>     > and
>     >     > want
>     >     >     it to make it shine: We should try to simple focus in
> what's
>     > important.
>     >     >     Chris is offering a way that ensures release done simple
> and
>     > easily. My
>     >     >     take is that we can't afford to go this way more time,
> since the
>     >     > project
>     >     >     will see his existence threatened. We're here many years
> here,
>     > and this
>     >     >     actual problem is a big one. It's clear that we have a
> problem
>     > if we
>     >     > can
>     >     >     release every month (or two month) with a process that is
> easy
>     > for
>     >     > everyone
>     >     >     and requires not a great training to do so, and will
> require
>     > some few
>     >     >     commands and operations to be done. We simply can't
> release, and
>     > we can
>     >     >     rely in a process that is so fragile, to make every change
> we do
>     > in the
>     >     >     future will break it.
>     >     >
>     >     >     The fact is that we didn't get so many people jumping to
> Royale
>     > and the
>     >     >     ones with an eye on this project can finally gone if we
> continue
>     >     > trying to
>     >     >     force things that we don't need. We can release just with
> maven
>     > in few
>     >     >     steps, that's a fact, and we don't really need to make
> things in
>     > the
>     >     > actual
>     >     >     way. If we do is because we're forcing it, but nobody
> cares, and
>     > my
>     >     > vision
>     >     >     is that will cost the project.
>     >     >
>     >     >     We simplify the build Maven process to make it more
> reliable,
>     > that
>     >     > break
>     >     >     the release process in November. The build process has
> priority
>     > over
>     >     > the
>     >     >     release process, since lots of users depend on them (royale
>     > devs, and
>     >     >     users). The release process is important in the project
> context
>     > to
>     >     > offer
>     >     >     the bits to the public as a tag or point in time.
>     >     >
>     >     >     We simply can't put the release process to the service of
> the
>     > build
>     >     > process
>     >     >     and make all of that stop in time to not break a fragile
> release
>     >     > process.
>     >     >     That's not an option for an open source project. The
> release
>     > process
>     >     > is at
>     >     >     the service of the rest (people, builds, code....)
>     >     >
>     >     >     I'd want people here to rethink all of this since:
>     >     >
>     >     >
>     >     >        - We can't afford this project not to release easily
> monthly
>     > (or
>     >     > every 2
>     >     >        months) for anyone here (and I mean all people here that
>     > wants to
>     >     > be an RM).
>     >     >        - We can't afford so many hours invested to release, or
> to
>     > maintain
>     >     > a
>     >     >        process that is very, very, very difficult to operate,
>     > fragile and
>     >     > easy to
>     >     >        break.
>     >     >
>     >     >
>     >     >     The motivations are:
>     >     >
>     >     >
>     >     >        1. Although the process was designed and done with very
> good
>     >     > intentions,
>     >     >        the final product does not match the premise. "To make
> the
>     > Release
>     >     > process
>     >     >        affordable and reliable for each RM"
>     >     >        2. The CI server steps needs you to work on you local
>     > machine, what
>     >     >        defeats the premise to work just in the CI server.
>     >     >        3. The actual process involve 13 steps instead of
> something
>     > more
>     >     >        manageable like 2-3
>     >     >        4. The actual process involve many manual commands in
> the CI
>     > server
>     >     >        splitter through the 13 steps (1 to 5 commands for each
> step
>     >     > depending on
>     >     >        the step)
>     >     >        5. The actual process involve many manual commands in
> your
>     > local
>     >     > machine
>     >     >        splittled every 3 steps. So you need to use your local
>     > machine what
>     >     > defeats
>     >     >        entirely the CI steps to not need the RM to configure
> his
>     > machine.
>     >     > This
>     >     >        happens in steps 3 and 7 (and fo sure later in
> frameworks
>     > part).
>     >     >        6. The CI server use to hang the Jenkins java agent
> process
>     > that
>     >     >        involves a reboot, what make all the process highly
>     > cumbersome. You
>     >     > can
>     >     >        easily get to reboot CI server 1-2 times while doing the
>     > first 3
>     >     > steps.
>     >     >        7. If you fail in some step (because you simply fail
> since
>     > you're
>     >     > human,
>     >     >        or the hangs and things happening make you loose the
> track of
>     > what
>     >     > you're
>     >     >        doing and make something that provoke the fail) you
> need to
>     >     > rollback, and
>     >     >        know how to operate to restore al the process, crossing
>     > fingers to
>     >     > expect
>     >     >        all goes well, rolling back versions, removing release
> branch,
>     >     > removing
>     >     >        tags,...)
>     >     >        8. In the end, If you finally get all the process to
> work,
>     > since is
>     >     >        very, very fragile, is very possible that some updates
> in the
>     >     > future make
>     >     >        it fail again, and the fix will required more and more
> hours
>     > of
>     >     >        experimented people, patience, and testing.
>     >     >
>     >     >     About time. For people trained in the process, (and I
> think I
>     > get very
>     >     >     trained this days). Steps 1 to 6-7 is about 1h and 30' to
> 2h. I
>     > think
>     >     >     getting to step 13 and taking into account that framework
> is
>     > much more
>     >     > code
>     >     >     and time to build, I expect the global process is about 2h
> or
>     > maybe
>     >     > more.
>     >     >     So we are talking about 3'5 to 4h, of all this complicated
>     > process with
>     >     >     lots of opportunities to fail in some of the ways already
>     > commented.
>     >     >
>     >     >     We have the opportunity now: Chris wanted to use the
> project for
>     > PCL4X
>     >     > to
>     >     >     build IoT apps. I think that's a huge opportunity for
> Royale.
>     > He's
>     >     > giving
>     >     >     up to use whatever other frontend tech (React, Angular,
> Vue,...).
>     >     >
>     >     >     So all this is making Royale to continue moving backwards
>     > instead to
>     >     >     conquer new positions. I have clear that this is not the
> way to
>     > go,
>     >     > and if
>     >     >     the rest of the team wants to continue forcing all of
> this. I
>     > just can
>     >     > do
>     >     >     anything but start thinking in other options, a fork or
>     > something that
>     >     >     ensure we are not loosing more for the years to come.
>     >     >
>     >     >     I still hope all of you try to think well on all of this.
> Remove
>     > egos,
>     >     >     since is not about you and me, is about just Apache
> Royale, and
>     > nobody
>     >     > out
>     >     >     there cares who or what did this or that. Is just a matter
> of
>     > what we
>     >     > want
>     >     >     for Royale, since people will just see what the project
> can do
>     > for him.
>     >     >
>     >     >     Hope this long email could make you think, and hope you
> all will
>     >     > comment to
>     >     >     have clear our positions and have clear what we can expect
> in
>     > this
>     >     >     problematic releasing problem, since is what will make us
> get
>     > more
>     >     > traction
>     >     >     or in reverse, end loosing more users and maybe die in the
> way.
>     >     >
>     >     >     Thanks
>     >     >
>     >     >     Carlos
>     >     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     >     El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
>     >     >     christofer.dutz@c-ware.de>) escribió:
>     >     >
>     >     >     > Hi all,
>     >     >     >
>     >     >     > after 3-4 days of some times 10-16 hours of working on
> getting
>     > the
>     >     >     > “process” running, I’m finally giving up.
>     >     >     > We managed to fix a lot of issues in the way the steps
> were
>     > setup and
>     >     >     > managed to get to step 7 however there’s no getting past
> that.
>     >     >     >
>     >     >     > The problem are the reproducible builds.
>     >     >     >
>     >     >     > While for the java part I think we have all bases
> covered,
>     > however I
>     >     > can’t
>     >     >     > see however how I can fix the compiler to actually
> produce
>     >     > reproducible
>     >     >     > builds.
>     >     >     >
>     >     >     > We are passing in the timestamp (slightly different
> format,
>     > however
>     >     > still
>     >     >     > correct as we also adjusted the format-string). When
> building
>     >     > locally, the
>     >     >     > timestamp is exactly as the timestamp string tells the
>     > compiler. On
>     >     > the CI
>     >     >     > however there’s this 60 minute offset. I have explicitly
> set
>     > the
>     >     > time-zone
>     >     >     > wherever I found time-zone relevant code to UTC (Which
> is the
>     >     > general best
>     >     >     > practice for date stuff). However the offset didn’t
> change. So
>     > I am
>     >     >     > completely out of ideas what could be causing this. If it
>     > really is
>     >     > the
>     >     >     > Summertime in the US, well I don’t know how to fix it
> (perhaps
>     > setup
>     >     > a rule
>     >     >     > to not release in this time).
>     >     >     >
>     >     >     > Besides that, there are still differences in the library
> SWF:
>     >     >     >
>     >     >     >   *   As I mentioned yesterday, the node typedef
> contains a
>     > “net”
>     >     > object
>     >     >     > definition in the local build and a “http” one on the CI
> server
>     >     > version.
>     >     >     >   *   In other modules it’s simply the order of items
>     > generated. I
>     >     > guess
>     >     >     > it’s a similar issue as the one I fixed in the
> build-tools,
>     > but I
>     >     > have no
>     >     >     > idea how to fix it in the compiler
>     >     >     >
>     >     >     > So in the end I’m giving up … I think the “process” is
> now way
>     > more
>     >     > stable
>     >     >     > than before, but it’s still a really fragile construct.
> Today
>     > Greg,
>     >     > Carlos
>     >     >     > and I did it together via Zoom and still we had to re-do
> some
>     > steps
>     >     > because
>     >     >     > one little preparation was missed.
>     >     >     >
>     >     >     > I would strongly doubt that the reproducible builds
> really
>     > built
>     >     > globally
>     >     >     > reproducible builds in the past … perhaps it worked in a
> narrow
>     >     > corridor of
>     >     >     > time-zones and OS/Java versions (I did use java 1.8),
> but I
>     > simply
>     >     > can’t
>     >     >     > believe it ever was 100% reproducible.
>     >     >     >
>     >     >     > So as long as this reproducibility is a requirement, I
> guess
>     > we’re
>     >     > done. I
>     >     >     > do understand what it’s used for in this context,
> however I
>     > think
>     >     > it’s just
>     >     >     > not working.
>     >     >     >
>     >     >     > The other option would be to simply release with maven,
> which
>     > would
>     >     > have
>     >     >     > been a 1-2 hour experience for all modules.
>     >     >     >
>     >     >     > I do agree that if the steps work and all preconditions
> would
>     > be
>     >     > checked
>     >     >     > (which they currently are not) it is very easy to break
> the
>     >     > “process”. And
>     >     >     > it involves running 13 jobs … but as far as I got it
> also the
>     >     > execution of
>     >     >     > 32 manual commands for everything till step 7
>     >     >     > 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
>     >     >     >
>     >     >     > So as long as we’re forced to stick to this process … I
> guess
>     >     > someone else
>     >     >     > will have to do it.
>     >     >     >
>     >     >     > Please feel free to revert any changes I did in the last
> few
>     > months.
>     >     >     >
>     >     >     > Signing off,
>     >     >     > Chris
>     >     >     >
>     >     >     > PS: You really should make this ApacheRoyaleCI guy a
> committer
>     >     > considering
>     >     >     > the amount of emails he’s writing ;-)
>     >     >     >
>     >     >     >
>     >     >     >
>     >     >
>     >     >     --
>     >     >     Carlos Rovira
>     >     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=yfDv5ocD5wFYvpuHrY2OUyw0tUpc3NZzbzbkaBF35aI%3D&amp;reserved=0
>     >     >
>     >     >
>     >     >
>     >     >
>     >
>     >     --
>     >     Carlos Rovira
>     >
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=yfDv5ocD5wFYvpuHrY2OUyw0tUpc3NZzbzbkaBF35aI%3D&amp;reserved=0
>     >
>     >
>     >
>
>     --
>     Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=yfDv5ocD5wFYvpuHrY2OUyw0tUpc3NZzbzbkaBF35aI%3D&amp;reserved=0
>
>
>

Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.
That has nothing to do with the Ant build of release artifacts.  That is just using Ant to run command line commands to download and verify Maven release artifacts.  I'm pretty sure you can just look at the steps and type them in manually at the command line and you'll get the same results.

AFAICT, the problem is that the reproducible binaries generated by Maven aren't reproducible.    It could be an issue when the US and Europe have different daylight savings time settings.  When we saw it work, we were not at one of those transition points.  So maybe it is best to just wait until Sunday.  But it did work for me in the US and Piotr in EU.

Proposals for better ways to have an RM verify artifacts built on a remote machine are welcome.  Testing reproducible binaries was the only way I could think of and implement.

-Alex

On 3/25/20, 11:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:

    Hi Alex,
    
    after run CI Server 007 we get this email:
    
    From the royale-typedefs repo:
    1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7
    -DskipTests=true
    This will download the artifacts then unzip and compile the source artifact.
    2. Validate that the compiled artifacts match the downloaded artifacts.
    3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign
    -Drelease.version=0.9.7
    This will PGP sign the source ZIP and compiled JARs
    4. Then run ant -f releasesteps.xml Release_Step_007_Upload
    -Drelease.version=0.9.7
    This will upload the signed artifacts to Maven Release Staging. Do not
    "Close" the staging repository until the other repos have been added.
    
    This is what is failing from sub step 007-1, so as part of the step, I'm
    downloading with ant and building, signing and then uploading (Or steps
    should allow me to do that, but is failing)
    
    A part from that I don't think we really want a solution where of breaking
    steps event more. What we're requesting is remove steps.
    
    
    
    
    El mié., 25 mar. 2020 a las 18:54, Alex Harui (<ah...@adobe.com.invalid>)
    escribió:
    
    > I'm sorry, I must have missed something.  Where was Ant involved in any of
    > the problems reported so far?  AFAICT, it was all Maven plugins driving our
    > compiler and we couldn't get reproducible binaries.
    >
    > I suggested in one reply that Chris fills a staging repo using his local
    > machine just to make sure we know what Maven commands need to be run to
    > generate all of the Maven artifacts.   And that would validate the claim
    > that it is really doable in two or three steps.  A partial verification of
    > validity is to check that the same set of files was produced as in 0.9.6
    > (there might be some new SWCs though).
    >
    > Then someone else (maybe Carlos) would download all of the artifacts, run
    > the same steps, download the new artifacts and verify that the binary
    > match.  Then we can work on splitting those steps into chunks for the CI
    > server.
    >
    > -Alex
    >
    >
    > On 3/25/20, 10:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
    >
    >     We imposed ourselves a need to release building with two build systems.
    >     That's the biggest issue and that's a requirement of this PMC.
    >     That's what makes the need of the actual CI steps and the complex and
    >     intricate process.
    >
    >     For the rest of Apache a release is:
    >
    >     "For an *Apache* project, that means any publication outside the
    >     development community, defined as individuals actively participating in
    >     development or following the dev list. More narrowly, an official
    > *Apache
    >     release* is one which has been endorsed as an "act of the Foundation"
    > by a
    >     PMC."
    >
    >     That means that we can release with ANT, with Maven, or any other build
    >     systems as part of the process, and even try what we're doing of
    > trying to
    >     build with n build systems and try to check all is ok with the
    > artifacts
    >     generated by all that build systems and check all of them...but if
    > that's
    >     what we want, I personally will left this wagon, and wish you the best
    > of
    >     lucks in the process.
    >
    >     Chris and I proposed to just use Maven *for release* (so please, I
    > expect
    >     no body starts to say we are throwing away ANT from the project for
    >     building, please....we are just discussing release here).
    >
    >     What do you think about to try to release just with Maven? If can do
    > in the
    >     next day or two and get the release published...will that work for
    > you? I
    >     think we don't need anything more, and I'm sure our users will be
    > happy too.
    >
    >     And yes, people wanting then to build with Ant or with Maven will be
    > able
    >     to do so... :-)
    >
    >     Thanks
    >
    >     Carlos
    >
    >
    >     [1]
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease-publishing.html&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=dsxwqItfcgSIUYZMYzgMziBunHmiBgubwQfiHAsaovA%3D&amp;reserved=0
    >
    >
    >
    >     El mié., 25 mar. 2020 a las 17:46, Christofer Dutz (<
    >     christofer.dutz@c-ware.de>) escribió:
    >
    >     > Hi Yiashay,
    >     >
    >     > I agree ... but I didn't create Maven ... haven't even provided a
    > single
    >     > PR to it ;-)
    >     > I think my only noticeable contribution was that they changed their
    >     > website to forbid the usage of "maven-{something}-plugin" to Apache
    > Maven
    >     > Core modules (It initially said Apache Maven Plugins which would have
    >     > applied for maven-flex-plugin and maven-plc4x-plugin)
    >     >
    >     > I think you should focus not on the process, but the bases a process
    >     > should cover.
    >     >
    >     > Focus on what you want to be provided or ensured by any process, no
    > matter
    >     > which tool it is based on.
    >     >
    >     > That's what I created the google doc for.
    >     >
    >     > If you decide to loosen the requirement on sticking 100% to the
    > existing
    >     > process I am more than willing to help.
    >     > However if you stick to the current process, it doesn't make any
    > sense for
    >     > me to do so.
    >     >
    >     > Looking forward to a productive discussion,
    >     >
    >     > Chris
    >     >
    >     >
    >     > Am 25.03.20, 17:36 schrieb "Yishay Weiss" <yi...@hotmail.com>:
    >     >
    >     >     I think the focus should be to agree on the requirements.
    > Whether an
    >     > RM uses the tool created by Chris or Alex can be a matter of choice.
    >     >
    >     >     From: Carlos Rovira<ma...@apache.org>
    >     >     Sent: Wednesday, March 25, 2020 5:18 PM
    >     >     To: Apache Royale Development<ma...@royale.apache.org>
    >     >     Subject: Re: Releasing: Finally giving up
    >     >
    >     >     Hi,
    >     >
    >     >     first of all, many thanks for all the time invested by Chris this
    >     > days. We
    >     >     almost didn't have any normal life this latest 2'5 days, but as
    > well
    >     > many
    >     >     other work (spliced in many hours in the several previous days)
    > was
    >     >     prepared to start this release, so for a person out side this
    > project,
    >     > I
    >     >     think we all should thanks a lot his dedications. The good
    > output is
    >     > that
    >     >     process was streamlined, removing unneeded params to enter and
    > fixing
    >     > many
    >     >     bugs over the place. That only can be performed by a good
    > specialist in
    >     >     build systems like Chris, I just could be a companion to execute
    > steps
    >     > and
    >     >     try to be trained in the process.
    >     >
    >     >     About me: I must to say that I tried hard to make this work, but
    > I must
    >     >     assume I don't have the skills to do it (what is normal, since
    > if an
    >     > expert
    >     >     in build stuff like Chris can't do it, I don't think any other
    > one
    >     > could do
    >     >     it, and less me). The good point is that I know I have a great a
    > deep
    >     >     knowledge about the overall process, and while in November I
    > could
    >     >     envision, something of what I could see this days, now I have a
    > clear
    >     >     knowledge of all of it (taking into account that we just go
    > through
    >     >     compiler and typedefs and not framework, that could be, due to
    > size, a
    >     > much
    >     >     bigger challenge...)
    >     >
    >     >     About the process: I must say that the initial intention was so
    > good,
    >     > and I
    >     >     think we all want the premise offered thanks to Alex. The
    > reality I
    >     > think
    >     >     is defeating the premise, and we should all see the reality with
    > clear
    >     >     sight and without worrying about egos but just looking and what
    > the
    >     > project
    >     >     need.
    >     >
    >     >     Since the CI process involves so many steps, manual commands in
    > CI
    >     > steps,
    >     >     and...manual commands in local machine. One of the most annoying
    >     > things is
    >     >     the CI server hanging lots of time (the Java agent exits and that
    >     > means you
    >     >     must reboot in order the system working all again without
    > problems).
    >     > The
    >     >     final problem is that you as a RM will fail some times in doing
    > what
    >     > the
    >     >     process needs (indicated in emails), and although you are
    > trained a
    >     > lot in
    >     >     how to do the project you will found stuck in some situations
    > where you
    >     >     simple don't know what to do.
    >     >
    >     >     (For example I forgot or did a bad step that makes me rollover
    > things
    >     > in
    >     >     succeed steps, so I had to roll back versions in the compiler,
    > but
    >     > since I
    >     >     was doing a tools release too, I didn't have into account that I
    > need
    >     > to
    >     >     roll back versions in tools too. It's clear as Chris notice
    > that, but
    >     > not
    >     >     for me at all. So we all should know with this example that the
    >     > process is
    >     >     not automatic at all. If just involve 2-3 steps, that would be
    >     > manageable,
    >     >     but we are talking of 13 steps with 32 manual steps (until step
    > 7),
    >     > plus
    >     >     maybe other 30 or so commands until step 13?)...hope you
    > understand the
    >     >     challenge here and that is nothing easy for any of us.
    >     >
    >     >     What I mean, and my advice, from someone that loves this project
    > and
    >     > want
    >     >     it to make it shine: We should try to simple focus in what's
    > important.
    >     >     Chris is offering a way that ensures release done simple and
    > easily. My
    >     >     take is that we can't afford to go this way more time, since the
    >     > project
    >     >     will see his existence threatened. We're here many years here,
    > and this
    >     >     actual problem is a big one. It's clear that we have a problem
    > if we
    >     > can
    >     >     release every month (or two month) with a process that is easy
    > for
    >     > everyone
    >     >     and requires not a great training to do so, and will require
    > some few
    >     >     commands and operations to be done. We simply can't release, and
    > we can
    >     >     rely in a process that is so fragile, to make every change we do
    > in the
    >     >     future will break it.
    >     >
    >     >     The fact is that we didn't get so many people jumping to Royale
    > and the
    >     >     ones with an eye on this project can finally gone if we continue
    >     > trying to
    >     >     force things that we don't need. We can release just with maven
    > in few
    >     >     steps, that's a fact, and we don't really need to make things in
    > the
    >     > actual
    >     >     way. If we do is because we're forcing it, but nobody cares, and
    > my
    >     > vision
    >     >     is that will cost the project.
    >     >
    >     >     We simplify the build Maven process to make it more reliable,
    > that
    >     > break
    >     >     the release process in November. The build process has priority
    > over
    >     > the
    >     >     release process, since lots of users depend on them (royale
    > devs, and
    >     >     users). The release process is important in the project context
    > to
    >     > offer
    >     >     the bits to the public as a tag or point in time.
    >     >
    >     >     We simply can't put the release process to the service of the
    > build
    >     > process
    >     >     and make all of that stop in time to not break a fragile release
    >     > process.
    >     >     That's not an option for an open source project. The release
    > process
    >     > is at
    >     >     the service of the rest (people, builds, code....)
    >     >
    >     >     I'd want people here to rethink all of this since:
    >     >
    >     >
    >     >        - We can't afford this project not to release easily monthly
    > (or
    >     > every 2
    >     >        months) for anyone here (and I mean all people here that
    > wants to
    >     > be an RM).
    >     >        - We can't afford so many hours invested to release, or to
    > maintain
    >     > a
    >     >        process that is very, very, very difficult to operate,
    > fragile and
    >     > easy to
    >     >        break.
    >     >
    >     >
    >     >     The motivations are:
    >     >
    >     >
    >     >        1. Although the process was designed and done with very good
    >     > intentions,
    >     >        the final product does not match the premise. "To make the
    > Release
    >     > process
    >     >        affordable and reliable for each RM"
    >     >        2. The CI server steps needs you to work on you local
    > machine, what
    >     >        defeats the premise to work just in the CI server.
    >     >        3. The actual process involve 13 steps instead of something
    > more
    >     >        manageable like 2-3
    >     >        4. The actual process involve many manual commands in the CI
    > server
    >     >        splitter through the 13 steps (1 to 5 commands for each step
    >     > depending on
    >     >        the step)
    >     >        5. The actual process involve many manual commands in your
    > local
    >     > machine
    >     >        splittled every 3 steps. So you need to use your local
    > machine what
    >     > defeats
    >     >        entirely the CI steps to not need the RM to configure his
    > machine.
    >     > This
    >     >        happens in steps 3 and 7 (and fo sure later in frameworks
    > part).
    >     >        6. The CI server use to hang the Jenkins java agent process
    > that
    >     >        involves a reboot, what make all the process highly
    > cumbersome. You
    >     > can
    >     >        easily get to reboot CI server 1-2 times while doing the
    > first 3
    >     > steps.
    >     >        7. If you fail in some step (because you simply fail since
    > you're
    >     > human,
    >     >        or the hangs and things happening make you loose the track of
    > what
    >     > you're
    >     >        doing and make something that provoke the fail) you need to
    >     > rollback, and
    >     >        know how to operate to restore al the process, crossing
    > fingers to
    >     > expect
    >     >        all goes well, rolling back versions, removing release branch,
    >     > removing
    >     >        tags,...)
    >     >        8. In the end, If you finally get all the process to work,
    > since is
    >     >        very, very fragile, is very possible that some updates in the
    >     > future make
    >     >        it fail again, and the fix will required more and more hours
    > of
    >     >        experimented people, patience, and testing.
    >     >
    >     >     About time. For people trained in the process, (and I think I
    > get very
    >     >     trained this days). Steps 1 to 6-7 is about 1h and 30' to 2h. I
    > think
    >     >     getting to step 13 and taking into account that framework is
    > much more
    >     > code
    >     >     and time to build, I expect the global process is about 2h or
    > maybe
    >     > more.
    >     >     So we are talking about 3'5 to 4h, of all this complicated
    > process with
    >     >     lots of opportunities to fail in some of the ways already
    > commented.
    >     >
    >     >     We have the opportunity now: Chris wanted to use the project for
    > PCL4X
    >     > to
    >     >     build IoT apps. I think that's a huge opportunity for Royale.
    > He's
    >     > giving
    >     >     up to use whatever other frontend tech (React, Angular, Vue,...).
    >     >
    >     >     So all this is making Royale to continue moving backwards
    > instead to
    >     >     conquer new positions. I have clear that this is not the way to
    > go,
    >     > and if
    >     >     the rest of the team wants to continue forcing all of this. I
    > just can
    >     > do
    >     >     anything but start thinking in other options, a fork or
    > something that
    >     >     ensure we are not loosing more for the years to come.
    >     >
    >     >     I still hope all of you try to think well on all of this. Remove
    > egos,
    >     >     since is not about you and me, is about just Apache Royale, and
    > nobody
    >     > out
    >     >     there cares who or what did this or that. Is just a matter of
    > what we
    >     > want
    >     >     for Royale, since people will just see what the project can do
    > for him.
    >     >
    >     >     Hope this long email could make you think, and hope you all will
    >     > comment to
    >     >     have clear our positions and have clear what we can expect in
    > this
    >     >     problematic releasing problem, since is what will make us get
    > more
    >     > traction
    >     >     or in reverse, end loosing more users and maybe die in the way.
    >     >
    >     >     Thanks
    >     >
    >     >     Carlos
    >     >
    >     >
    >     >
    >     >
    >     >
    >     >
    >     >
    >     >
    >     >
    >     >     El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
    >     >     christofer.dutz@c-ware.de>) escribió:
    >     >
    >     >     > Hi all,
    >     >     >
    >     >     > after 3-4 days of some times 10-16 hours of working on getting
    > the
    >     >     > “process” running, I’m finally giving up.
    >     >     > We managed to fix a lot of issues in the way the steps were
    > setup and
    >     >     > managed to get to step 7 however there’s no getting past that.
    >     >     >
    >     >     > The problem are the reproducible builds.
    >     >     >
    >     >     > While for the java part I think we have all bases covered,
    > however I
    >     > can’t
    >     >     > see however how I can fix the compiler to actually produce
    >     > reproducible
    >     >     > builds.
    >     >     >
    >     >     > We are passing in the timestamp (slightly different format,
    > however
    >     > still
    >     >     > correct as we also adjusted the format-string). When building
    >     > locally, the
    >     >     > timestamp is exactly as the timestamp string tells the
    > compiler. On
    >     > the CI
    >     >     > however there’s this 60 minute offset. I have explicitly set
    > the
    >     > time-zone
    >     >     > wherever I found time-zone relevant code to UTC (Which is the
    >     > general best
    >     >     > practice for date stuff). However the offset didn’t change. So
    > I am
    >     >     > completely out of ideas what could be causing this. If it
    > really is
    >     > the
    >     >     > Summertime in the US, well I don’t know how to fix it (perhaps
    > setup
    >     > a rule
    >     >     > to not release in this time).
    >     >     >
    >     >     > Besides that, there are still differences in the library SWF:
    >     >     >
    >     >     >   *   As I mentioned yesterday, the node typedef contains a
    > “net”
    >     > object
    >     >     > definition in the local build and a “http” one on the CI server
    >     > version.
    >     >     >   *   In other modules it’s simply the order of items
    > generated. I
    >     > guess
    >     >     > it’s a similar issue as the one I fixed in the build-tools,
    > but I
    >     > have no
    >     >     > idea how to fix it in the compiler
    >     >     >
    >     >     > So in the end I’m giving up … I think the “process” is now way
    > more
    >     > stable
    >     >     > than before, but it’s still a really fragile construct. Today
    > Greg,
    >     > Carlos
    >     >     > and I did it together via Zoom and still we had to re-do some
    > steps
    >     > because
    >     >     > one little preparation was missed.
    >     >     >
    >     >     > I would strongly doubt that the reproducible builds really
    > built
    >     > globally
    >     >     > reproducible builds in the past … perhaps it worked in a narrow
    >     > corridor of
    >     >     > time-zones and OS/Java versions (I did use java 1.8), but I
    > simply
    >     > can’t
    >     >     > believe it ever was 100% reproducible.
    >     >     >
    >     >     > So as long as this reproducibility is a requirement, I guess
    > we’re
    >     > done. I
    >     >     > do understand what it’s used for in this context, however I
    > think
    >     > it’s just
    >     >     > not working.
    >     >     >
    >     >     > The other option would be to simply release with maven, which
    > would
    >     > have
    >     >     > been a 1-2 hour experience for all modules.
    >     >     >
    >     >     > I do agree that if the steps work and all preconditions would
    > be
    >     > checked
    >     >     > (which they currently are not) it is very easy to break the
    >     > “process”. And
    >     >     > it involves running 13 jobs … but as far as I got it also the
    >     > execution of
    >     >     > 32 manual commands for everything till step 7
    >     >     > 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
    >     >     >
    >     >     > So as long as we’re forced to stick to this process … I guess
    >     > someone else
    >     >     > will have to do it.
    >     >     >
    >     >     > Please feel free to revert any changes I did in the last few
    > months.
    >     >     >
    >     >     > Signing off,
    >     >     > Chris
    >     >     >
    >     >     > PS: You really should make this ApacheRoyaleCI guy a committer
    >     > considering
    >     >     > the amount of emails he’s writing ;-)
    >     >     >
    >     >     >
    >     >     >
    >     >
    >     >     --
    >     >     Carlos Rovira
    >     >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=yfDv5ocD5wFYvpuHrY2OUyw0tUpc3NZzbzbkaBF35aI%3D&amp;reserved=0
    >     >
    >     >
    >     >
    >     >
    >
    >     --
    >     Carlos Rovira
    >
    > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=yfDv5ocD5wFYvpuHrY2OUyw0tUpc3NZzbzbkaBF35aI%3D&amp;reserved=0
    >
    >
    >
    
    -- 
    Carlos Rovira
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Ccaac200c25a74888e76008d7d0e83611%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207568075948274&amp;sdata=yfDv5ocD5wFYvpuHrY2OUyw0tUpc3NZzbzbkaBF35aI%3D&amp;reserved=0
    


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,

after run CI Server 007 we get this email:

From the royale-typedefs repo:
1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7
-DskipTests=true
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging. Do not
"Close" the staging repository until the other repos have been added.

This is what is failing from sub step 007-1, so as part of the step, I'm
downloading with ant and building, signing and then uploading (Or steps
should allow me to do that, but is failing)

A part from that I don't think we really want a solution where of breaking
steps event more. What we're requesting is remove steps.




El mié., 25 mar. 2020 a las 18:54, Alex Harui (<ah...@adobe.com.invalid>)
escribió:

> I'm sorry, I must have missed something.  Where was Ant involved in any of
> the problems reported so far?  AFAICT, it was all Maven plugins driving our
> compiler and we couldn't get reproducible binaries.
>
> I suggested in one reply that Chris fills a staging repo using his local
> machine just to make sure we know what Maven commands need to be run to
> generate all of the Maven artifacts.   And that would validate the claim
> that it is really doable in two or three steps.  A partial verification of
> validity is to check that the same set of files was produced as in 0.9.6
> (there might be some new SWCs though).
>
> Then someone else (maybe Carlos) would download all of the artifacts, run
> the same steps, download the new artifacts and verify that the binary
> match.  Then we can work on splitting those steps into chunks for the CI
> server.
>
> -Alex
>
>
> On 3/25/20, 10:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
>     We imposed ourselves a need to release building with two build systems.
>     That's the biggest issue and that's a requirement of this PMC.
>     That's what makes the need of the actual CI steps and the complex and
>     intricate process.
>
>     For the rest of Apache a release is:
>
>     "For an *Apache* project, that means any publication outside the
>     development community, defined as individuals actively participating in
>     development or following the dev list. More narrowly, an official
> *Apache
>     release* is one which has been endorsed as an "act of the Foundation"
> by a
>     PMC."
>
>     That means that we can release with ANT, with Maven, or any other build
>     systems as part of the process, and even try what we're doing of
> trying to
>     build with n build systems and try to check all is ok with the
> artifacts
>     generated by all that build systems and check all of them...but if
> that's
>     what we want, I personally will left this wagon, and wish you the best
> of
>     lucks in the process.
>
>     Chris and I proposed to just use Maven *for release* (so please, I
> expect
>     no body starts to say we are throwing away ANT from the project for
>     building, please....we are just discussing release here).
>
>     What do you think about to try to release just with Maven? If can do
> in the
>     next day or two and get the release published...will that work for
> you? I
>     think we don't need anything more, and I'm sure our users will be
> happy too.
>
>     And yes, people wanting then to build with Ant or with Maven will be
> able
>     to do so... :-)
>
>     Thanks
>
>     Carlos
>
>
>     [1]
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease-publishing.html&amp;data=02%7C01%7Caharui%40adobe.com%7C051d4367ac9743249ec808d7d0dfd038%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207532001774243&amp;sdata=JWLztd6WGtyugYMEzRLqytO41ypZsDYQIdUhaPIMEG4%3D&amp;reserved=0
>
>
>
>     El mié., 25 mar. 2020 a las 17:46, Christofer Dutz (<
>     christofer.dutz@c-ware.de>) escribió:
>
>     > Hi Yiashay,
>     >
>     > I agree ... but I didn't create Maven ... haven't even provided a
> single
>     > PR to it ;-)
>     > I think my only noticeable contribution was that they changed their
>     > website to forbid the usage of "maven-{something}-plugin" to Apache
> Maven
>     > Core modules (It initially said Apache Maven Plugins which would have
>     > applied for maven-flex-plugin and maven-plc4x-plugin)
>     >
>     > I think you should focus not on the process, but the bases a process
>     > should cover.
>     >
>     > Focus on what you want to be provided or ensured by any process, no
> matter
>     > which tool it is based on.
>     >
>     > That's what I created the google doc for.
>     >
>     > If you decide to loosen the requirement on sticking 100% to the
> existing
>     > process I am more than willing to help.
>     > However if you stick to the current process, it doesn't make any
> sense for
>     > me to do so.
>     >
>     > Looking forward to a productive discussion,
>     >
>     > Chris
>     >
>     >
>     > Am 25.03.20, 17:36 schrieb "Yishay Weiss" <yi...@hotmail.com>:
>     >
>     >     I think the focus should be to agree on the requirements.
> Whether an
>     > RM uses the tool created by Chris or Alex can be a matter of choice.
>     >
>     >     From: Carlos Rovira<ma...@apache.org>
>     >     Sent: Wednesday, March 25, 2020 5:18 PM
>     >     To: Apache Royale Development<ma...@royale.apache.org>
>     >     Subject: Re: Releasing: Finally giving up
>     >
>     >     Hi,
>     >
>     >     first of all, many thanks for all the time invested by Chris this
>     > days. We
>     >     almost didn't have any normal life this latest 2'5 days, but as
> well
>     > many
>     >     other work (spliced in many hours in the several previous days)
> was
>     >     prepared to start this release, so for a person out side this
> project,
>     > I
>     >     think we all should thanks a lot his dedications. The good
> output is
>     > that
>     >     process was streamlined, removing unneeded params to enter and
> fixing
>     > many
>     >     bugs over the place. That only can be performed by a good
> specialist in
>     >     build systems like Chris, I just could be a companion to execute
> steps
>     > and
>     >     try to be trained in the process.
>     >
>     >     About me: I must to say that I tried hard to make this work, but
> I must
>     >     assume I don't have the skills to do it (what is normal, since
> if an
>     > expert
>     >     in build stuff like Chris can't do it, I don't think any other
> one
>     > could do
>     >     it, and less me). The good point is that I know I have a great a
> deep
>     >     knowledge about the overall process, and while in November I
> could
>     >     envision, something of what I could see this days, now I have a
> clear
>     >     knowledge of all of it (taking into account that we just go
> through
>     >     compiler and typedefs and not framework, that could be, due to
> size, a
>     > much
>     >     bigger challenge...)
>     >
>     >     About the process: I must say that the initial intention was so
> good,
>     > and I
>     >     think we all want the premise offered thanks to Alex. The
> reality I
>     > think
>     >     is defeating the premise, and we should all see the reality with
> clear
>     >     sight and without worrying about egos but just looking and what
> the
>     > project
>     >     need.
>     >
>     >     Since the CI process involves so many steps, manual commands in
> CI
>     > steps,
>     >     and...manual commands in local machine. One of the most annoying
>     > things is
>     >     the CI server hanging lots of time (the Java agent exits and that
>     > means you
>     >     must reboot in order the system working all again without
> problems).
>     > The
>     >     final problem is that you as a RM will fail some times in doing
> what
>     > the
>     >     process needs (indicated in emails), and although you are
> trained a
>     > lot in
>     >     how to do the project you will found stuck in some situations
> where you
>     >     simple don't know what to do.
>     >
>     >     (For example I forgot or did a bad step that makes me rollover
> things
>     > in
>     >     succeed steps, so I had to roll back versions in the compiler,
> but
>     > since I
>     >     was doing a tools release too, I didn't have into account that I
> need
>     > to
>     >     roll back versions in tools too. It's clear as Chris notice
> that, but
>     > not
>     >     for me at all. So we all should know with this example that the
>     > process is
>     >     not automatic at all. If just involve 2-3 steps, that would be
>     > manageable,
>     >     but we are talking of 13 steps with 32 manual steps (until step
> 7),
>     > plus
>     >     maybe other 30 or so commands until step 13?)...hope you
> understand the
>     >     challenge here and that is nothing easy for any of us.
>     >
>     >     What I mean, and my advice, from someone that loves this project
> and
>     > want
>     >     it to make it shine: We should try to simple focus in what's
> important.
>     >     Chris is offering a way that ensures release done simple and
> easily. My
>     >     take is that we can't afford to go this way more time, since the
>     > project
>     >     will see his existence threatened. We're here many years here,
> and this
>     >     actual problem is a big one. It's clear that we have a problem
> if we
>     > can
>     >     release every month (or two month) with a process that is easy
> for
>     > everyone
>     >     and requires not a great training to do so, and will require
> some few
>     >     commands and operations to be done. We simply can't release, and
> we can
>     >     rely in a process that is so fragile, to make every change we do
> in the
>     >     future will break it.
>     >
>     >     The fact is that we didn't get so many people jumping to Royale
> and the
>     >     ones with an eye on this project can finally gone if we continue
>     > trying to
>     >     force things that we don't need. We can release just with maven
> in few
>     >     steps, that's a fact, and we don't really need to make things in
> the
>     > actual
>     >     way. If we do is because we're forcing it, but nobody cares, and
> my
>     > vision
>     >     is that will cost the project.
>     >
>     >     We simplify the build Maven process to make it more reliable,
> that
>     > break
>     >     the release process in November. The build process has priority
> over
>     > the
>     >     release process, since lots of users depend on them (royale
> devs, and
>     >     users). The release process is important in the project context
> to
>     > offer
>     >     the bits to the public as a tag or point in time.
>     >
>     >     We simply can't put the release process to the service of the
> build
>     > process
>     >     and make all of that stop in time to not break a fragile release
>     > process.
>     >     That's not an option for an open source project. The release
> process
>     > is at
>     >     the service of the rest (people, builds, code....)
>     >
>     >     I'd want people here to rethink all of this since:
>     >
>     >
>     >        - We can't afford this project not to release easily monthly
> (or
>     > every 2
>     >        months) for anyone here (and I mean all people here that
> wants to
>     > be an RM).
>     >        - We can't afford so many hours invested to release, or to
> maintain
>     > a
>     >        process that is very, very, very difficult to operate,
> fragile and
>     > easy to
>     >        break.
>     >
>     >
>     >     The motivations are:
>     >
>     >
>     >        1. Although the process was designed and done with very good
>     > intentions,
>     >        the final product does not match the premise. "To make the
> Release
>     > process
>     >        affordable and reliable for each RM"
>     >        2. The CI server steps needs you to work on you local
> machine, what
>     >        defeats the premise to work just in the CI server.
>     >        3. The actual process involve 13 steps instead of something
> more
>     >        manageable like 2-3
>     >        4. The actual process involve many manual commands in the CI
> server
>     >        splitter through the 13 steps (1 to 5 commands for each step
>     > depending on
>     >        the step)
>     >        5. The actual process involve many manual commands in your
> local
>     > machine
>     >        splittled every 3 steps. So you need to use your local
> machine what
>     > defeats
>     >        entirely the CI steps to not need the RM to configure his
> machine.
>     > This
>     >        happens in steps 3 and 7 (and fo sure later in frameworks
> part).
>     >        6. The CI server use to hang the Jenkins java agent process
> that
>     >        involves a reboot, what make all the process highly
> cumbersome. You
>     > can
>     >        easily get to reboot CI server 1-2 times while doing the
> first 3
>     > steps.
>     >        7. If you fail in some step (because you simply fail since
> you're
>     > human,
>     >        or the hangs and things happening make you loose the track of
> what
>     > you're
>     >        doing and make something that provoke the fail) you need to
>     > rollback, and
>     >        know how to operate to restore al the process, crossing
> fingers to
>     > expect
>     >        all goes well, rolling back versions, removing release branch,
>     > removing
>     >        tags,...)
>     >        8. In the end, If you finally get all the process to work,
> since is
>     >        very, very fragile, is very possible that some updates in the
>     > future make
>     >        it fail again, and the fix will required more and more hours
> of
>     >        experimented people, patience, and testing.
>     >
>     >     About time. For people trained in the process, (and I think I
> get very
>     >     trained this days). Steps 1 to 6-7 is about 1h and 30' to 2h. I
> think
>     >     getting to step 13 and taking into account that framework is
> much more
>     > code
>     >     and time to build, I expect the global process is about 2h or
> maybe
>     > more.
>     >     So we are talking about 3'5 to 4h, of all this complicated
> process with
>     >     lots of opportunities to fail in some of the ways already
> commented.
>     >
>     >     We have the opportunity now: Chris wanted to use the project for
> PCL4X
>     > to
>     >     build IoT apps. I think that's a huge opportunity for Royale.
> He's
>     > giving
>     >     up to use whatever other frontend tech (React, Angular, Vue,...).
>     >
>     >     So all this is making Royale to continue moving backwards
> instead to
>     >     conquer new positions. I have clear that this is not the way to
> go,
>     > and if
>     >     the rest of the team wants to continue forcing all of this. I
> just can
>     > do
>     >     anything but start thinking in other options, a fork or
> something that
>     >     ensure we are not loosing more for the years to come.
>     >
>     >     I still hope all of you try to think well on all of this. Remove
> egos,
>     >     since is not about you and me, is about just Apache Royale, and
> nobody
>     > out
>     >     there cares who or what did this or that. Is just a matter of
> what we
>     > want
>     >     for Royale, since people will just see what the project can do
> for him.
>     >
>     >     Hope this long email could make you think, and hope you all will
>     > comment to
>     >     have clear our positions and have clear what we can expect in
> this
>     >     problematic releasing problem, since is what will make us get
> more
>     > traction
>     >     or in reverse, end loosing more users and maybe die in the way.
>     >
>     >     Thanks
>     >
>     >     Carlos
>     >
>     >
>     >
>     >
>     >
>     >
>     >
>     >
>     >
>     >     El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
>     >     christofer.dutz@c-ware.de>) escribió:
>     >
>     >     > Hi all,
>     >     >
>     >     > after 3-4 days of some times 10-16 hours of working on getting
> the
>     >     > “process” running, I’m finally giving up.
>     >     > We managed to fix a lot of issues in the way the steps were
> setup and
>     >     > managed to get to step 7 however there’s no getting past that.
>     >     >
>     >     > The problem are the reproducible builds.
>     >     >
>     >     > While for the java part I think we have all bases covered,
> however I
>     > can’t
>     >     > see however how I can fix the compiler to actually produce
>     > reproducible
>     >     > builds.
>     >     >
>     >     > We are passing in the timestamp (slightly different format,
> however
>     > still
>     >     > correct as we also adjusted the format-string). When building
>     > locally, the
>     >     > timestamp is exactly as the timestamp string tells the
> compiler. On
>     > the CI
>     >     > however there’s this 60 minute offset. I have explicitly set
> the
>     > time-zone
>     >     > wherever I found time-zone relevant code to UTC (Which is the
>     > general best
>     >     > practice for date stuff). However the offset didn’t change. So
> I am
>     >     > completely out of ideas what could be causing this. If it
> really is
>     > the
>     >     > Summertime in the US, well I don’t know how to fix it (perhaps
> setup
>     > a rule
>     >     > to not release in this time).
>     >     >
>     >     > Besides that, there are still differences in the library SWF:
>     >     >
>     >     >   *   As I mentioned yesterday, the node typedef contains a
> “net”
>     > object
>     >     > definition in the local build and a “http” one on the CI server
>     > version.
>     >     >   *   In other modules it’s simply the order of items
> generated. I
>     > guess
>     >     > it’s a similar issue as the one I fixed in the build-tools,
> but I
>     > have no
>     >     > idea how to fix it in the compiler
>     >     >
>     >     > So in the end I’m giving up … I think the “process” is now way
> more
>     > stable
>     >     > than before, but it’s still a really fragile construct. Today
> Greg,
>     > Carlos
>     >     > and I did it together via Zoom and still we had to re-do some
> steps
>     > because
>     >     > one little preparation was missed.
>     >     >
>     >     > I would strongly doubt that the reproducible builds really
> built
>     > globally
>     >     > reproducible builds in the past … perhaps it worked in a narrow
>     > corridor of
>     >     > time-zones and OS/Java versions (I did use java 1.8), but I
> simply
>     > can’t
>     >     > believe it ever was 100% reproducible.
>     >     >
>     >     > So as long as this reproducibility is a requirement, I guess
> we’re
>     > done. I
>     >     > do understand what it’s used for in this context, however I
> think
>     > it’s just
>     >     > not working.
>     >     >
>     >     > The other option would be to simply release with maven, which
> would
>     > have
>     >     > been a 1-2 hour experience for all modules.
>     >     >
>     >     > I do agree that if the steps work and all preconditions would
> be
>     > checked
>     >     > (which they currently are not) it is very easy to break the
>     > “process”. And
>     >     > it involves running 13 jobs … but as far as I got it also the
>     > execution of
>     >     > 32 manual commands for everything till step 7
>     >     > 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
>     >     >
>     >     > So as long as we’re forced to stick to this process … I guess
>     > someone else
>     >     > will have to do it.
>     >     >
>     >     > Please feel free to revert any changes I did in the last few
> months.
>     >     >
>     >     > Signing off,
>     >     > Chris
>     >     >
>     >     > PS: You really should make this ApacheRoyaleCI guy a committer
>     > considering
>     >     > the amount of emails he’s writing ;-)
>     >     >
>     >     >
>     >     >
>     >
>     >     --
>     >     Carlos Rovira
>     >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C051d4367ac9743249ec808d7d0dfd038%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207532001774243&amp;sdata=j3HnOqs9UELWlW9kQ2axZlH8mIyN9CBDOriQytA1fo8%3D&amp;reserved=0
>     >
>     >
>     >
>     >
>
>     --
>     Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C051d4367ac9743249ec808d7d0dfd038%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207532001774243&amp;sdata=j3HnOqs9UELWlW9kQ2axZlH8mIyN9CBDOriQytA1fo8%3D&amp;reserved=0
>
>
>

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

Re: Releasing: Finally giving up

Posted by Alex Harui <ah...@adobe.com.INVALID>.
I'm sorry, I must have missed something.  Where was Ant involved in any of the problems reported so far?  AFAICT, it was all Maven plugins driving our compiler and we couldn't get reproducible binaries.

I suggested in one reply that Chris fills a staging repo using his local machine just to make sure we know what Maven commands need to be run to generate all of the Maven artifacts.   And that would validate the claim that it is really doable in two or three steps.  A partial verification of validity is to check that the same set of files was produced as in 0.9.6 (there might be some new SWCs though).

Then someone else (maybe Carlos) would download all of the artifacts, run the same steps, download the new artifacts and verify that the binary match.  Then we can work on splitting those steps into chunks for the CI server.

-Alex


On 3/25/20, 10:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:

    We imposed ourselves a need to release building with two build systems.
    That's the biggest issue and that's a requirement of this PMC.
    That's what makes the need of the actual CI steps and the complex and
    intricate process.
    
    For the rest of Apache a release is:
    
    "For an *Apache* project, that means any publication outside the
    development community, defined as individuals actively participating in
    development or following the dev list. More narrowly, an official *Apache
    release* is one which has been endorsed as an "act of the Foundation" by a
    PMC."
    
    That means that we can release with ANT, with Maven, or any other build
    systems as part of the process, and even try what we're doing of trying to
    build with n build systems and try to check all is ok with the artifacts
    generated by all that build systems and check all of them...but if that's
    what we want, I personally will left this wagon, and wish you the best of
    lucks in the process.
    
    Chris and I proposed to just use Maven *for release* (so please, I expect
    no body starts to say we are throwing away ANT from the project for
    building, please....we are just discussing release here).
    
    What do you think about to try to release just with Maven? If can do in the
    next day or two and get the release published...will that work for you? I
    think we don't need anything more, and I'm sure our users will be happy too.
    
    And yes, people wanting then to build with Ant or with Maven will be able
    to do so... :-)
    
    Thanks
    
    Carlos
    
    
    [1] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease-publishing.html&amp;data=02%7C01%7Caharui%40adobe.com%7C051d4367ac9743249ec808d7d0dfd038%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207532001774243&amp;sdata=JWLztd6WGtyugYMEzRLqytO41ypZsDYQIdUhaPIMEG4%3D&amp;reserved=0
    
    
    
    El mié., 25 mar. 2020 a las 17:46, Christofer Dutz (<
    christofer.dutz@c-ware.de>) escribió:
    
    > Hi Yiashay,
    >
    > I agree ... but I didn't create Maven ... haven't even provided a single
    > PR to it ;-)
    > I think my only noticeable contribution was that they changed their
    > website to forbid the usage of "maven-{something}-plugin" to Apache Maven
    > Core modules (It initially said Apache Maven Plugins which would have
    > applied for maven-flex-plugin and maven-plc4x-plugin)
    >
    > I think you should focus not on the process, but the bases a process
    > should cover.
    >
    > Focus on what you want to be provided or ensured by any process, no matter
    > which tool it is based on.
    >
    > That's what I created the google doc for.
    >
    > If you decide to loosen the requirement on sticking 100% to the existing
    > process I am more than willing to help.
    > However if you stick to the current process, it doesn't make any sense for
    > me to do so.
    >
    > Looking forward to a productive discussion,
    >
    > Chris
    >
    >
    > Am 25.03.20, 17:36 schrieb "Yishay Weiss" <yi...@hotmail.com>:
    >
    >     I think the focus should be to agree on the requirements. Whether an
    > RM uses the tool created by Chris or Alex can be a matter of choice.
    >
    >     From: Carlos Rovira<ma...@apache.org>
    >     Sent: Wednesday, March 25, 2020 5:18 PM
    >     To: Apache Royale Development<ma...@royale.apache.org>
    >     Subject: Re: Releasing: Finally giving up
    >
    >     Hi,
    >
    >     first of all, many thanks for all the time invested by Chris this
    > days. We
    >     almost didn't have any normal life this latest 2'5 days, but as well
    > many
    >     other work (spliced in many hours in the several previous days) was
    >     prepared to start this release, so for a person out side this project,
    > I
    >     think we all should thanks a lot his dedications. The good output is
    > that
    >     process was streamlined, removing unneeded params to enter and fixing
    > many
    >     bugs over the place. That only can be performed by a good specialist in
    >     build systems like Chris, I just could be a companion to execute steps
    > and
    >     try to be trained in the process.
    >
    >     About me: I must to say that I tried hard to make this work, but I must
    >     assume I don't have the skills to do it (what is normal, since if an
    > expert
    >     in build stuff like Chris can't do it, I don't think any other one
    > could do
    >     it, and less me). The good point is that I know I have a great a deep
    >     knowledge about the overall process, and while in November I could
    >     envision, something of what I could see this days, now I have a clear
    >     knowledge of all of it (taking into account that we just go through
    >     compiler and typedefs and not framework, that could be, due to size, a
    > much
    >     bigger challenge...)
    >
    >     About the process: I must say that the initial intention was so good,
    > and I
    >     think we all want the premise offered thanks to Alex. The reality I
    > think
    >     is defeating the premise, and we should all see the reality with clear
    >     sight and without worrying about egos but just looking and what the
    > project
    >     need.
    >
    >     Since the CI process involves so many steps, manual commands in CI
    > steps,
    >     and...manual commands in local machine. One of the most annoying
    > things is
    >     the CI server hanging lots of time (the Java agent exits and that
    > means you
    >     must reboot in order the system working all again without problems).
    > The
    >     final problem is that you as a RM will fail some times in doing what
    > the
    >     process needs (indicated in emails), and although you are trained a
    > lot in
    >     how to do the project you will found stuck in some situations where you
    >     simple don't know what to do.
    >
    >     (For example I forgot or did a bad step that makes me rollover things
    > in
    >     succeed steps, so I had to roll back versions in the compiler, but
    > since I
    >     was doing a tools release too, I didn't have into account that I need
    > to
    >     roll back versions in tools too. It's clear as Chris notice that, but
    > not
    >     for me at all. So we all should know with this example that the
    > process is
    >     not automatic at all. If just involve 2-3 steps, that would be
    > manageable,
    >     but we are talking of 13 steps with 32 manual steps (until step 7),
    > plus
    >     maybe other 30 or so commands until step 13?)...hope you understand the
    >     challenge here and that is nothing easy for any of us.
    >
    >     What I mean, and my advice, from someone that loves this project and
    > want
    >     it to make it shine: We should try to simple focus in what's important.
    >     Chris is offering a way that ensures release done simple and easily. My
    >     take is that we can't afford to go this way more time, since the
    > project
    >     will see his existence threatened. We're here many years here, and this
    >     actual problem is a big one. It's clear that we have a problem if we
    > can
    >     release every month (or two month) with a process that is easy for
    > everyone
    >     and requires not a great training to do so, and will require some few
    >     commands and operations to be done. We simply can't release, and we can
    >     rely in a process that is so fragile, to make every change we do in the
    >     future will break it.
    >
    >     The fact is that we didn't get so many people jumping to Royale and the
    >     ones with an eye on this project can finally gone if we continue
    > trying to
    >     force things that we don't need. We can release just with maven in few
    >     steps, that's a fact, and we don't really need to make things in the
    > actual
    >     way. If we do is because we're forcing it, but nobody cares, and my
    > vision
    >     is that will cost the project.
    >
    >     We simplify the build Maven process to make it more reliable, that
    > break
    >     the release process in November. The build process has priority over
    > the
    >     release process, since lots of users depend on them (royale devs, and
    >     users). The release process is important in the project context to
    > offer
    >     the bits to the public as a tag or point in time.
    >
    >     We simply can't put the release process to the service of the build
    > process
    >     and make all of that stop in time to not break a fragile release
    > process.
    >     That's not an option for an open source project. The release process
    > is at
    >     the service of the rest (people, builds, code....)
    >
    >     I'd want people here to rethink all of this since:
    >
    >
    >        - We can't afford this project not to release easily monthly (or
    > every 2
    >        months) for anyone here (and I mean all people here that wants to
    > be an RM).
    >        - We can't afford so many hours invested to release, or to maintain
    > a
    >        process that is very, very, very difficult to operate, fragile and
    > easy to
    >        break.
    >
    >
    >     The motivations are:
    >
    >
    >        1. Although the process was designed and done with very good
    > intentions,
    >        the final product does not match the premise. "To make the Release
    > process
    >        affordable and reliable for each RM"
    >        2. The CI server steps needs you to work on you local machine, what
    >        defeats the premise to work just in the CI server.
    >        3. The actual process involve 13 steps instead of something more
    >        manageable like 2-3
    >        4. The actual process involve many manual commands in the CI server
    >        splitter through the 13 steps (1 to 5 commands for each step
    > depending on
    >        the step)
    >        5. The actual process involve many manual commands in your local
    > machine
    >        splittled every 3 steps. So you need to use your local machine what
    > defeats
    >        entirely the CI steps to not need the RM to configure his machine.
    > This
    >        happens in steps 3 and 7 (and fo sure later in frameworks part).
    >        6. The CI server use to hang the Jenkins java agent process that
    >        involves a reboot, what make all the process highly cumbersome. You
    > can
    >        easily get to reboot CI server 1-2 times while doing the first 3
    > steps.
    >        7. If you fail in some step (because you simply fail since you're
    > human,
    >        or the hangs and things happening make you loose the track of what
    > you're
    >        doing and make something that provoke the fail) you need to
    > rollback, and
    >        know how to operate to restore al the process, crossing fingers to
    > expect
    >        all goes well, rolling back versions, removing release branch,
    > removing
    >        tags,...)
    >        8. In the end, If you finally get all the process to work, since is
    >        very, very fragile, is very possible that some updates in the
    > future make
    >        it fail again, and the fix will required more and more hours of
    >        experimented people, patience, and testing.
    >
    >     About time. For people trained in the process, (and I think I get very
    >     trained this days). Steps 1 to 6-7 is about 1h and 30' to 2h. I think
    >     getting to step 13 and taking into account that framework is much more
    > code
    >     and time to build, I expect the global process is about 2h or maybe
    > more.
    >     So we are talking about 3'5 to 4h, of all this complicated process with
    >     lots of opportunities to fail in some of the ways already commented.
    >
    >     We have the opportunity now: Chris wanted to use the project for PCL4X
    > to
    >     build IoT apps. I think that's a huge opportunity for Royale. He's
    > giving
    >     up to use whatever other frontend tech (React, Angular, Vue,...).
    >
    >     So all this is making Royale to continue moving backwards instead to
    >     conquer new positions. I have clear that this is not the way to go,
    > and if
    >     the rest of the team wants to continue forcing all of this. I just can
    > do
    >     anything but start thinking in other options, a fork or something that
    >     ensure we are not loosing more for the years to come.
    >
    >     I still hope all of you try to think well on all of this. Remove egos,
    >     since is not about you and me, is about just Apache Royale, and nobody
    > out
    >     there cares who or what did this or that. Is just a matter of what we
    > want
    >     for Royale, since people will just see what the project can do for him.
    >
    >     Hope this long email could make you think, and hope you all will
    > comment to
    >     have clear our positions and have clear what we can expect in this
    >     problematic releasing problem, since is what will make us get more
    > traction
    >     or in reverse, end loosing more users and maybe die in the way.
    >
    >     Thanks
    >
    >     Carlos
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >     El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
    >     christofer.dutz@c-ware.de>) escribió:
    >
    >     > Hi all,
    >     >
    >     > after 3-4 days of some times 10-16 hours of working on getting the
    >     > “process” running, I’m finally giving up.
    >     > We managed to fix a lot of issues in the way the steps were setup and
    >     > managed to get to step 7 however there’s no getting past that.
    >     >
    >     > The problem are the reproducible builds.
    >     >
    >     > While for the java part I think we have all bases covered, however I
    > can’t
    >     > see however how I can fix the compiler to actually produce
    > reproducible
    >     > builds.
    >     >
    >     > We are passing in the timestamp (slightly different format, however
    > still
    >     > correct as we also adjusted the format-string). When building
    > locally, the
    >     > timestamp is exactly as the timestamp string tells the compiler. On
    > the CI
    >     > however there’s this 60 minute offset. I have explicitly set the
    > time-zone
    >     > wherever I found time-zone relevant code to UTC (Which is the
    > general best
    >     > practice for date stuff). However the offset didn’t change. So I am
    >     > completely out of ideas what could be causing this. If it really is
    > the
    >     > Summertime in the US, well I don’t know how to fix it (perhaps setup
    > a rule
    >     > to not release in this time).
    >     >
    >     > Besides that, there are still differences in the library SWF:
    >     >
    >     >   *   As I mentioned yesterday, the node typedef contains a “net”
    > object
    >     > definition in the local build and a “http” one on the CI server
    > version.
    >     >   *   In other modules it’s simply the order of items generated. I
    > guess
    >     > it’s a similar issue as the one I fixed in the build-tools, but I
    > have no
    >     > idea how to fix it in the compiler
    >     >
    >     > So in the end I’m giving up … I think the “process” is now way more
    > stable
    >     > than before, but it’s still a really fragile construct. Today Greg,
    > Carlos
    >     > and I did it together via Zoom and still we had to re-do some steps
    > because
    >     > one little preparation was missed.
    >     >
    >     > I would strongly doubt that the reproducible builds really built
    > globally
    >     > reproducible builds in the past … perhaps it worked in a narrow
    > corridor of
    >     > time-zones and OS/Java versions (I did use java 1.8), but I simply
    > can’t
    >     > believe it ever was 100% reproducible.
    >     >
    >     > So as long as this reproducibility is a requirement, I guess we’re
    > done. I
    >     > do understand what it’s used for in this context, however I think
    > it’s just
    >     > not working.
    >     >
    >     > The other option would be to simply release with maven, which would
    > have
    >     > been a 1-2 hour experience for all modules.
    >     >
    >     > I do agree that if the steps work and all preconditions would be
    > checked
    >     > (which they currently are not) it is very easy to break the
    > “process”. And
    >     > it involves running 13 jobs … but as far as I got it also the
    > execution of
    >     > 32 manual commands for everything till step 7
    >     > 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
    >     >
    >     > So as long as we’re forced to stick to this process … I guess
    > someone else
    >     > will have to do it.
    >     >
    >     > Please feel free to revert any changes I did in the last few months.
    >     >
    >     > Signing off,
    >     > Chris
    >     >
    >     > PS: You really should make this ApacheRoyaleCI guy a committer
    > considering
    >     > the amount of emails he’s writing ;-)
    >     >
    >     >
    >     >
    >
    >     --
    >     Carlos Rovira
    >     https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C051d4367ac9743249ec808d7d0dfd038%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207532001774243&amp;sdata=j3HnOqs9UELWlW9kQ2axZlH8mIyN9CBDOriQytA1fo8%3D&amp;reserved=0
    >
    >
    >
    >
    
    -- 
    Carlos Rovira
    https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C051d4367ac9743249ec808d7d0dfd038%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207532001774243&amp;sdata=j3HnOqs9UELWlW9kQ2axZlH8mIyN9CBDOriQytA1fo8%3D&amp;reserved=0
    


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
We imposed ourselves a need to release building with two build systems.
That's the biggest issue and that's a requirement of this PMC.
That's what makes the need of the actual CI steps and the complex and
intricate process.

For the rest of Apache a release is:

"For an *Apache* project, that means any publication outside the
development community, defined as individuals actively participating in
development or following the dev list. More narrowly, an official *Apache
release* is one which has been endorsed as an "act of the Foundation" by a
PMC."

That means that we can release with ANT, with Maven, or any other build
systems as part of the process, and even try what we're doing of trying to
build with n build systems and try to check all is ok with the artifacts
generated by all that build systems and check all of them...but if that's
what we want, I personally will left this wagon, and wish you the best of
lucks in the process.

Chris and I proposed to just use Maven *for release* (so please, I expect
no body starts to say we are throwing away ANT from the project for
building, please....we are just discussing release here).

What do you think about to try to release just with Maven? If can do in the
next day or two and get the release published...will that work for you? I
think we don't need anything more, and I'm sure our users will be happy too.

And yes, people wanting then to build with Ant or with Maven will be able
to do so... :-)

Thanks

Carlos


[1] http://www.apache.org/dev/release-publishing.html



El mié., 25 mar. 2020 a las 17:46, Christofer Dutz (<
christofer.dutz@c-ware.de>) escribió:

> Hi Yiashay,
>
> I agree ... but I didn't create Maven ... haven't even provided a single
> PR to it ;-)
> I think my only noticeable contribution was that they changed their
> website to forbid the usage of "maven-{something}-plugin" to Apache Maven
> Core modules (It initially said Apache Maven Plugins which would have
> applied for maven-flex-plugin and maven-plc4x-plugin)
>
> I think you should focus not on the process, but the bases a process
> should cover.
>
> Focus on what you want to be provided or ensured by any process, no matter
> which tool it is based on.
>
> That's what I created the google doc for.
>
> If you decide to loosen the requirement on sticking 100% to the existing
> process I am more than willing to help.
> However if you stick to the current process, it doesn't make any sense for
> me to do so.
>
> Looking forward to a productive discussion,
>
> Chris
>
>
> Am 25.03.20, 17:36 schrieb "Yishay Weiss" <yi...@hotmail.com>:
>
>     I think the focus should be to agree on the requirements. Whether an
> RM uses the tool created by Chris or Alex can be a matter of choice.
>
>     From: Carlos Rovira<ma...@apache.org>
>     Sent: Wednesday, March 25, 2020 5:18 PM
>     To: Apache Royale Development<ma...@royale.apache.org>
>     Subject: Re: Releasing: Finally giving up
>
>     Hi,
>
>     first of all, many thanks for all the time invested by Chris this
> days. We
>     almost didn't have any normal life this latest 2'5 days, but as well
> many
>     other work (spliced in many hours in the several previous days) was
>     prepared to start this release, so for a person out side this project,
> I
>     think we all should thanks a lot his dedications. The good output is
> that
>     process was streamlined, removing unneeded params to enter and fixing
> many
>     bugs over the place. That only can be performed by a good specialist in
>     build systems like Chris, I just could be a companion to execute steps
> and
>     try to be trained in the process.
>
>     About me: I must to say that I tried hard to make this work, but I must
>     assume I don't have the skills to do it (what is normal, since if an
> expert
>     in build stuff like Chris can't do it, I don't think any other one
> could do
>     it, and less me). The good point is that I know I have a great a deep
>     knowledge about the overall process, and while in November I could
>     envision, something of what I could see this days, now I have a clear
>     knowledge of all of it (taking into account that we just go through
>     compiler and typedefs and not framework, that could be, due to size, a
> much
>     bigger challenge...)
>
>     About the process: I must say that the initial intention was so good,
> and I
>     think we all want the premise offered thanks to Alex. The reality I
> think
>     is defeating the premise, and we should all see the reality with clear
>     sight and without worrying about egos but just looking and what the
> project
>     need.
>
>     Since the CI process involves so many steps, manual commands in CI
> steps,
>     and...manual commands in local machine. One of the most annoying
> things is
>     the CI server hanging lots of time (the Java agent exits and that
> means you
>     must reboot in order the system working all again without problems).
> The
>     final problem is that you as a RM will fail some times in doing what
> the
>     process needs (indicated in emails), and although you are trained a
> lot in
>     how to do the project you will found stuck in some situations where you
>     simple don't know what to do.
>
>     (For example I forgot or did a bad step that makes me rollover things
> in
>     succeed steps, so I had to roll back versions in the compiler, but
> since I
>     was doing a tools release too, I didn't have into account that I need
> to
>     roll back versions in tools too. It's clear as Chris notice that, but
> not
>     for me at all. So we all should know with this example that the
> process is
>     not automatic at all. If just involve 2-3 steps, that would be
> manageable,
>     but we are talking of 13 steps with 32 manual steps (until step 7),
> plus
>     maybe other 30 or so commands until step 13?)...hope you understand the
>     challenge here and that is nothing easy for any of us.
>
>     What I mean, and my advice, from someone that loves this project and
> want
>     it to make it shine: We should try to simple focus in what's important.
>     Chris is offering a way that ensures release done simple and easily. My
>     take is that we can't afford to go this way more time, since the
> project
>     will see his existence threatened. We're here many years here, and this
>     actual problem is a big one. It's clear that we have a problem if we
> can
>     release every month (or two month) with a process that is easy for
> everyone
>     and requires not a great training to do so, and will require some few
>     commands and operations to be done. We simply can't release, and we can
>     rely in a process that is so fragile, to make every change we do in the
>     future will break it.
>
>     The fact is that we didn't get so many people jumping to Royale and the
>     ones with an eye on this project can finally gone if we continue
> trying to
>     force things that we don't need. We can release just with maven in few
>     steps, that's a fact, and we don't really need to make things in the
> actual
>     way. If we do is because we're forcing it, but nobody cares, and my
> vision
>     is that will cost the project.
>
>     We simplify the build Maven process to make it more reliable, that
> break
>     the release process in November. The build process has priority over
> the
>     release process, since lots of users depend on them (royale devs, and
>     users). The release process is important in the project context to
> offer
>     the bits to the public as a tag or point in time.
>
>     We simply can't put the release process to the service of the build
> process
>     and make all of that stop in time to not break a fragile release
> process.
>     That's not an option for an open source project. The release process
> is at
>     the service of the rest (people, builds, code....)
>
>     I'd want people here to rethink all of this since:
>
>
>        - We can't afford this project not to release easily monthly (or
> every 2
>        months) for anyone here (and I mean all people here that wants to
> be an RM).
>        - We can't afford so many hours invested to release, or to maintain
> a
>        process that is very, very, very difficult to operate, fragile and
> easy to
>        break.
>
>
>     The motivations are:
>
>
>        1. Although the process was designed and done with very good
> intentions,
>        the final product does not match the premise. "To make the Release
> process
>        affordable and reliable for each RM"
>        2. The CI server steps needs you to work on you local machine, what
>        defeats the premise to work just in the CI server.
>        3. The actual process involve 13 steps instead of something more
>        manageable like 2-3
>        4. The actual process involve many manual commands in the CI server
>        splitter through the 13 steps (1 to 5 commands for each step
> depending on
>        the step)
>        5. The actual process involve many manual commands in your local
> machine
>        splittled every 3 steps. So you need to use your local machine what
> defeats
>        entirely the CI steps to not need the RM to configure his machine.
> This
>        happens in steps 3 and 7 (and fo sure later in frameworks part).
>        6. The CI server use to hang the Jenkins java agent process that
>        involves a reboot, what make all the process highly cumbersome. You
> can
>        easily get to reboot CI server 1-2 times while doing the first 3
> steps.
>        7. If you fail in some step (because you simply fail since you're
> human,
>        or the hangs and things happening make you loose the track of what
> you're
>        doing and make something that provoke the fail) you need to
> rollback, and
>        know how to operate to restore al the process, crossing fingers to
> expect
>        all goes well, rolling back versions, removing release branch,
> removing
>        tags,...)
>        8. In the end, If you finally get all the process to work, since is
>        very, very fragile, is very possible that some updates in the
> future make
>        it fail again, and the fix will required more and more hours of
>        experimented people, patience, and testing.
>
>     About time. For people trained in the process, (and I think I get very
>     trained this days). Steps 1 to 6-7 is about 1h and 30' to 2h. I think
>     getting to step 13 and taking into account that framework is much more
> code
>     and time to build, I expect the global process is about 2h or maybe
> more.
>     So we are talking about 3'5 to 4h, of all this complicated process with
>     lots of opportunities to fail in some of the ways already commented.
>
>     We have the opportunity now: Chris wanted to use the project for PCL4X
> to
>     build IoT apps. I think that's a huge opportunity for Royale. He's
> giving
>     up to use whatever other frontend tech (React, Angular, Vue,...).
>
>     So all this is making Royale to continue moving backwards instead to
>     conquer new positions. I have clear that this is not the way to go,
> and if
>     the rest of the team wants to continue forcing all of this. I just can
> do
>     anything but start thinking in other options, a fork or something that
>     ensure we are not loosing more for the years to come.
>
>     I still hope all of you try to think well on all of this. Remove egos,
>     since is not about you and me, is about just Apache Royale, and nobody
> out
>     there cares who or what did this or that. Is just a matter of what we
> want
>     for Royale, since people will just see what the project can do for him.
>
>     Hope this long email could make you think, and hope you all will
> comment to
>     have clear our positions and have clear what we can expect in this
>     problematic releasing problem, since is what will make us get more
> traction
>     or in reverse, end loosing more users and maybe die in the way.
>
>     Thanks
>
>     Carlos
>
>
>
>
>
>
>
>
>
>     El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
>     christofer.dutz@c-ware.de>) escribió:
>
>     > Hi all,
>     >
>     > after 3-4 days of some times 10-16 hours of working on getting the
>     > “process” running, I’m finally giving up.
>     > We managed to fix a lot of issues in the way the steps were setup and
>     > managed to get to step 7 however there’s no getting past that.
>     >
>     > The problem are the reproducible builds.
>     >
>     > While for the java part I think we have all bases covered, however I
> can’t
>     > see however how I can fix the compiler to actually produce
> reproducible
>     > builds.
>     >
>     > We are passing in the timestamp (slightly different format, however
> still
>     > correct as we also adjusted the format-string). When building
> locally, the
>     > timestamp is exactly as the timestamp string tells the compiler. On
> the CI
>     > however there’s this 60 minute offset. I have explicitly set the
> time-zone
>     > wherever I found time-zone relevant code to UTC (Which is the
> general best
>     > practice for date stuff). However the offset didn’t change. So I am
>     > completely out of ideas what could be causing this. If it really is
> the
>     > Summertime in the US, well I don’t know how to fix it (perhaps setup
> a rule
>     > to not release in this time).
>     >
>     > Besides that, there are still differences in the library SWF:
>     >
>     >   *   As I mentioned yesterday, the node typedef contains a “net”
> object
>     > definition in the local build and a “http” one on the CI server
> version.
>     >   *   In other modules it’s simply the order of items generated. I
> guess
>     > it’s a similar issue as the one I fixed in the build-tools, but I
> have no
>     > idea how to fix it in the compiler
>     >
>     > So in the end I’m giving up … I think the “process” is now way more
> stable
>     > than before, but it’s still a really fragile construct. Today Greg,
> Carlos
>     > and I did it together via Zoom and still we had to re-do some steps
> because
>     > one little preparation was missed.
>     >
>     > I would strongly doubt that the reproducible builds really built
> globally
>     > reproducible builds in the past … perhaps it worked in a narrow
> corridor of
>     > time-zones and OS/Java versions (I did use java 1.8), but I simply
> can’t
>     > believe it ever was 100% reproducible.
>     >
>     > So as long as this reproducibility is a requirement, I guess we’re
> done. I
>     > do understand what it’s used for in this context, however I think
> it’s just
>     > not working.
>     >
>     > The other option would be to simply release with maven, which would
> have
>     > been a 1-2 hour experience for all modules.
>     >
>     > I do agree that if the steps work and all preconditions would be
> checked
>     > (which they currently are not) it is very easy to break the
> “process”. And
>     > it involves running 13 jobs … but as far as I got it also the
> execution of
>     > 32 manual commands for everything till step 7
>     > 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
>     >
>     > So as long as we’re forced to stick to this process … I guess
> someone else
>     > will have to do it.
>     >
>     > Please feel free to revert any changes I did in the last few months.
>     >
>     > Signing off,
>     > Chris
>     >
>     > PS: You really should make this ApacheRoyaleCI guy a committer
> considering
>     > the amount of emails he’s writing ;-)
>     >
>     >
>     >
>
>     --
>     Carlos Rovira
>     http://about.me/carlosrovira
>
>
>
>

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

Re: Releasing: Finally giving up

Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Yiashay,

I agree ... but I didn't create Maven ... haven't even provided a single PR to it ;-)
I think my only noticeable contribution was that they changed their website to forbid the usage of "maven-{something}-plugin" to Apache Maven Core modules (It initially said Apache Maven Plugins which would have applied for maven-flex-plugin and maven-plc4x-plugin)

I think you should focus not on the process, but the bases a process should cover.

Focus on what you want to be provided or ensured by any process, no matter which tool it is based on. 

That's what I created the google doc for.

If you decide to loosen the requirement on sticking 100% to the existing process I am more than willing to help.
However if you stick to the current process, it doesn't make any sense for me to do so.

Looking forward to a productive discussion,

Chris


Am 25.03.20, 17:36 schrieb "Yishay Weiss" <yi...@hotmail.com>:

    I think the focus should be to agree on the requirements. Whether an RM uses the tool created by Chris or Alex can be a matter of choice.
    
    From: Carlos Rovira<ma...@apache.org>
    Sent: Wednesday, March 25, 2020 5:18 PM
    To: Apache Royale Development<ma...@royale.apache.org>
    Subject: Re: Releasing: Finally giving up
    
    Hi,
    
    first of all, many thanks for all the time invested by Chris this days. We
    almost didn't have any normal life this latest 2'5 days, but as well many
    other work (spliced in many hours in the several previous days) was
    prepared to start this release, so for a person out side this project, I
    think we all should thanks a lot his dedications. The good output is that
    process was streamlined, removing unneeded params to enter and fixing many
    bugs over the place. That only can be performed by a good specialist in
    build systems like Chris, I just could be a companion to execute steps and
    try to be trained in the process.
    
    About me: I must to say that I tried hard to make this work, but I must
    assume I don't have the skills to do it (what is normal, since if an expert
    in build stuff like Chris can't do it, I don't think any other one could do
    it, and less me). The good point is that I know I have a great a deep
    knowledge about the overall process, and while in November I could
    envision, something of what I could see this days, now I have a clear
    knowledge of all of it (taking into account that we just go through
    compiler and typedefs and not framework, that could be, due to size, a much
    bigger challenge...)
    
    About the process: I must say that the initial intention was so good, and I
    think we all want the premise offered thanks to Alex. The reality I think
    is defeating the premise, and we should all see the reality with clear
    sight and without worrying about egos but just looking and what the project
    need.
    
    Since the CI process involves so many steps, manual commands in CI steps,
    and...manual commands in local machine. One of the most annoying things is
    the CI server hanging lots of time (the Java agent exits and that means you
    must reboot in order the system working all again without problems). The
    final problem is that you as a RM will fail some times in doing what the
    process needs (indicated in emails), and although you are trained a lot in
    how to do the project you will found stuck in some situations where you
    simple don't know what to do.
    
    (For example I forgot or did a bad step that makes me rollover things in
    succeed steps, so I had to roll back versions in the compiler, but since I
    was doing a tools release too, I didn't have into account that I need to
    roll back versions in tools too. It's clear as Chris notice that, but not
    for me at all. So we all should know with this example that the process is
    not automatic at all. If just involve 2-3 steps, that would be manageable,
    but we are talking of 13 steps with 32 manual steps (until step 7), plus
    maybe other 30 or so commands until step 13?)...hope you understand the
    challenge here and that is nothing easy for any of us.
    
    What I mean, and my advice, from someone that loves this project and want
    it to make it shine: We should try to simple focus in what's important.
    Chris is offering a way that ensures release done simple and easily. My
    take is that we can't afford to go this way more time, since the project
    will see his existence threatened. We're here many years here, and this
    actual problem is a big one. It's clear that we have a problem if we can
    release every month (or two month) with a process that is easy for everyone
    and requires not a great training to do so, and will require some few
    commands and operations to be done. We simply can't release, and we can
    rely in a process that is so fragile, to make every change we do in the
    future will break it.
    
    The fact is that we didn't get so many people jumping to Royale and the
    ones with an eye on this project can finally gone if we continue trying to
    force things that we don't need. We can release just with maven in few
    steps, that's a fact, and we don't really need to make things in the actual
    way. If we do is because we're forcing it, but nobody cares, and my vision
    is that will cost the project.
    
    We simplify the build Maven process to make it more reliable, that break
    the release process in November. The build process has priority over the
    release process, since lots of users depend on them (royale devs, and
    users). The release process is important in the project context to offer
    the bits to the public as a tag or point in time.
    
    We simply can't put the release process to the service of the build process
    and make all of that stop in time to not break a fragile release process.
    That's not an option for an open source project. The release process is at
    the service of the rest (people, builds, code....)
    
    I'd want people here to rethink all of this since:
    
    
       - We can't afford this project not to release easily monthly (or every 2
       months) for anyone here (and I mean all people here that wants to be an RM).
       - We can't afford so many hours invested to release, or to maintain a
       process that is very, very, very difficult to operate, fragile and easy to
       break.
    
    
    The motivations are:
    
    
       1. Although the process was designed and done with very good intentions,
       the final product does not match the premise. "To make the Release process
       affordable and reliable for each RM"
       2. The CI server steps needs you to work on you local machine, what
       defeats the premise to work just in the CI server.
       3. The actual process involve 13 steps instead of something more
       manageable like 2-3
       4. The actual process involve many manual commands in the CI server
       splitter through the 13 steps (1 to 5 commands for each step depending on
       the step)
       5. The actual process involve many manual commands in your local machine
       splittled every 3 steps. So you need to use your local machine what defeats
       entirely the CI steps to not need the RM to configure his machine. This
       happens in steps 3 and 7 (and fo sure later in frameworks part).
       6. The CI server use to hang the Jenkins java agent process that
       involves a reboot, what make all the process highly cumbersome. You can
       easily get to reboot CI server 1-2 times while doing the first 3 steps.
       7. If you fail in some step (because you simply fail since you're human,
       or the hangs and things happening make you loose the track of what you're
       doing and make something that provoke the fail) you need to rollback, and
       know how to operate to restore al the process, crossing fingers to expect
       all goes well, rolling back versions, removing release branch, removing
       tags,...)
       8. In the end, If you finally get all the process to work, since is
       very, very fragile, is very possible that some updates in the future make
       it fail again, and the fix will required more and more hours of
       experimented people, patience, and testing.
    
    About time. For people trained in the process, (and I think I get very
    trained this days). Steps 1 to 6-7 is about 1h and 30' to 2h. I think
    getting to step 13 and taking into account that framework is much more code
    and time to build, I expect the global process is about 2h or maybe more.
    So we are talking about 3'5 to 4h, of all this complicated process with
    lots of opportunities to fail in some of the ways already commented.
    
    We have the opportunity now: Chris wanted to use the project for PCL4X to
    build IoT apps. I think that's a huge opportunity for Royale. He's giving
    up to use whatever other frontend tech (React, Angular, Vue,...).
    
    So all this is making Royale to continue moving backwards instead to
    conquer new positions. I have clear that this is not the way to go, and if
    the rest of the team wants to continue forcing all of this. I just can do
    anything but start thinking in other options, a fork or something that
    ensure we are not loosing more for the years to come.
    
    I still hope all of you try to think well on all of this. Remove egos,
    since is not about you and me, is about just Apache Royale, and nobody out
    there cares who or what did this or that. Is just a matter of what we want
    for Royale, since people will just see what the project can do for him.
    
    Hope this long email could make you think, and hope you all will comment to
    have clear our positions and have clear what we can expect in this
    problematic releasing problem, since is what will make us get more traction
    or in reverse, end loosing more users and maybe die in the way.
    
    Thanks
    
    Carlos
    
    
    
    
    
    
    
    
    
    El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
    christofer.dutz@c-ware.de>) escribió:
    
    > Hi all,
    >
    > after 3-4 days of some times 10-16 hours of working on getting the
    > “process” running, I’m finally giving up.
    > We managed to fix a lot of issues in the way the steps were setup and
    > managed to get to step 7 however there’s no getting past that.
    >
    > The problem are the reproducible builds.
    >
    > While for the java part I think we have all bases covered, however I can’t
    > see however how I can fix the compiler to actually produce reproducible
    > builds.
    >
    > We are passing in the timestamp (slightly different format, however still
    > correct as we also adjusted the format-string). When building locally, the
    > timestamp is exactly as the timestamp string tells the compiler. On the CI
    > however there’s this 60 minute offset. I have explicitly set the time-zone
    > wherever I found time-zone relevant code to UTC (Which is the general best
    > practice for date stuff). However the offset didn’t change. So I am
    > completely out of ideas what could be causing this. If it really is the
    > Summertime in the US, well I don’t know how to fix it (perhaps setup a rule
    > to not release in this time).
    >
    > Besides that, there are still differences in the library SWF:
    >
    >   *   As I mentioned yesterday, the node typedef contains a “net” object
    > definition in the local build and a “http” one on the CI server version.
    >   *   In other modules it’s simply the order of items generated. I guess
    > it’s a similar issue as the one I fixed in the build-tools, but I have no
    > idea how to fix it in the compiler
    >
    > So in the end I’m giving up … I think the “process” is now way more stable
    > than before, but it’s still a really fragile construct. Today Greg, Carlos
    > and I did it together via Zoom and still we had to re-do some steps because
    > one little preparation was missed.
    >
    > I would strongly doubt that the reproducible builds really built globally
    > reproducible builds in the past … perhaps it worked in a narrow corridor of
    > time-zones and OS/Java versions (I did use java 1.8), but I simply can’t
    > believe it ever was 100% reproducible.
    >
    > So as long as this reproducibility is a requirement, I guess we’re done. I
    > do understand what it’s used for in this context, however I think it’s just
    > not working.
    >
    > The other option would be to simply release with maven, which would have
    > been a 1-2 hour experience for all modules.
    >
    > I do agree that if the steps work and all preconditions would be checked
    > (which they currently are not) it is very easy to break the “process”. And
    > it involves running 13 jobs … but as far as I got it also the execution of
    > 32 manual commands for everything till step 7
    > 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
    >
    > So as long as we’re forced to stick to this process … I guess someone else
    > will have to do it.
    >
    > Please feel free to revert any changes I did in the last few months.
    >
    > Signing off,
    > Chris
    >
    > PS: You really should make this ApacheRoyaleCI guy a committer considering
    > the amount of emails he’s writing ;-)
    >
    >
    >
    
    --
    Carlos Rovira
    http://about.me/carlosrovira
    
    


RE: Releasing: Finally giving up

Posted by Yishay Weiss <yi...@hotmail.com>.
I think the focus should be to agree on the requirements. Whether an RM uses the tool created by Chris or Alex can be a matter of choice.

From: Carlos Rovira<ma...@apache.org>
Sent: Wednesday, March 25, 2020 5:18 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Releasing: Finally giving up

Hi,

first of all, many thanks for all the time invested by Chris this days. We
almost didn't have any normal life this latest 2'5 days, but as well many
other work (spliced in many hours in the several previous days) was
prepared to start this release, so for a person out side this project, I
think we all should thanks a lot his dedications. The good output is that
process was streamlined, removing unneeded params to enter and fixing many
bugs over the place. That only can be performed by a good specialist in
build systems like Chris, I just could be a companion to execute steps and
try to be trained in the process.

About me: I must to say that I tried hard to make this work, but I must
assume I don't have the skills to do it (what is normal, since if an expert
in build stuff like Chris can't do it, I don't think any other one could do
it, and less me). The good point is that I know I have a great a deep
knowledge about the overall process, and while in November I could
envision, something of what I could see this days, now I have a clear
knowledge of all of it (taking into account that we just go through
compiler and typedefs and not framework, that could be, due to size, a much
bigger challenge...)

About the process: I must say that the initial intention was so good, and I
think we all want the premise offered thanks to Alex. The reality I think
is defeating the premise, and we should all see the reality with clear
sight and without worrying about egos but just looking and what the project
need.

Since the CI process involves so many steps, manual commands in CI steps,
and...manual commands in local machine. One of the most annoying things is
the CI server hanging lots of time (the Java agent exits and that means you
must reboot in order the system working all again without problems). The
final problem is that you as a RM will fail some times in doing what the
process needs (indicated in emails), and although you are trained a lot in
how to do the project you will found stuck in some situations where you
simple don't know what to do.

(For example I forgot or did a bad step that makes me rollover things in
succeed steps, so I had to roll back versions in the compiler, but since I
was doing a tools release too, I didn't have into account that I need to
roll back versions in tools too. It's clear as Chris notice that, but not
for me at all. So we all should know with this example that the process is
not automatic at all. If just involve 2-3 steps, that would be manageable,
but we are talking of 13 steps with 32 manual steps (until step 7), plus
maybe other 30 or so commands until step 13?)...hope you understand the
challenge here and that is nothing easy for any of us.

What I mean, and my advice, from someone that loves this project and want
it to make it shine: We should try to simple focus in what's important.
Chris is offering a way that ensures release done simple and easily. My
take is that we can't afford to go this way more time, since the project
will see his existence threatened. We're here many years here, and this
actual problem is a big one. It's clear that we have a problem if we can
release every month (or two month) with a process that is easy for everyone
and requires not a great training to do so, and will require some few
commands and operations to be done. We simply can't release, and we can
rely in a process that is so fragile, to make every change we do in the
future will break it.

The fact is that we didn't get so many people jumping to Royale and the
ones with an eye on this project can finally gone if we continue trying to
force things that we don't need. We can release just with maven in few
steps, that's a fact, and we don't really need to make things in the actual
way. If we do is because we're forcing it, but nobody cares, and my vision
is that will cost the project.

We simplify the build Maven process to make it more reliable, that break
the release process in November. The build process has priority over the
release process, since lots of users depend on them (royale devs, and
users). The release process is important in the project context to offer
the bits to the public as a tag or point in time.

We simply can't put the release process to the service of the build process
and make all of that stop in time to not break a fragile release process.
That's not an option for an open source project. The release process is at
the service of the rest (people, builds, code....)

I'd want people here to rethink all of this since:


   - We can't afford this project not to release easily monthly (or every 2
   months) for anyone here (and I mean all people here that wants to be an RM).
   - We can't afford so many hours invested to release, or to maintain a
   process that is very, very, very difficult to operate, fragile and easy to
   break.


The motivations are:


   1. Although the process was designed and done with very good intentions,
   the final product does not match the premise. "To make the Release process
   affordable and reliable for each RM"
   2. The CI server steps needs you to work on you local machine, what
   defeats the premise to work just in the CI server.
   3. The actual process involve 13 steps instead of something more
   manageable like 2-3
   4. The actual process involve many manual commands in the CI server
   splitter through the 13 steps (1 to 5 commands for each step depending on
   the step)
   5. The actual process involve many manual commands in your local machine
   splittled every 3 steps. So you need to use your local machine what defeats
   entirely the CI steps to not need the RM to configure his machine. This
   happens in steps 3 and 7 (and fo sure later in frameworks part).
   6. The CI server use to hang the Jenkins java agent process that
   involves a reboot, what make all the process highly cumbersome. You can
   easily get to reboot CI server 1-2 times while doing the first 3 steps.
   7. If you fail in some step (because you simply fail since you're human,
   or the hangs and things happening make you loose the track of what you're
   doing and make something that provoke the fail) you need to rollback, and
   know how to operate to restore al the process, crossing fingers to expect
   all goes well, rolling back versions, removing release branch, removing
   tags,...)
   8. In the end, If you finally get all the process to work, since is
   very, very fragile, is very possible that some updates in the future make
   it fail again, and the fix will required more and more hours of
   experimented people, patience, and testing.

About time. For people trained in the process, (and I think I get very
trained this days). Steps 1 to 6-7 is about 1h and 30' to 2h. I think
getting to step 13 and taking into account that framework is much more code
and time to build, I expect the global process is about 2h or maybe more.
So we are talking about 3'5 to 4h, of all this complicated process with
lots of opportunities to fail in some of the ways already commented.

We have the opportunity now: Chris wanted to use the project for PCL4X to
build IoT apps. I think that's a huge opportunity for Royale. He's giving
up to use whatever other frontend tech (React, Angular, Vue,...).

So all this is making Royale to continue moving backwards instead to
conquer new positions. I have clear that this is not the way to go, and if
the rest of the team wants to continue forcing all of this. I just can do
anything but start thinking in other options, a fork or something that
ensure we are not loosing more for the years to come.

I still hope all of you try to think well on all of this. Remove egos,
since is not about you and me, is about just Apache Royale, and nobody out
there cares who or what did this or that. Is just a matter of what we want
for Royale, since people will just see what the project can do for him.

Hope this long email could make you think, and hope you all will comment to
have clear our positions and have clear what we can expect in this
problematic releasing problem, since is what will make us get more traction
or in reverse, end loosing more users and maybe die in the way.

Thanks

Carlos









El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
christofer.dutz@c-ware.de>) escribió:

> Hi all,
>
> after 3-4 days of some times 10-16 hours of working on getting the
> “process” running, I’m finally giving up.
> We managed to fix a lot of issues in the way the steps were setup and
> managed to get to step 7 however there’s no getting past that.
>
> The problem are the reproducible builds.
>
> While for the java part I think we have all bases covered, however I can’t
> see however how I can fix the compiler to actually produce reproducible
> builds.
>
> We are passing in the timestamp (slightly different format, however still
> correct as we also adjusted the format-string). When building locally, the
> timestamp is exactly as the timestamp string tells the compiler. On the CI
> however there’s this 60 minute offset. I have explicitly set the time-zone
> wherever I found time-zone relevant code to UTC (Which is the general best
> practice for date stuff). However the offset didn’t change. So I am
> completely out of ideas what could be causing this. If it really is the
> Summertime in the US, well I don’t know how to fix it (perhaps setup a rule
> to not release in this time).
>
> Besides that, there are still differences in the library SWF:
>
>   *   As I mentioned yesterday, the node typedef contains a “net” object
> definition in the local build and a “http” one on the CI server version.
>   *   In other modules it’s simply the order of items generated. I guess
> it’s a similar issue as the one I fixed in the build-tools, but I have no
> idea how to fix it in the compiler
>
> So in the end I’m giving up … I think the “process” is now way more stable
> than before, but it’s still a really fragile construct. Today Greg, Carlos
> and I did it together via Zoom and still we had to re-do some steps because
> one little preparation was missed.
>
> I would strongly doubt that the reproducible builds really built globally
> reproducible builds in the past … perhaps it worked in a narrow corridor of
> time-zones and OS/Java versions (I did use java 1.8), but I simply can’t
> believe it ever was 100% reproducible.
>
> So as long as this reproducibility is a requirement, I guess we’re done. I
> do understand what it’s used for in this context, however I think it’s just
> not working.
>
> The other option would be to simply release with maven, which would have
> been a 1-2 hour experience for all modules.
>
> I do agree that if the steps work and all preconditions would be checked
> (which they currently are not) it is very easy to break the “process”. And
> it involves running 13 jobs … but as far as I got it also the execution of
> 32 manual commands for everything till step 7
> 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
>
> So as long as we’re forced to stick to this process … I guess someone else
> will have to do it.
>
> Please feel free to revert any changes I did in the last few months.
>
> Signing off,
> Chris
>
> PS: You really should make this ApacheRoyaleCI guy a committer considering
> the amount of emails he’s writing ;-)
>
>
>

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


Re: Releasing: Finally giving up

Posted by Carlos Rovira <ca...@apache.org>.
Hi,

first of all, many thanks for all the time invested by Chris this days. We
almost didn't have any normal life this latest 2'5 days, but as well many
other work (spliced in many hours in the several previous days) was
prepared to start this release, so for a person out side this project, I
think we all should thanks a lot his dedications. The good output is that
process was streamlined, removing unneeded params to enter and fixing many
bugs over the place. That only can be performed by a good specialist in
build systems like Chris, I just could be a companion to execute steps and
try to be trained in the process.

About me: I must to say that I tried hard to make this work, but I must
assume I don't have the skills to do it (what is normal, since if an expert
in build stuff like Chris can't do it, I don't think any other one could do
it, and less me). The good point is that I know I have a great a deep
knowledge about the overall process, and while in November I could
envision, something of what I could see this days, now I have a clear
knowledge of all of it (taking into account that we just go through
compiler and typedefs and not framework, that could be, due to size, a much
bigger challenge...)

About the process: I must say that the initial intention was so good, and I
think we all want the premise offered thanks to Alex. The reality I think
is defeating the premise, and we should all see the reality with clear
sight and without worrying about egos but just looking and what the project
need.

Since the CI process involves so many steps, manual commands in CI steps,
and...manual commands in local machine. One of the most annoying things is
the CI server hanging lots of time (the Java agent exits and that means you
must reboot in order the system working all again without problems). The
final problem is that you as a RM will fail some times in doing what the
process needs (indicated in emails), and although you are trained a lot in
how to do the project you will found stuck in some situations where you
simple don't know what to do.

(For example I forgot or did a bad step that makes me rollover things in
succeed steps, so I had to roll back versions in the compiler, but since I
was doing a tools release too, I didn't have into account that I need to
roll back versions in tools too. It's clear as Chris notice that, but not
for me at all. So we all should know with this example that the process is
not automatic at all. If just involve 2-3 steps, that would be manageable,
but we are talking of 13 steps with 32 manual steps (until step 7), plus
maybe other 30 or so commands until step 13?)...hope you understand the
challenge here and that is nothing easy for any of us.

What I mean, and my advice, from someone that loves this project and want
it to make it shine: We should try to simple focus in what's important.
Chris is offering a way that ensures release done simple and easily. My
take is that we can't afford to go this way more time, since the project
will see his existence threatened. We're here many years here, and this
actual problem is a big one. It's clear that we have a problem if we can
release every month (or two month) with a process that is easy for everyone
and requires not a great training to do so, and will require some few
commands and operations to be done. We simply can't release, and we can
rely in a process that is so fragile, to make every change we do in the
future will break it.

The fact is that we didn't get so many people jumping to Royale and the
ones with an eye on this project can finally gone if we continue trying to
force things that we don't need. We can release just with maven in few
steps, that's a fact, and we don't really need to make things in the actual
way. If we do is because we're forcing it, but nobody cares, and my vision
is that will cost the project.

We simplify the build Maven process to make it more reliable, that break
the release process in November. The build process has priority over the
release process, since lots of users depend on them (royale devs, and
users). The release process is important in the project context to offer
the bits to the public as a tag or point in time.

We simply can't put the release process to the service of the build process
and make all of that stop in time to not break a fragile release process.
That's not an option for an open source project. The release process is at
the service of the rest (people, builds, code....)

I'd want people here to rethink all of this since:


   - We can't afford this project not to release easily monthly (or every 2
   months) for anyone here (and I mean all people here that wants to be an RM).
   - We can't afford so many hours invested to release, or to maintain a
   process that is very, very, very difficult to operate, fragile and easy to
   break.


The motivations are:


   1. Although the process was designed and done with very good intentions,
   the final product does not match the premise. "To make the Release process
   affordable and reliable for each RM"
   2. The CI server steps needs you to work on you local machine, what
   defeats the premise to work just in the CI server.
   3. The actual process involve 13 steps instead of something more
   manageable like 2-3
   4. The actual process involve many manual commands in the CI server
   splitter through the 13 steps (1 to 5 commands for each step depending on
   the step)
   5. The actual process involve many manual commands in your local machine
   splittled every 3 steps. So you need to use your local machine what defeats
   entirely the CI steps to not need the RM to configure his machine. This
   happens in steps 3 and 7 (and fo sure later in frameworks part).
   6. The CI server use to hang the Jenkins java agent process that
   involves a reboot, what make all the process highly cumbersome. You can
   easily get to reboot CI server 1-2 times while doing the first 3 steps.
   7. If you fail in some step (because you simply fail since you're human,
   or the hangs and things happening make you loose the track of what you're
   doing and make something that provoke the fail) you need to rollback, and
   know how to operate to restore al the process, crossing fingers to expect
   all goes well, rolling back versions, removing release branch, removing
   tags,...)
   8. In the end, If you finally get all the process to work, since is
   very, very fragile, is very possible that some updates in the future make
   it fail again, and the fix will required more and more hours of
   experimented people, patience, and testing.

About time. For people trained in the process, (and I think I get very
trained this days). Steps 1 to 6-7 is about 1h and 30' to 2h. I think
getting to step 13 and taking into account that framework is much more code
and time to build, I expect the global process is about 2h or maybe more.
So we are talking about 3'5 to 4h, of all this complicated process with
lots of opportunities to fail in some of the ways already commented.

We have the opportunity now: Chris wanted to use the project for PCL4X to
build IoT apps. I think that's a huge opportunity for Royale. He's giving
up to use whatever other frontend tech (React, Angular, Vue,...).

So all this is making Royale to continue moving backwards instead to
conquer new positions. I have clear that this is not the way to go, and if
the rest of the team wants to continue forcing all of this. I just can do
anything but start thinking in other options, a fork or something that
ensure we are not loosing more for the years to come.

I still hope all of you try to think well on all of this. Remove egos,
since is not about you and me, is about just Apache Royale, and nobody out
there cares who or what did this or that. Is just a matter of what we want
for Royale, since people will just see what the project can do for him.

Hope this long email could make you think, and hope you all will comment to
have clear our positions and have clear what we can expect in this
problematic releasing problem, since is what will make us get more traction
or in reverse, end loosing more users and maybe die in the way.

Thanks

Carlos









El mié., 25 mar. 2020 a las 12:39, Christofer Dutz (<
christofer.dutz@c-ware.de>) escribió:

> Hi all,
>
> after 3-4 days of some times 10-16 hours of working on getting the
> “process” running, I’m finally giving up.
> We managed to fix a lot of issues in the way the steps were setup and
> managed to get to step 7 however there’s no getting past that.
>
> The problem are the reproducible builds.
>
> While for the java part I think we have all bases covered, however I can’t
> see however how I can fix the compiler to actually produce reproducible
> builds.
>
> We are passing in the timestamp (slightly different format, however still
> correct as we also adjusted the format-string). When building locally, the
> timestamp is exactly as the timestamp string tells the compiler. On the CI
> however there’s this 60 minute offset. I have explicitly set the time-zone
> wherever I found time-zone relevant code to UTC (Which is the general best
> practice for date stuff). However the offset didn’t change. So I am
> completely out of ideas what could be causing this. If it really is the
> Summertime in the US, well I don’t know how to fix it (perhaps setup a rule
> to not release in this time).
>
> Besides that, there are still differences in the library SWF:
>
>   *   As I mentioned yesterday, the node typedef contains a “net” object
> definition in the local build and a “http” one on the CI server version.
>   *   In other modules it’s simply the order of items generated. I guess
> it’s a similar issue as the one I fixed in the build-tools, but I have no
> idea how to fix it in the compiler
>
> So in the end I’m giving up … I think the “process” is now way more stable
> than before, but it’s still a really fragile construct. Today Greg, Carlos
> and I did it together via Zoom and still we had to re-do some steps because
> one little preparation was missed.
>
> I would strongly doubt that the reproducible builds really built globally
> reproducible builds in the past … perhaps it worked in a narrow corridor of
> time-zones and OS/Java versions (I did use java 1.8), but I simply can’t
> believe it ever was 100% reproducible.
>
> So as long as this reproducibility is a requirement, I guess we’re done. I
> do understand what it’s used for in this context, however I think it’s just
> not working.
>
> The other option would be to simply release with maven, which would have
> been a 1-2 hour experience for all modules.
>
> I do agree that if the steps work and all preconditions would be checked
> (which they currently are not) it is very easy to break the “process”. And
> it involves running 13 jobs … but as far as I got it also the execution of
> 32 manual commands for everything till step 7
> 4 + 6 + 3 + 3 + 3 + 4 + 2 + 3 + 3 = 32
>
> So as long as we’re forced to stick to this process … I guess someone else
> will have to do it.
>
> Please feel free to revert any changes I did in the last few months.
>
> Signing off,
> Chris
>
> PS: You really should make this ApacheRoyaleCI guy a committer considering
> the amount of emails he’s writing ;-)
>
>
>

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

Re: Releasing: Finally giving up

Posted by OmPrakash Muppirala <bi...@gmail.com>.
>
>
>
>
> We are passing in the timestamp (slightly different format, however still
> correct as we also adjusted the format-string). When building locally, the
> timestamp is exactly as the timestamp string tells the compiler. On the CI
> however there’s this 60 minute offset. I have explicitly set the time-zone
> wherever I found time-zone relevant code to UTC (Which is the general best
> practice for date stuff). However the offset didn’t change. So I am
> completely out of ideas what could be causing this. If it really is the
> Summertime in the US, well I don’t know how to fix it (perhaps setup a rule
> to not release in this time).
>

Thanks for all the hard work.  It is really appreciated!
Dumb question - have you tried setting the computer date/time manually on
the server to match what you have?  Just see if the problem goes away?

Thanks,
Om