You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Piotr Zarzycki <pi...@gmail.com> on 2019/10/01 07:25:41 UTC
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Hi Harbs,
I think we have enough votes. I still have to gather info how actually
release Maven artifacts. However I'm going to push binaries today in svn.
Thanks,
Piotr
sob., 28 wrz 2019 o 20:02 Harbs <ha...@gmail.com> napisał(a):
> FYI, I will not be able to test the release until Wednesday.
>
> If the vote is still open, I plan on testing then.
>
> Thanks,
> Harbs
>
> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <pi...@gmail.com>
> wrote:
> >
> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript myself
> > yet, but will do that tomorrow or next week.
> >
> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
> apacheroyaleci@gmail.com>
> > napisał(a):
> >
> >> This is the discussion thread.
> >>
> >> Thanks,
> >> Piotr
> >
> >
> >
> > --
> >
> > 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: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
yes, I already did some days ago an uploaded to website
If you search for some new class (like jewel SimpleButton) it appears now.
El jue., 10 oct. 2019 a las 11:49, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Hi Carlos,
>
> Did you make an update API doc ? ->
> https://royale.apache.org/asdoc/index.html
>
> Thanks,
> Piotr
>
> pon., 7 paź 2019 o 19:38 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Piotr,
> > yes, I'll do in next few hours.
> > thanks.
> >
> > El lun., 7 oct. 2019 a las 9:54, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>)
> > escribió:
> >
> > > Hi Carlos,
> > >
> > > Will you be able update website with links for 0.9.6 release ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > niedz., 6 paź 2019 o 10:52 Piotr Zarzycki <pi...@gmail.com>
> > > napisał(a):
> > >
> > > > Hi Alex,
> > > >
> > > > Thank you for the fix. Everything worked fine this time.
> > > >
> > > > Piotr
> > > >
> > > > sob., 5 paź 2019 o 01:51 Alex Harui <ah...@adobe.com.invalid>
> > > napisał(a):
> > > >
> > > >> I found some time to try the releasecandidate.xml and found the
> > problem.
> > > >> I pushed the fix to release/0.9.6. So try that and see what
> happens.
> > > >> It seemed to do the right thing for me on my Windows computer.
> > > >>
> > > >> You will next likely run into several merge conflicts. I have not
> > > looked
> > > >> into the conflicts, but there is a good chance that some of that is
> > due
> > > to
> > > >> the cherry-picking. I am going to start a separate thread about
> > branch
> > > >> management.
> > > >>
> > > >> -Alex
> > > >>
> > > >> On 10/4/19, 10:55 AM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> > > >>
> > > >> If we don't fix the release scripts, then the next RM is
> probably
> > > >> going to run into the same problem. The time we spend now helps
> save
> > > time
> > > >> in the future. It is wise to improve the process now in case I get
> > run
> > > >> over by a bus tomorrow. If you do it manually and make a mistake,
> we
> > > might
> > > >> not catch it until later or cause more problems.
> > > >>
> > > >> IIRC, the Poms should not require changing. Maven should have
> > done
> > > >> that already.
> > > >>
> > > >> All the places I know of changing are in the script.
> > > >>
> > > >> -Alex
> > > >>
> > > >> On 10/4/19, 10:46 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com
> > >
> > > >> wrote:
> > > >>
> > > >> Alex,
> > > >>
> > > >> Can I just do that changes manually on release branch and
> > merge
> > > >> stuff to
> > > >> develop?
> > > >>
> > > >> I just don't won't to spend any more minute on release
> process
> > > >> anymore.
> > > >>
> > > >> 1) I should change build properties
> > > >> 2) I should change all poms
> > > >>
> > > >> Is there anymore place which I should know to change?
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >>
> > > >> On Fri, Oct 4, 2019, 7:41 PM Alex Harui
> > > <ah...@adobe.com.invalid>
> > > >> wrote:
> > > >>
> > > >> > Piotr,
> > > >> >
> > > >> > Again, I am asking you to get in the mindset of a
> developer
> > > and
> > > >> not just a
> > > >> > user. You can see that the Ant script is making some
> > updates.
> > > >> You can
> > > >> > verify that the release branch does not have 0.9.7 for the
> > > >> release.version
> > > >> > in build.properties. You can see there is 1 commit
> pending
> > in
> > > >> > royale-asjs. You can see that the build.properties did
> get
> > > >> changed to have
> > > >> > release.version=0.9.7.
> > > >> >
> > > >> > So, you will have to investigate further. What is in that
> > > >> commit? Is
> > > >> > this output from a fresh start of cloning the repo or
> could
> > > >> that commit be
> > > >> > from a previous run? How could Git change a file but not
> > > >> report it? Maybe
> > > >> > add some <echo> tags or use -verbose to get more output.
> > But
> > > >> just giving
> > > >> > me minimal information and waiting for me to guess as to
> > what
> > > >> to do next is
> > > >> > not very efficient, IMO.
> > > >> >
> > > >> > Thanks,
> > > >> > -Alex
> > > >> >
> > > >> > On 10/4/19, 4:01 AM, "Piotr Zarzycki" <
> > > >> piotrzarzycki21@gmail.com> wrote:
> > > >> >
> > > >> > Hi Alex,
> > > >> >
> > > >> > Git status after failing for all 3 repos [1].
> > > >> >
> > > >> > Here is how build.properties look like after
> performing
> > > >> update.versions
> > > >> > target [2].
> > > >> >
> > > >> > I will skip some part to move forward but
> > update.versions
> > > >> is important.
> > > >> >
> > > >> > [1]
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=nvSDESjmBw5j%2FlBoaIPGTUiBKrkoXcAVGIyUV371eE8%3D&reserved=0
> > > >> > [2]
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvou&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=ljQmwiJbtqsTIj3tx9%2FtKyy%2Bns5Sz7P%2BCQE3Knb%2F1fA%3D&reserved=0
> > > >> >
> > > >> > Thanks,
> > > >> > Piotr
> > > >> >
> > > >> > czw., 3 paź 2019 o 17:49 Alex Harui
> > > >> <ah...@adobe.com.invalid>
> > > >> > napisał(a):
> > > >> >
> > > >> > > What does "git status" show in the 3 repos?
> > > >> > >
> > > >> > > The update.versions should have at least changed the
> > > >> > build.properties file
> > > >> > > in the repo.
> > > >> > >
> > > >> > > You can try skipping over steps by listing the steps
> > on
> > > >> the command
> > > >> > line.
> > > >> > > You might need to list some pre-requisite steps
> before
> > > or
> > > >> add them
> > > >> > to the
> > > >> > > "depends" of the step that needs it.
> > > >> > >
> > > >> > > ant -e -f releasecandidate.xml
> -Drelease.version=0.9.6
> > > >> -Drc=3
> > > >> > > update.versions merge_rc_to_develop
> > > >> release.maven.staging.repo
> > > >> > >
> > > >> > > -Alex
> > > >> > >
> > > >> > > On 10/3/19, 1:49 AM, "Piotr Zarzycki" <
> > > >> piotrzarzycki21@gmail.com>
> > > >> > wrote:
> > > >> > >
> > > >> > > Those are the steps from the script which need
> to
> > be
> > > >> done still:
> > > >> > >
> > > >> > > 1) <antcall target="update.versions" />
> > > >> > > 2) <antcall target="merge_rc_to_develop" />
> > > >> > > 3) <antcall target="release.maven.staging.repo"
> />
> > > >> > >
> > > >> > > Number #1 is failing.
> > > >> > >
> > > >> > >
> > > >> > > czw., 3 paź 2019 o 10:41 Piotr Zarzycki <
> > > >> > piotrzarzycki21@gmail.com>
> > > >> > > napisał(a):
> > > >> > >
> > > >> > > > It looks like we already have:
> > > >> > > > 1) Successfully published npm:
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=HBSzGRshuTJ2xDFdHeLsUs6INhVdTygxlhVnJG18h4Q%3D&reserved=0
> > > >> > > > 2) Successfully published which can be updated
> > on
> > > >> the website:
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=Aom6KVIcuGyMhaH6Tih1GOD7TWklkr40GSXsy4Drp7o%3D&reserved=0
> > > >> > > >
> > > >> > > > Thanks,
> > > >> > > > Piotr
> > > >> > > >
> > > >> > > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <
> > > >> > piotrzarzycki21@gmail.com>
> > > >> > > > napisał(a):
> > > >> > > >
> > > >> > > >> I have used npm password from private and
> went
> > > >> trough
> > > >> > publishing
> > > >> > > npm and
> > > >> > > >> it's failed on next step update.version with
> > the
> > > >> same error.
> > > >> > Here
> > > >> > > you go
> > > >> > > >> full log [1].
> > > >> > > >>
> > > >> > > >> What will happen if I run publish npm stuff
> > again
> > > >> ? I can
> > > >> > omit that
> > > >> > > part
> > > >> > > >> in the next attempt.
> > > >> > > >>
> > > >> > > >> Om can you check whether my npm publish stuff
> > > went
> > > >> ok ?
> > > >> > > >>
> > > >> > > >> [1]
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=cT350bhfIX2sL59mnbWF7sffIHN%2BhgTaCiPR%2B3AYtKQ%3D&reserved=0
> > > >> > > >>
> > > >> > > >> Thanks,
> > > >> > > >> Piotr
> > > >> > > >>
> > > >> > > >> Thanks,
> > > >> > > >> Piotr
> > > >> > > >>
> > > >> > > >> śr., 2 paź 2019 o 18:40 Alex Harui
> > > >> <ah...@adobe.com.invalid>
> > > >> > > napisał(a):
> > > >> > > >>
> > > >> > > >>> Responses inline...
> > > >> > > >>>
> > > >> > > >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <
> > > >> > piotrzarzycki21@gmail.com>
> > > >> > > >>> wrote:
> > > >> > > >>>
> > > >> > > >>> Just to understand something.
> > > >> releasecandidate script is
> > > >> > using
> > > >> > > tag
> > > >> > > >>> instead
> > > >> > > >>> release branch to whole operation of
> > > increase
> > > >> version ?
> > > >> > > >>>
> > > >> > > >>> No, the "get_head_of_rc_branches" target
> > should
> > > >> get you the
> > > >> > head.
> > > >> > > >>>
> > > >> > > >>> > Hi,
> > > >> > > >>> >
> > > >> > > >>> > I just tried releasecandidate script.
> It
> > > >> contains
> > > >> > following
> > > >> > > steps.
> > > >> > > >>> >
> > > >> > > >>> > <antcall target="release.tag" />
> > > >> > > >>> > <!-- this is intended to merge
> > the
> > > >> tag to
> > > >> > master
> > > >> > > because
> > > >> > > >>> it should
> > > >> > > >>> > have the right versions in it -->
> > > >> > > >>> > <antcall
> > > >> target="merge_rc_to_master" />
> > > >> > > >>> > <antcall
> > > >> target="get_head_of_rc_branches" />
> > > >> > > >>> > <antcall target="release.npm"
> />
> > > >> > > >>> > <antcall
> > target="update.versions"
> > > />
> > > >> > > >>> > <antcall
> > > >> target="merge_rc_to_develop" />
> > > >> > > >>> > <antcall
> > > >> target="release.maven.staging.repo" />
> > > >> > > >>> >
> > > >> > > >>> > One step previous was move in svn
> > binaries
> > > >> from dev
> > > >> > folder to
> > > >> > > >>> release - I
> > > >> > > >>> > omit that cause I did it already
> > manually.
> > > >> Launching
> > > >> > > following
> > > >> > > >>> steps I
> > > >> > > >>> > reached release.npm - Which requires
> > login
> > > >> and
> > > >> > password to
> > > >> > > npm - I
> > > >> > > >>> > omitted that as well. Next was
> > > >> update.versions and it
> > > >> > failed
> > > >> > > with
> > > >> > > >>> following
> > > >> > > >>> > stack trace [1]
> > > >> > > >>> >
> > > >> > > >>>
> > > >> > > >>> The login and password is available in the
> > > >> private@
> > > >> > archives.
> > > >> > > >>>
> > > >> > > >>>
> > > >> > > >>> > In mentioned lines in the stacktrace I
> > > have:
> > > >> > > >>> >
> > > >> > > >>> > Line 1088:
> > > >> > > >>> > <antcall target="update.versions" />
> > > >> > > >>> >
> > > >> > > >>> > Line 1216:
> > > >> > > >>> > <exec executable="${git}"
> > > dir="${compiler}"
> > > >> > > failonerror="true" >
> > > >> > > >>> > <arg value="commit" />
> > > >> > > >>> > <arg value="-m" />
> > > >> > > >>> > <arg value="update version
> > to
> > > >> > > ${new.release.version}"
> > > >> > > >>> />
> > > >> > > >>> > </exec>
> > > >> > > >>> >
> > > >> > > >>> > [1]
> > > >> > > >>>
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=vVBlXC7nYVUkQAFYGZvqH1kq6uV5WeI%2BCG5W2nyYFEE%3D&reserved=0
> > > >> > > >>>
> > > >> > > >>> You did not post the whole log, so it is
> > > possible
> > > >> you missed
> > > >> > a
> > > >> > > step.
> > > >> > > >>> There is almost no way there shouldn't be
> > > changes
> > > >> and the
> > > >> > head
> > > >> > > should not
> > > >> > > >>> be detached.
> > > >> > > >>>
> > > >> > > >>> -Alex
> > > >> > > >>>
> > > >> > > >>>
> > > >> > > >>
> > > >> > > >> --
> > > >> > > >>
> > > >> > > >> Piotr Zarzycki
> > > >> > > >>
> > > >> > > >> Patreon: *
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >> > > >> <
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >> > > >*
> > > >> > > >>
> > > >> > > >
> > > >> > > >
> > > >> > > > --
> > > >> > > >
> > > >> > > > Piotr Zarzycki
> > > >> > > >
> > > >> > > > Patreon: *
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >> > > > <
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >> > > >*
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > >
> > > >> > > Piotr Zarzycki
> > > >> > >
> > > >> > > Patreon: *
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >> > > <
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >> > > >*
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> >
> > > >> > --
> > > >> >
> > > >> > Piotr Zarzycki
> > > >> >
> > > >> > Patreon: *
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >> > <
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >> > >*
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > > --
> > > >
> > > > 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
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Carlos,
Did you make an update API doc ? ->
https://royale.apache.org/asdoc/index.html
Thanks,
Piotr
pon., 7 paź 2019 o 19:38 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Piotr,
> yes, I'll do in next few hours.
> thanks.
>
> El lun., 7 oct. 2019 a las 9:54, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>)
> escribió:
>
> > Hi Carlos,
> >
> > Will you be able update website with links for 0.9.6 release ?
> >
> > Thanks,
> > Piotr
> >
> > niedz., 6 paź 2019 o 10:52 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> > > Hi Alex,
> > >
> > > Thank you for the fix. Everything worked fine this time.
> > >
> > > Piotr
> > >
> > > sob., 5 paź 2019 o 01:51 Alex Harui <ah...@adobe.com.invalid>
> > napisał(a):
> > >
> > >> I found some time to try the releasecandidate.xml and found the
> problem.
> > >> I pushed the fix to release/0.9.6. So try that and see what happens.
> > >> It seemed to do the right thing for me on my Windows computer.
> > >>
> > >> You will next likely run into several merge conflicts. I have not
> > looked
> > >> into the conflicts, but there is a good chance that some of that is
> due
> > to
> > >> the cherry-picking. I am going to start a separate thread about
> branch
> > >> management.
> > >>
> > >> -Alex
> > >>
> > >> On 10/4/19, 10:55 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> > >>
> > >> If we don't fix the release scripts, then the next RM is probably
> > >> going to run into the same problem. The time we spend now helps save
> > time
> > >> in the future. It is wise to improve the process now in case I get
> run
> > >> over by a bus tomorrow. If you do it manually and make a mistake, we
> > might
> > >> not catch it until later or cause more problems.
> > >>
> > >> IIRC, the Poms should not require changing. Maven should have
> done
> > >> that already.
> > >>
> > >> All the places I know of changing are in the script.
> > >>
> > >> -Alex
> > >>
> > >> On 10/4/19, 10:46 AM, "Piotr Zarzycki" <piotrzarzycki21@gmail.com
> >
> > >> wrote:
> > >>
> > >> Alex,
> > >>
> > >> Can I just do that changes manually on release branch and
> merge
> > >> stuff to
> > >> develop?
> > >>
> > >> I just don't won't to spend any more minute on release process
> > >> anymore.
> > >>
> > >> 1) I should change build properties
> > >> 2) I should change all poms
> > >>
> > >> Is there anymore place which I should know to change?
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> On Fri, Oct 4, 2019, 7:41 PM Alex Harui
> > <ah...@adobe.com.invalid>
> > >> wrote:
> > >>
> > >> > Piotr,
> > >> >
> > >> > Again, I am asking you to get in the mindset of a developer
> > and
> > >> not just a
> > >> > user. You can see that the Ant script is making some
> updates.
> > >> You can
> > >> > verify that the release branch does not have 0.9.7 for the
> > >> release.version
> > >> > in build.properties. You can see there is 1 commit pending
> in
> > >> > royale-asjs. You can see that the build.properties did get
> > >> changed to have
> > >> > release.version=0.9.7.
> > >> >
> > >> > So, you will have to investigate further. What is in that
> > >> commit? Is
> > >> > this output from a fresh start of cloning the repo or could
> > >> that commit be
> > >> > from a previous run? How could Git change a file but not
> > >> report it? Maybe
> > >> > add some <echo> tags or use -verbose to get more output.
> But
> > >> just giving
> > >> > me minimal information and waiting for me to guess as to
> what
> > >> to do next is
> > >> > not very efficient, IMO.
> > >> >
> > >> > Thanks,
> > >> > -Alex
> > >> >
> > >> > On 10/4/19, 4:01 AM, "Piotr Zarzycki" <
> > >> piotrzarzycki21@gmail.com> wrote:
> > >> >
> > >> > Hi Alex,
> > >> >
> > >> > Git status after failing for all 3 repos [1].
> > >> >
> > >> > Here is how build.properties look like after performing
> > >> update.versions
> > >> > target [2].
> > >> >
> > >> > I will skip some part to move forward but
> update.versions
> > >> is important.
> > >> >
> > >> > [1]
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=nvSDESjmBw5j%2FlBoaIPGTUiBKrkoXcAVGIyUV371eE8%3D&reserved=0
> > >> > [2]
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvou&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=ljQmwiJbtqsTIj3tx9%2FtKyy%2Bns5Sz7P%2BCQE3Knb%2F1fA%3D&reserved=0
> > >> >
> > >> > Thanks,
> > >> > Piotr
> > >> >
> > >> > czw., 3 paź 2019 o 17:49 Alex Harui
> > >> <ah...@adobe.com.invalid>
> > >> > napisał(a):
> > >> >
> > >> > > What does "git status" show in the 3 repos?
> > >> > >
> > >> > > The update.versions should have at least changed the
> > >> > build.properties file
> > >> > > in the repo.
> > >> > >
> > >> > > You can try skipping over steps by listing the steps
> on
> > >> the command
> > >> > line.
> > >> > > You might need to list some pre-requisite steps before
> > or
> > >> add them
> > >> > to the
> > >> > > "depends" of the step that needs it.
> > >> > >
> > >> > > ant -e -f releasecandidate.xml -Drelease.version=0.9.6
> > >> -Drc=3
> > >> > > update.versions merge_rc_to_develop
> > >> release.maven.staging.repo
> > >> > >
> > >> > > -Alex
> > >> > >
> > >> > > On 10/3/19, 1:49 AM, "Piotr Zarzycki" <
> > >> piotrzarzycki21@gmail.com>
> > >> > wrote:
> > >> > >
> > >> > > Those are the steps from the script which need to
> be
> > >> done still:
> > >> > >
> > >> > > 1) <antcall target="update.versions" />
> > >> > > 2) <antcall target="merge_rc_to_develop" />
> > >> > > 3) <antcall target="release.maven.staging.repo" />
> > >> > >
> > >> > > Number #1 is failing.
> > >> > >
> > >> > >
> > >> > > czw., 3 paź 2019 o 10:41 Piotr Zarzycki <
> > >> > piotrzarzycki21@gmail.com>
> > >> > > napisał(a):
> > >> > >
> > >> > > > It looks like we already have:
> > >> > > > 1) Successfully published npm:
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=HBSzGRshuTJ2xDFdHeLsUs6INhVdTygxlhVnJG18h4Q%3D&reserved=0
> > >> > > > 2) Successfully published which can be updated
> on
> > >> the website:
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=Aom6KVIcuGyMhaH6Tih1GOD7TWklkr40GSXsy4Drp7o%3D&reserved=0
> > >> > > >
> > >> > > > Thanks,
> > >> > > > Piotr
> > >> > > >
> > >> > > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <
> > >> > piotrzarzycki21@gmail.com>
> > >> > > > napisał(a):
> > >> > > >
> > >> > > >> I have used npm password from private and went
> > >> trough
> > >> > publishing
> > >> > > npm and
> > >> > > >> it's failed on next step update.version with
> the
> > >> same error.
> > >> > Here
> > >> > > you go
> > >> > > >> full log [1].
> > >> > > >>
> > >> > > >> What will happen if I run publish npm stuff
> again
> > >> ? I can
> > >> > omit that
> > >> > > part
> > >> > > >> in the next attempt.
> > >> > > >>
> > >> > > >> Om can you check whether my npm publish stuff
> > went
> > >> ok ?
> > >> > > >>
> > >> > > >> [1]
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=cT350bhfIX2sL59mnbWF7sffIHN%2BhgTaCiPR%2B3AYtKQ%3D&reserved=0
> > >> > > >>
> > >> > > >> Thanks,
> > >> > > >> Piotr
> > >> > > >>
> > >> > > >> Thanks,
> > >> > > >> Piotr
> > >> > > >>
> > >> > > >> śr., 2 paź 2019 o 18:40 Alex Harui
> > >> <ah...@adobe.com.invalid>
> > >> > > napisał(a):
> > >> > > >>
> > >> > > >>> Responses inline...
> > >> > > >>>
> > >> > > >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <
> > >> > piotrzarzycki21@gmail.com>
> > >> > > >>> wrote:
> > >> > > >>>
> > >> > > >>> Just to understand something.
> > >> releasecandidate script is
> > >> > using
> > >> > > tag
> > >> > > >>> instead
> > >> > > >>> release branch to whole operation of
> > increase
> > >> version ?
> > >> > > >>>
> > >> > > >>> No, the "get_head_of_rc_branches" target
> should
> > >> get you the
> > >> > head.
> > >> > > >>>
> > >> > > >>> > Hi,
> > >> > > >>> >
> > >> > > >>> > I just tried releasecandidate script. It
> > >> contains
> > >> > following
> > >> > > steps.
> > >> > > >>> >
> > >> > > >>> > <antcall target="release.tag" />
> > >> > > >>> > <!-- this is intended to merge
> the
> > >> tag to
> > >> > master
> > >> > > because
> > >> > > >>> it should
> > >> > > >>> > have the right versions in it -->
> > >> > > >>> > <antcall
> > >> target="merge_rc_to_master" />
> > >> > > >>> > <antcall
> > >> target="get_head_of_rc_branches" />
> > >> > > >>> > <antcall target="release.npm" />
> > >> > > >>> > <antcall
> target="update.versions"
> > />
> > >> > > >>> > <antcall
> > >> target="merge_rc_to_develop" />
> > >> > > >>> > <antcall
> > >> target="release.maven.staging.repo" />
> > >> > > >>> >
> > >> > > >>> > One step previous was move in svn
> binaries
> > >> from dev
> > >> > folder to
> > >> > > >>> release - I
> > >> > > >>> > omit that cause I did it already
> manually.
> > >> Launching
> > >> > > following
> > >> > > >>> steps I
> > >> > > >>> > reached release.npm - Which requires
> login
> > >> and
> > >> > password to
> > >> > > npm - I
> > >> > > >>> > omitted that as well. Next was
> > >> update.versions and it
> > >> > failed
> > >> > > with
> > >> > > >>> following
> > >> > > >>> > stack trace [1]
> > >> > > >>> >
> > >> > > >>>
> > >> > > >>> The login and password is available in the
> > >> private@
> > >> > archives.
> > >> > > >>>
> > >> > > >>>
> > >> > > >>> > In mentioned lines in the stacktrace I
> > have:
> > >> > > >>> >
> > >> > > >>> > Line 1088:
> > >> > > >>> > <antcall target="update.versions" />
> > >> > > >>> >
> > >> > > >>> > Line 1216:
> > >> > > >>> > <exec executable="${git}"
> > dir="${compiler}"
> > >> > > failonerror="true" >
> > >> > > >>> > <arg value="commit" />
> > >> > > >>> > <arg value="-m" />
> > >> > > >>> > <arg value="update version
> to
> > >> > > ${new.release.version}"
> > >> > > >>> />
> > >> > > >>> > </exec>
> > >> > > >>> >
> > >> > > >>> > [1]
> > >> > > >>>
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=vVBlXC7nYVUkQAFYGZvqH1kq6uV5WeI%2BCG5W2nyYFEE%3D&reserved=0
> > >> > > >>>
> > >> > > >>> You did not post the whole log, so it is
> > possible
> > >> you missed
> > >> > a
> > >> > > step.
> > >> > > >>> There is almost no way there shouldn't be
> > changes
> > >> and the
> > >> > head
> > >> > > should not
> > >> > > >>> be detached.
> > >> > > >>>
> > >> > > >>> -Alex
> > >> > > >>>
> > >> > > >>>
> > >> > > >>
> > >> > > >> --
> > >> > > >>
> > >> > > >> Piotr Zarzycki
> > >> > > >>
> > >> > > >> Patreon: *
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >> > > >> <
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >> > > >*
> > >> > > >>
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > >
> > >> > > > Piotr Zarzycki
> > >> > > >
> > >> > > > Patreon: *
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >> > > > <
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >> > > >*
> > >> > > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > >
> > >> > > Piotr Zarzycki
> > >> > >
> > >> > > Patreon: *
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >> > > <
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >> > > >*
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >> > --
> > >> >
> > >> > Piotr Zarzycki
> > >> >
> > >> > Patreon: *
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >> > <
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >> > >*
> > >> >
> > >> >
> > >> >
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > > --
> > >
> > > 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
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
yes, I'll do in next few hours.
thanks.
El lun., 7 oct. 2019 a las 9:54, Piotr Zarzycki (<pi...@gmail.com>)
escribió:
> Hi Carlos,
>
> Will you be able update website with links for 0.9.6 release ?
>
> Thanks,
> Piotr
>
> niedz., 6 paź 2019 o 10:52 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Hi Alex,
> >
> > Thank you for the fix. Everything worked fine this time.
> >
> > Piotr
> >
> > sob., 5 paź 2019 o 01:51 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
> >
> >> I found some time to try the releasecandidate.xml and found the problem.
> >> I pushed the fix to release/0.9.6. So try that and see what happens.
> >> It seemed to do the right thing for me on my Windows computer.
> >>
> >> You will next likely run into several merge conflicts. I have not
> looked
> >> into the conflicts, but there is a good chance that some of that is due
> to
> >> the cherry-picking. I am going to start a separate thread about branch
> >> management.
> >>
> >> -Alex
> >>
> >> On 10/4/19, 10:55 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >>
> >> If we don't fix the release scripts, then the next RM is probably
> >> going to run into the same problem. The time we spend now helps save
> time
> >> in the future. It is wise to improve the process now in case I get run
> >> over by a bus tomorrow. If you do it manually and make a mistake, we
> might
> >> not catch it until later or cause more problems.
> >>
> >> IIRC, the Poms should not require changing. Maven should have done
> >> that already.
> >>
> >> All the places I know of changing are in the script.
> >>
> >> -Alex
> >>
> >> On 10/4/19, 10:46 AM, "Piotr Zarzycki" <pi...@gmail.com>
> >> wrote:
> >>
> >> Alex,
> >>
> >> Can I just do that changes manually on release branch and merge
> >> stuff to
> >> develop?
> >>
> >> I just don't won't to spend any more minute on release process
> >> anymore.
> >>
> >> 1) I should change build properties
> >> 2) I should change all poms
> >>
> >> Is there anymore place which I should know to change?
> >>
> >> Thanks,
> >> Piotr
> >>
> >> On Fri, Oct 4, 2019, 7:41 PM Alex Harui
> <ah...@adobe.com.invalid>
> >> wrote:
> >>
> >> > Piotr,
> >> >
> >> > Again, I am asking you to get in the mindset of a developer
> and
> >> not just a
> >> > user. You can see that the Ant script is making some updates.
> >> You can
> >> > verify that the release branch does not have 0.9.7 for the
> >> release.version
> >> > in build.properties. You can see there is 1 commit pending in
> >> > royale-asjs. You can see that the build.properties did get
> >> changed to have
> >> > release.version=0.9.7.
> >> >
> >> > So, you will have to investigate further. What is in that
> >> commit? Is
> >> > this output from a fresh start of cloning the repo or could
> >> that commit be
> >> > from a previous run? How could Git change a file but not
> >> report it? Maybe
> >> > add some <echo> tags or use -verbose to get more output. But
> >> just giving
> >> > me minimal information and waiting for me to guess as to what
> >> to do next is
> >> > not very efficient, IMO.
> >> >
> >> > Thanks,
> >> > -Alex
> >> >
> >> > On 10/4/19, 4:01 AM, "Piotr Zarzycki" <
> >> piotrzarzycki21@gmail.com> wrote:
> >> >
> >> > Hi Alex,
> >> >
> >> > Git status after failing for all 3 repos [1].
> >> >
> >> > Here is how build.properties look like after performing
> >> update.versions
> >> > target [2].
> >> >
> >> > I will skip some part to move forward but update.versions
> >> is important.
> >> >
> >> > [1]
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=nvSDESjmBw5j%2FlBoaIPGTUiBKrkoXcAVGIyUV371eE8%3D&reserved=0
> >> > [2]
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvou&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=ljQmwiJbtqsTIj3tx9%2FtKyy%2Bns5Sz7P%2BCQE3Knb%2F1fA%3D&reserved=0
> >> >
> >> > Thanks,
> >> > Piotr
> >> >
> >> > czw., 3 paź 2019 o 17:49 Alex Harui
> >> <ah...@adobe.com.invalid>
> >> > napisał(a):
> >> >
> >> > > What does "git status" show in the 3 repos?
> >> > >
> >> > > The update.versions should have at least changed the
> >> > build.properties file
> >> > > in the repo.
> >> > >
> >> > > You can try skipping over steps by listing the steps on
> >> the command
> >> > line.
> >> > > You might need to list some pre-requisite steps before
> or
> >> add them
> >> > to the
> >> > > "depends" of the step that needs it.
> >> > >
> >> > > ant -e -f releasecandidate.xml -Drelease.version=0.9.6
> >> -Drc=3
> >> > > update.versions merge_rc_to_develop
> >> release.maven.staging.repo
> >> > >
> >> > > -Alex
> >> > >
> >> > > On 10/3/19, 1:49 AM, "Piotr Zarzycki" <
> >> piotrzarzycki21@gmail.com>
> >> > wrote:
> >> > >
> >> > > Those are the steps from the script which need to be
> >> done still:
> >> > >
> >> > > 1) <antcall target="update.versions" />
> >> > > 2) <antcall target="merge_rc_to_develop" />
> >> > > 3) <antcall target="release.maven.staging.repo" />
> >> > >
> >> > > Number #1 is failing.
> >> > >
> >> > >
> >> > > czw., 3 paź 2019 o 10:41 Piotr Zarzycki <
> >> > piotrzarzycki21@gmail.com>
> >> > > napisał(a):
> >> > >
> >> > > > It looks like we already have:
> >> > > > 1) Successfully published npm:
> >> > > >
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=HBSzGRshuTJ2xDFdHeLsUs6INhVdTygxlhVnJG18h4Q%3D&reserved=0
> >> > > > 2) Successfully published which can be updated on
> >> the website:
> >> > > >
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=Aom6KVIcuGyMhaH6Tih1GOD7TWklkr40GSXsy4Drp7o%3D&reserved=0
> >> > > >
> >> > > > Thanks,
> >> > > > Piotr
> >> > > >
> >> > > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <
> >> > piotrzarzycki21@gmail.com>
> >> > > > napisał(a):
> >> > > >
> >> > > >> I have used npm password from private and went
> >> trough
> >> > publishing
> >> > > npm and
> >> > > >> it's failed on next step update.version with the
> >> same error.
> >> > Here
> >> > > you go
> >> > > >> full log [1].
> >> > > >>
> >> > > >> What will happen if I run publish npm stuff again
> >> ? I can
> >> > omit that
> >> > > part
> >> > > >> in the next attempt.
> >> > > >>
> >> > > >> Om can you check whether my npm publish stuff
> went
> >> ok ?
> >> > > >>
> >> > > >> [1]
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=cT350bhfIX2sL59mnbWF7sffIHN%2BhgTaCiPR%2B3AYtKQ%3D&reserved=0
> >> > > >>
> >> > > >> Thanks,
> >> > > >> Piotr
> >> > > >>
> >> > > >> Thanks,
> >> > > >> Piotr
> >> > > >>
> >> > > >> śr., 2 paź 2019 o 18:40 Alex Harui
> >> <ah...@adobe.com.invalid>
> >> > > napisał(a):
> >> > > >>
> >> > > >>> Responses inline...
> >> > > >>>
> >> > > >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <
> >> > piotrzarzycki21@gmail.com>
> >> > > >>> wrote:
> >> > > >>>
> >> > > >>> Just to understand something.
> >> releasecandidate script is
> >> > using
> >> > > tag
> >> > > >>> instead
> >> > > >>> release branch to whole operation of
> increase
> >> version ?
> >> > > >>>
> >> > > >>> No, the "get_head_of_rc_branches" target should
> >> get you the
> >> > head.
> >> > > >>>
> >> > > >>> > Hi,
> >> > > >>> >
> >> > > >>> > I just tried releasecandidate script. It
> >> contains
> >> > following
> >> > > steps.
> >> > > >>> >
> >> > > >>> > <antcall target="release.tag" />
> >> > > >>> > <!-- this is intended to merge the
> >> tag to
> >> > master
> >> > > because
> >> > > >>> it should
> >> > > >>> > have the right versions in it -->
> >> > > >>> > <antcall
> >> target="merge_rc_to_master" />
> >> > > >>> > <antcall
> >> target="get_head_of_rc_branches" />
> >> > > >>> > <antcall target="release.npm" />
> >> > > >>> > <antcall target="update.versions"
> />
> >> > > >>> > <antcall
> >> target="merge_rc_to_develop" />
> >> > > >>> > <antcall
> >> target="release.maven.staging.repo" />
> >> > > >>> >
> >> > > >>> > One step previous was move in svn binaries
> >> from dev
> >> > folder to
> >> > > >>> release - I
> >> > > >>> > omit that cause I did it already manually.
> >> Launching
> >> > > following
> >> > > >>> steps I
> >> > > >>> > reached release.npm - Which requires login
> >> and
> >> > password to
> >> > > npm - I
> >> > > >>> > omitted that as well. Next was
> >> update.versions and it
> >> > failed
> >> > > with
> >> > > >>> following
> >> > > >>> > stack trace [1]
> >> > > >>> >
> >> > > >>>
> >> > > >>> The login and password is available in the
> >> private@
> >> > archives.
> >> > > >>>
> >> > > >>>
> >> > > >>> > In mentioned lines in the stacktrace I
> have:
> >> > > >>> >
> >> > > >>> > Line 1088:
> >> > > >>> > <antcall target="update.versions" />
> >> > > >>> >
> >> > > >>> > Line 1216:
> >> > > >>> > <exec executable="${git}"
> dir="${compiler}"
> >> > > failonerror="true" >
> >> > > >>> > <arg value="commit" />
> >> > > >>> > <arg value="-m" />
> >> > > >>> > <arg value="update version to
> >> > > ${new.release.version}"
> >> > > >>> />
> >> > > >>> > </exec>
> >> > > >>> >
> >> > > >>> > [1]
> >> > > >>>
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=vVBlXC7nYVUkQAFYGZvqH1kq6uV5WeI%2BCG5W2nyYFEE%3D&reserved=0
> >> > > >>>
> >> > > >>> You did not post the whole log, so it is
> possible
> >> you missed
> >> > a
> >> > > step.
> >> > > >>> There is almost no way there shouldn't be
> changes
> >> and the
> >> > head
> >> > > should not
> >> > > >>> be detached.
> >> > > >>>
> >> > > >>> -Alex
> >> > > >>>
> >> > > >>>
> >> > > >>
> >> > > >> --
> >> > > >>
> >> > > >> Piotr Zarzycki
> >> > > >>
> >> > > >> Patreon: *
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> >> > > >> <
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> >> > > >*
> >> > > >>
> >> > > >
> >> > > >
> >> > > > --
> >> > > >
> >> > > > Piotr Zarzycki
> >> > > >
> >> > > > Patreon: *
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> >> > > > <
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> >> > > >*
> >> > > >
> >> > >
> >> > >
> >> > > --
> >> > >
> >> > > Piotr Zarzycki
> >> > >
> >> > > Patreon: *
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> >> > > <
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> >> > > >*
> >> > >
> >> > >
> >> > >
> >> >
> >> > --
> >> >
> >> > Piotr Zarzycki
> >> >
> >> > Patreon: *
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> >> > <
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> >> > >*
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >>
> >>
> >
> > --
> >
> > 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: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Carlos,
Will you be able update website with links for 0.9.6 release ?
Thanks,
Piotr
niedz., 6 paź 2019 o 10:52 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi Alex,
>
> Thank you for the fix. Everything worked fine this time.
>
> Piotr
>
> sob., 5 paź 2019 o 01:51 Alex Harui <ah...@adobe.com.invalid> napisał(a):
>
>> I found some time to try the releasecandidate.xml and found the problem.
>> I pushed the fix to release/0.9.6. So try that and see what happens.
>> It seemed to do the right thing for me on my Windows computer.
>>
>> You will next likely run into several merge conflicts. I have not looked
>> into the conflicts, but there is a good chance that some of that is due to
>> the cherry-picking. I am going to start a separate thread about branch
>> management.
>>
>> -Alex
>>
>> On 10/4/19, 10:55 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>>
>> If we don't fix the release scripts, then the next RM is probably
>> going to run into the same problem. The time we spend now helps save time
>> in the future. It is wise to improve the process now in case I get run
>> over by a bus tomorrow. If you do it manually and make a mistake, we might
>> not catch it until later or cause more problems.
>>
>> IIRC, the Poms should not require changing. Maven should have done
>> that already.
>>
>> All the places I know of changing are in the script.
>>
>> -Alex
>>
>> On 10/4/19, 10:46 AM, "Piotr Zarzycki" <pi...@gmail.com>
>> wrote:
>>
>> Alex,
>>
>> Can I just do that changes manually on release branch and merge
>> stuff to
>> develop?
>>
>> I just don't won't to spend any more minute on release process
>> anymore.
>>
>> 1) I should change build properties
>> 2) I should change all poms
>>
>> Is there anymore place which I should know to change?
>>
>> Thanks,
>> Piotr
>>
>> On Fri, Oct 4, 2019, 7:41 PM Alex Harui <ah...@adobe.com.invalid>
>> wrote:
>>
>> > Piotr,
>> >
>> > Again, I am asking you to get in the mindset of a developer and
>> not just a
>> > user. You can see that the Ant script is making some updates.
>> You can
>> > verify that the release branch does not have 0.9.7 for the
>> release.version
>> > in build.properties. You can see there is 1 commit pending in
>> > royale-asjs. You can see that the build.properties did get
>> changed to have
>> > release.version=0.9.7.
>> >
>> > So, you will have to investigate further. What is in that
>> commit? Is
>> > this output from a fresh start of cloning the repo or could
>> that commit be
>> > from a previous run? How could Git change a file but not
>> report it? Maybe
>> > add some <echo> tags or use -verbose to get more output. But
>> just giving
>> > me minimal information and waiting for me to guess as to what
>> to do next is
>> > not very efficient, IMO.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 10/4/19, 4:01 AM, "Piotr Zarzycki" <
>> piotrzarzycki21@gmail.com> wrote:
>> >
>> > Hi Alex,
>> >
>> > Git status after failing for all 3 repos [1].
>> >
>> > Here is how build.properties look like after performing
>> update.versions
>> > target [2].
>> >
>> > I will skip some part to move forward but update.versions
>> is important.
>> >
>> > [1]
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=nvSDESjmBw5j%2FlBoaIPGTUiBKrkoXcAVGIyUV371eE8%3D&reserved=0
>> > [2]
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvou&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=ljQmwiJbtqsTIj3tx9%2FtKyy%2Bns5Sz7P%2BCQE3Knb%2F1fA%3D&reserved=0
>> >
>> > Thanks,
>> > Piotr
>> >
>> > czw., 3 paź 2019 o 17:49 Alex Harui
>> <ah...@adobe.com.invalid>
>> > napisał(a):
>> >
>> > > What does "git status" show in the 3 repos?
>> > >
>> > > The update.versions should have at least changed the
>> > build.properties file
>> > > in the repo.
>> > >
>> > > You can try skipping over steps by listing the steps on
>> the command
>> > line.
>> > > You might need to list some pre-requisite steps before or
>> add them
>> > to the
>> > > "depends" of the step that needs it.
>> > >
>> > > ant -e -f releasecandidate.xml -Drelease.version=0.9.6
>> -Drc=3
>> > > update.versions merge_rc_to_develop
>> release.maven.staging.repo
>> > >
>> > > -Alex
>> > >
>> > > On 10/3/19, 1:49 AM, "Piotr Zarzycki" <
>> piotrzarzycki21@gmail.com>
>> > wrote:
>> > >
>> > > Those are the steps from the script which need to be
>> done still:
>> > >
>> > > 1) <antcall target="update.versions" />
>> > > 2) <antcall target="merge_rc_to_develop" />
>> > > 3) <antcall target="release.maven.staging.repo" />
>> > >
>> > > Number #1 is failing.
>> > >
>> > >
>> > > czw., 3 paź 2019 o 10:41 Piotr Zarzycki <
>> > piotrzarzycki21@gmail.com>
>> > > napisał(a):
>> > >
>> > > > It looks like we already have:
>> > > > 1) Successfully published npm:
>> > > >
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=HBSzGRshuTJ2xDFdHeLsUs6INhVdTygxlhVnJG18h4Q%3D&reserved=0
>> > > > 2) Successfully published which can be updated on
>> the website:
>> > > >
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=Aom6KVIcuGyMhaH6Tih1GOD7TWklkr40GSXsy4Drp7o%3D&reserved=0
>> > > >
>> > > > Thanks,
>> > > > Piotr
>> > > >
>> > > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <
>> > piotrzarzycki21@gmail.com>
>> > > > napisał(a):
>> > > >
>> > > >> I have used npm password from private and went
>> trough
>> > publishing
>> > > npm and
>> > > >> it's failed on next step update.version with the
>> same error.
>> > Here
>> > > you go
>> > > >> full log [1].
>> > > >>
>> > > >> What will happen if I run publish npm stuff again
>> ? I can
>> > omit that
>> > > part
>> > > >> in the next attempt.
>> > > >>
>> > > >> Om can you check whether my npm publish stuff went
>> ok ?
>> > > >>
>> > > >> [1]
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=cT350bhfIX2sL59mnbWF7sffIHN%2BhgTaCiPR%2B3AYtKQ%3D&reserved=0
>> > > >>
>> > > >> Thanks,
>> > > >> Piotr
>> > > >>
>> > > >> Thanks,
>> > > >> Piotr
>> > > >>
>> > > >> śr., 2 paź 2019 o 18:40 Alex Harui
>> <ah...@adobe.com.invalid>
>> > > napisał(a):
>> > > >>
>> > > >>> Responses inline...
>> > > >>>
>> > > >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <
>> > piotrzarzycki21@gmail.com>
>> > > >>> wrote:
>> > > >>>
>> > > >>> Just to understand something.
>> releasecandidate script is
>> > using
>> > > tag
>> > > >>> instead
>> > > >>> release branch to whole operation of increase
>> version ?
>> > > >>>
>> > > >>> No, the "get_head_of_rc_branches" target should
>> get you the
>> > head.
>> > > >>>
>> > > >>> > Hi,
>> > > >>> >
>> > > >>> > I just tried releasecandidate script. It
>> contains
>> > following
>> > > steps.
>> > > >>> >
>> > > >>> > <antcall target="release.tag" />
>> > > >>> > <!-- this is intended to merge the
>> tag to
>> > master
>> > > because
>> > > >>> it should
>> > > >>> > have the right versions in it -->
>> > > >>> > <antcall
>> target="merge_rc_to_master" />
>> > > >>> > <antcall
>> target="get_head_of_rc_branches" />
>> > > >>> > <antcall target="release.npm" />
>> > > >>> > <antcall target="update.versions" />
>> > > >>> > <antcall
>> target="merge_rc_to_develop" />
>> > > >>> > <antcall
>> target="release.maven.staging.repo" />
>> > > >>> >
>> > > >>> > One step previous was move in svn binaries
>> from dev
>> > folder to
>> > > >>> release - I
>> > > >>> > omit that cause I did it already manually.
>> Launching
>> > > following
>> > > >>> steps I
>> > > >>> > reached release.npm - Which requires login
>> and
>> > password to
>> > > npm - I
>> > > >>> > omitted that as well. Next was
>> update.versions and it
>> > failed
>> > > with
>> > > >>> following
>> > > >>> > stack trace [1]
>> > > >>> >
>> > > >>>
>> > > >>> The login and password is available in the
>> private@
>> > archives.
>> > > >>>
>> > > >>>
>> > > >>> > In mentioned lines in the stacktrace I have:
>> > > >>> >
>> > > >>> > Line 1088:
>> > > >>> > <antcall target="update.versions" />
>> > > >>> >
>> > > >>> > Line 1216:
>> > > >>> > <exec executable="${git}" dir="${compiler}"
>> > > failonerror="true" >
>> > > >>> > <arg value="commit" />
>> > > >>> > <arg value="-m" />
>> > > >>> > <arg value="update version to
>> > > ${new.release.version}"
>> > > >>> />
>> > > >>> > </exec>
>> > > >>> >
>> > > >>> > [1]
>> > > >>>
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=vVBlXC7nYVUkQAFYGZvqH1kq6uV5WeI%2BCG5W2nyYFEE%3D&reserved=0
>> > > >>>
>> > > >>> You did not post the whole log, so it is possible
>> you missed
>> > a
>> > > step.
>> > > >>> There is almost no way there shouldn't be changes
>> and the
>> > head
>> > > should not
>> > > >>> be detached.
>> > > >>>
>> > > >>> -Alex
>> > > >>>
>> > > >>>
>> > > >>
>> > > >> --
>> > > >>
>> > > >> Piotr Zarzycki
>> > > >>
>> > > >> Patreon: *
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
>> > > >> <
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
>> > > >*
>> > > >>
>> > > >
>> > > >
>> > > > --
>> > > >
>> > > > Piotr Zarzycki
>> > > >
>> > > > Patreon: *
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
>> > > > <
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
>> > > >*
>> > > >
>> > >
>> > >
>> > > --
>> > >
>> > > Piotr Zarzycki
>> > >
>> > > Patreon: *
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
>> > > <
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
>> > > >*
>> > >
>> > >
>> > >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
>> > <
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
>> > >*
>> >
>> >
>> >
>>
>>
>>
>>
>>
>
> --
>
> 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: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
Thank you for the fix. Everything worked fine this time.
Piotr
sob., 5 paź 2019 o 01:51 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> I found some time to try the releasecandidate.xml and found the problem.
> I pushed the fix to release/0.9.6. So try that and see what happens. It
> seemed to do the right thing for me on my Windows computer.
>
> You will next likely run into several merge conflicts. I have not looked
> into the conflicts, but there is a good chance that some of that is due to
> the cherry-picking. I am going to start a separate thread about branch
> management.
>
> -Alex
>
> On 10/4/19, 10:55 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> If we don't fix the release scripts, then the next RM is probably
> going to run into the same problem. The time we spend now helps save time
> in the future. It is wise to improve the process now in case I get run
> over by a bus tomorrow. If you do it manually and make a mistake, we might
> not catch it until later or cause more problems.
>
> IIRC, the Poms should not require changing. Maven should have done
> that already.
>
> All the places I know of changing are in the script.
>
> -Alex
>
> On 10/4/19, 10:46 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
>
> Alex,
>
> Can I just do that changes manually on release branch and merge
> stuff to
> develop?
>
> I just don't won't to spend any more minute on release process
> anymore.
>
> 1) I should change build properties
> 2) I should change all poms
>
> Is there anymore place which I should know to change?
>
> Thanks,
> Piotr
>
> On Fri, Oct 4, 2019, 7:41 PM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
> > Piotr,
> >
> > Again, I am asking you to get in the mindset of a developer and
> not just a
> > user. You can see that the Ant script is making some updates.
> You can
> > verify that the release branch does not have 0.9.7 for the
> release.version
> > in build.properties. You can see there is 1 commit pending in
> > royale-asjs. You can see that the build.properties did get
> changed to have
> > release.version=0.9.7.
> >
> > So, you will have to investigate further. What is in that
> commit? Is
> > this output from a fresh start of cloning the repo or could that
> commit be
> > from a previous run? How could Git change a file but not report
> it? Maybe
> > add some <echo> tags or use -verbose to get more output. But
> just giving
> > me minimal information and waiting for me to guess as to what to
> do next is
> > not very efficient, IMO.
> >
> > Thanks,
> > -Alex
> >
> > On 10/4/19, 4:01 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Hi Alex,
> >
> > Git status after failing for all 3 repos [1].
> >
> > Here is how build.properties look like after performing
> update.versions
> > target [2].
> >
> > I will skip some part to move forward but update.versions is
> important.
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=nvSDESjmBw5j%2FlBoaIPGTUiBKrkoXcAVGIyUV371eE8%3D&reserved=0
> > [2]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvou&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=ljQmwiJbtqsTIj3tx9%2FtKyy%2Bns5Sz7P%2BCQE3Knb%2F1fA%3D&reserved=0
> >
> > Thanks,
> > Piotr
> >
> > czw., 3 paź 2019 o 17:49 Alex Harui <aharui@adobe.com.invalid
> >
> > napisał(a):
> >
> > > What does "git status" show in the 3 repos?
> > >
> > > The update.versions should have at least changed the
> > build.properties file
> > > in the repo.
> > >
> > > You can try skipping over steps by listing the steps on
> the command
> > line.
> > > You might need to list some pre-requisite steps before or
> add them
> > to the
> > > "depends" of the step that needs it.
> > >
> > > ant -e -f releasecandidate.xml -Drelease.version=0.9.6
> -Drc=3
> > > update.versions merge_rc_to_develop
> release.maven.staging.repo
> > >
> > > -Alex
> > >
> > > On 10/3/19, 1:49 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com>
> > wrote:
> > >
> > > Those are the steps from the script which need to be
> done still:
> > >
> > > 1) <antcall target="update.versions" />
> > > 2) <antcall target="merge_rc_to_develop" />
> > > 3) <antcall target="release.maven.staging.repo" />
> > >
> > > Number #1 is failing.
> > >
> > >
> > > czw., 3 paź 2019 o 10:41 Piotr Zarzycki <
> > piotrzarzycki21@gmail.com>
> > > napisał(a):
> > >
> > > > It looks like we already have:
> > > > 1) Successfully published npm:
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=HBSzGRshuTJ2xDFdHeLsUs6INhVdTygxlhVnJG18h4Q%3D&reserved=0
> > > > 2) Successfully published which can be updated on
> the website:
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=Aom6KVIcuGyMhaH6Tih1GOD7TWklkr40GSXsy4Drp7o%3D&reserved=0
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <
> > piotrzarzycki21@gmail.com>
> > > > napisał(a):
> > > >
> > > >> I have used npm password from private and went
> trough
> > publishing
> > > npm and
> > > >> it's failed on next step update.version with the
> same error.
> > Here
> > > you go
> > > >> full log [1].
> > > >>
> > > >> What will happen if I run publish npm stuff again ?
> I can
> > omit that
> > > part
> > > >> in the next attempt.
> > > >>
> > > >> Om can you check whether my npm publish stuff went
> ok ?
> > > >>
> > > >> [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=cT350bhfIX2sL59mnbWF7sffIHN%2BhgTaCiPR%2B3AYtKQ%3D&reserved=0
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >>
> > > >> śr., 2 paź 2019 o 18:40 Alex Harui
> <ah...@adobe.com.invalid>
> > > napisał(a):
> > > >>
> > > >>> Responses inline...
> > > >>>
> > > >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <
> > piotrzarzycki21@gmail.com>
> > > >>> wrote:
> > > >>>
> > > >>> Just to understand something. releasecandidate
> script is
> > using
> > > tag
> > > >>> instead
> > > >>> release branch to whole operation of increase
> version ?
> > > >>>
> > > >>> No, the "get_head_of_rc_branches" target should
> get you the
> > head.
> > > >>>
> > > >>> > Hi,
> > > >>> >
> > > >>> > I just tried releasecandidate script. It
> contains
> > following
> > > steps.
> > > >>> >
> > > >>> > <antcall target="release.tag" />
> > > >>> > <!-- this is intended to merge the
> tag to
> > master
> > > because
> > > >>> it should
> > > >>> > have the right versions in it -->
> > > >>> > <antcall target="merge_rc_to_master"
> />
> > > >>> > <antcall
> target="get_head_of_rc_branches" />
> > > >>> > <antcall target="release.npm" />
> > > >>> > <antcall target="update.versions" />
> > > >>> > <antcall
> target="merge_rc_to_develop" />
> > > >>> > <antcall
> target="release.maven.staging.repo" />
> > > >>> >
> > > >>> > One step previous was move in svn binaries
> from dev
> > folder to
> > > >>> release - I
> > > >>> > omit that cause I did it already manually.
> Launching
> > > following
> > > >>> steps I
> > > >>> > reached release.npm - Which requires login
> and
> > password to
> > > npm - I
> > > >>> > omitted that as well. Next was
> update.versions and it
> > failed
> > > with
> > > >>> following
> > > >>> > stack trace [1]
> > > >>> >
> > > >>>
> > > >>> The login and password is available in the private@
> > archives.
> > > >>>
> > > >>>
> > > >>> > In mentioned lines in the stacktrace I have:
> > > >>> >
> > > >>> > Line 1088:
> > > >>> > <antcall target="update.versions" />
> > > >>> >
> > > >>> > Line 1216:
> > > >>> > <exec executable="${git}" dir="${compiler}"
> > > failonerror="true" >
> > > >>> > <arg value="commit" />
> > > >>> > <arg value="-m" />
> > > >>> > <arg value="update version to
> > > ${new.release.version}"
> > > >>> />
> > > >>> > </exec>
> > > >>> >
> > > >>> > [1]
> > > >>>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=vVBlXC7nYVUkQAFYGZvqH1kq6uV5WeI%2BCG5W2nyYFEE%3D&reserved=0
> > > >>>
> > > >>> You did not post the whole log, so it is possible
> you missed
> > a
> > > step.
> > > >>> There is almost no way there shouldn't be changes
> and the
> > head
> > > should not
> > > >>> be detached.
> > > >>>
> > > >>> -Alex
> > > >>>
> > > >>>
> > > >>
> > > >> --
> > > >>
> > > >> Piotr Zarzycki
> > > >>
> > > >> Patreon: *
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >> <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >*
> > > >>
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > > <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >*
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > >*
> > >
> > >
> > >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >*
> >
> >
> >
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I found some time to try the releasecandidate.xml and found the problem. I pushed the fix to release/0.9.6. So try that and see what happens. It seemed to do the right thing for me on my Windows computer.
You will next likely run into several merge conflicts. I have not looked into the conflicts, but there is a good chance that some of that is due to the cherry-picking. I am going to start a separate thread about branch management.
-Alex
On 10/4/19, 10:55 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
If we don't fix the release scripts, then the next RM is probably going to run into the same problem. The time we spend now helps save time in the future. It is wise to improve the process now in case I get run over by a bus tomorrow. If you do it manually and make a mistake, we might not catch it until later or cause more problems.
IIRC, the Poms should not require changing. Maven should have done that already.
All the places I know of changing are in the script.
-Alex
On 10/4/19, 10:46 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Alex,
Can I just do that changes manually on release branch and merge stuff to
develop?
I just don't won't to spend any more minute on release process anymore.
1) I should change build properties
2) I should change all poms
Is there anymore place which I should know to change?
Thanks,
Piotr
On Fri, Oct 4, 2019, 7:41 PM Alex Harui <ah...@adobe.com.invalid> wrote:
> Piotr,
>
> Again, I am asking you to get in the mindset of a developer and not just a
> user. You can see that the Ant script is making some updates. You can
> verify that the release branch does not have 0.9.7 for the release.version
> in build.properties. You can see there is 1 commit pending in
> royale-asjs. You can see that the build.properties did get changed to have
> release.version=0.9.7.
>
> So, you will have to investigate further. What is in that commit? Is
> this output from a fresh start of cloning the repo or could that commit be
> from a previous run? How could Git change a file but not report it? Maybe
> add some <echo> tags or use -verbose to get more output. But just giving
> me minimal information and waiting for me to guess as to what to do next is
> not very efficient, IMO.
>
> Thanks,
> -Alex
>
> On 10/4/19, 4:01 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Hi Alex,
>
> Git status after failing for all 3 repos [1].
>
> Here is how build.properties look like after performing update.versions
> target [2].
>
> I will skip some part to move forward but update.versions is important.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=nvSDESjmBw5j%2FlBoaIPGTUiBKrkoXcAVGIyUV371eE8%3D&reserved=0
> [2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvou&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=ljQmwiJbtqsTIj3tx9%2FtKyy%2Bns5Sz7P%2BCQE3Knb%2F1fA%3D&reserved=0
>
> Thanks,
> Piotr
>
> czw., 3 paź 2019 o 17:49 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
>
> > What does "git status" show in the 3 repos?
> >
> > The update.versions should have at least changed the
> build.properties file
> > in the repo.
> >
> > You can try skipping over steps by listing the steps on the command
> line.
> > You might need to list some pre-requisite steps before or add them
> to the
> > "depends" of the step that needs it.
> >
> > ant -e -f releasecandidate.xml -Drelease.version=0.9.6 -Drc=3
> > update.versions merge_rc_to_develop release.maven.staging.repo
> >
> > -Alex
> >
> > On 10/3/19, 1:49 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Those are the steps from the script which need to be done still:
> >
> > 1) <antcall target="update.versions" />
> > 2) <antcall target="merge_rc_to_develop" />
> > 3) <antcall target="release.maven.staging.repo" />
> >
> > Number #1 is failing.
> >
> >
> > czw., 3 paź 2019 o 10:41 Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > napisał(a):
> >
> > > It looks like we already have:
> > > 1) Successfully published npm:
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=HBSzGRshuTJ2xDFdHeLsUs6INhVdTygxlhVnJG18h4Q%3D&reserved=0
> > > 2) Successfully published which can be updated on the website:
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=Aom6KVIcuGyMhaH6Tih1GOD7TWklkr40GSXsy4Drp7o%3D&reserved=0
> > >
> > > Thanks,
> > > Piotr
> > >
> > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > > napisał(a):
> > >
> > >> I have used npm password from private and went trough
> publishing
> > npm and
> > >> it's failed on next step update.version with the same error.
> Here
> > you go
> > >> full log [1].
> > >>
> > >> What will happen if I run publish npm stuff again ? I can
> omit that
> > part
> > >> in the next attempt.
> > >>
> > >> Om can you check whether my npm publish stuff went ok ?
> > >>
> > >> [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=cT350bhfIX2sL59mnbWF7sffIHN%2BhgTaCiPR%2B3AYtKQ%3D&reserved=0
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> śr., 2 paź 2019 o 18:40 Alex Harui <ah...@adobe.com.invalid>
> > napisał(a):
> > >>
> > >>> Responses inline...
> > >>>
> > >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com>
> > >>> wrote:
> > >>>
> > >>> Just to understand something. releasecandidate script is
> using
> > tag
> > >>> instead
> > >>> release branch to whole operation of increase version ?
> > >>>
> > >>> No, the "get_head_of_rc_branches" target should get you the
> head.
> > >>>
> > >>> > Hi,
> > >>> >
> > >>> > I just tried releasecandidate script. It contains
> following
> > steps.
> > >>> >
> > >>> > <antcall target="release.tag" />
> > >>> > <!-- this is intended to merge the tag to
> master
> > because
> > >>> it should
> > >>> > have the right versions in it -->
> > >>> > <antcall target="merge_rc_to_master" />
> > >>> > <antcall target="get_head_of_rc_branches" />
> > >>> > <antcall target="release.npm" />
> > >>> > <antcall target="update.versions" />
> > >>> > <antcall target="merge_rc_to_develop" />
> > >>> > <antcall target="release.maven.staging.repo" />
> > >>> >
> > >>> > One step previous was move in svn binaries from dev
> folder to
> > >>> release - I
> > >>> > omit that cause I did it already manually. Launching
> > following
> > >>> steps I
> > >>> > reached release.npm - Which requires login and
> password to
> > npm - I
> > >>> > omitted that as well. Next was update.versions and it
> failed
> > with
> > >>> following
> > >>> > stack trace [1]
> > >>> >
> > >>>
> > >>> The login and password is available in the private@
> archives.
> > >>>
> > >>>
> > >>> > In mentioned lines in the stacktrace I have:
> > >>> >
> > >>> > Line 1088:
> > >>> > <antcall target="update.versions" />
> > >>> >
> > >>> > Line 1216:
> > >>> > <exec executable="${git}" dir="${compiler}"
> > failonerror="true" >
> > >>> > <arg value="commit" />
> > >>> > <arg value="-m" />
> > >>> > <arg value="update version to
> > ${new.release.version}"
> > >>> />
> > >>> > </exec>
> > >>> >
> > >>> > [1]
> > >>>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010&sdata=vVBlXC7nYVUkQAFYGZvqH1kq6uV5WeI%2BCG5W2nyYFEE%3D&reserved=0
> > >>>
> > >>> You did not post the whole log, so it is possible you missed
> a
> > step.
> > >>> There is almost no way there shouldn't be changes and the
> head
> > should not
> > >>> be detached.
> > >>>
> > >>> -Alex
> > >>>
> > >>>
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >> <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >*
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> > >*
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331729004&sdata=DtkqAnAr82aCGscm196qyKrdwTVOyNMJeqM5vRfvpiA%3D&reserved=0
> >*
>
>
>
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Alex Harui <ah...@adobe.com.INVALID>.
If we don't fix the release scripts, then the next RM is probably going to run into the same problem. The time we spend now helps save time in the future. It is wise to improve the process now in case I get run over by a bus tomorrow. If you do it manually and make a mistake, we might not catch it until later or cause more problems.
IIRC, the Poms should not require changing. Maven should have done that already.
All the places I know of changing are in the script.
-Alex
On 10/4/19, 10:46 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Alex,
Can I just do that changes manually on release branch and merge stuff to
develop?
I just don't won't to spend any more minute on release process anymore.
1) I should change build properties
2) I should change all poms
Is there anymore place which I should know to change?
Thanks,
Piotr
On Fri, Oct 4, 2019, 7:41 PM Alex Harui <ah...@adobe.com.invalid> wrote:
> Piotr,
>
> Again, I am asking you to get in the mindset of a developer and not just a
> user. You can see that the Ant script is making some updates. You can
> verify that the release branch does not have 0.9.7 for the release.version
> in build.properties. You can see there is 1 commit pending in
> royale-asjs. You can see that the build.properties did get changed to have
> release.version=0.9.7.
>
> So, you will have to investigate further. What is in that commit? Is
> this output from a fresh start of cloning the repo or could that commit be
> from a previous run? How could Git change a file but not report it? Maybe
> add some <echo> tags or use -verbose to get more output. But just giving
> me minimal information and waiting for me to guess as to what to do next is
> not very efficient, IMO.
>
> Thanks,
> -Alex
>
> On 10/4/19, 4:01 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Hi Alex,
>
> Git status after failing for all 3 repos [1].
>
> Here is how build.properties look like after performing update.versions
> target [2].
>
> I will skip some part to move forward but update.versions is important.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114668654&sdata=Eabe%2BihRxhaEOgJlRj3XwIL%2BlidBAd5FTFhVoHfXBoM%3D&reserved=0
> [2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvou&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114668654&sdata=A16mYpPcwNwWhDp7UcWnEPBazsYxcUUvpfGVXJw3xrs%3D&reserved=0
>
> Thanks,
> Piotr
>
> czw., 3 paź 2019 o 17:49 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
>
> > What does "git status" show in the 3 repos?
> >
> > The update.versions should have at least changed the
> build.properties file
> > in the repo.
> >
> > You can try skipping over steps by listing the steps on the command
> line.
> > You might need to list some pre-requisite steps before or add them
> to the
> > "depends" of the step that needs it.
> >
> > ant -e -f releasecandidate.xml -Drelease.version=0.9.6 -Drc=3
> > update.versions merge_rc_to_develop release.maven.staging.repo
> >
> > -Alex
> >
> > On 10/3/19, 1:49 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Those are the steps from the script which need to be done still:
> >
> > 1) <antcall target="update.versions" />
> > 2) <antcall target="merge_rc_to_develop" />
> > 3) <antcall target="release.maven.staging.repo" />
> >
> > Number #1 is failing.
> >
> >
> > czw., 3 paź 2019 o 10:41 Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > napisał(a):
> >
> > > It looks like we already have:
> > > 1) Successfully published npm:
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114668654&sdata=on7rGMQu6TJkkyOZlBNYViAEL9BoZvMzFs0W1VR64IU%3D&reserved=0
> > > 2) Successfully published which can be updated on the website:
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=rhUFPvh70ZPm3pi04pnf7HFxZNfTaNcOFe88JndpEmU%3D&reserved=0
> > >
> > > Thanks,
> > > Piotr
> > >
> > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > > napisał(a):
> > >
> > >> I have used npm password from private and went trough
> publishing
> > npm and
> > >> it's failed on next step update.version with the same error.
> Here
> > you go
> > >> full log [1].
> > >>
> > >> What will happen if I run publish npm stuff again ? I can
> omit that
> > part
> > >> in the next attempt.
> > >>
> > >> Om can you check whether my npm publish stuff went ok ?
> > >>
> > >> [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=9J%2F1abydKn%2Fx7kmcTqnXHYjiItytajaY8pQ77KrMYpk%3D&reserved=0
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> śr., 2 paź 2019 o 18:40 Alex Harui <ah...@adobe.com.invalid>
> > napisał(a):
> > >>
> > >>> Responses inline...
> > >>>
> > >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com>
> > >>> wrote:
> > >>>
> > >>> Just to understand something. releasecandidate script is
> using
> > tag
> > >>> instead
> > >>> release branch to whole operation of increase version ?
> > >>>
> > >>> No, the "get_head_of_rc_branches" target should get you the
> head.
> > >>>
> > >>> > Hi,
> > >>> >
> > >>> > I just tried releasecandidate script. It contains
> following
> > steps.
> > >>> >
> > >>> > <antcall target="release.tag" />
> > >>> > <!-- this is intended to merge the tag to
> master
> > because
> > >>> it should
> > >>> > have the right versions in it -->
> > >>> > <antcall target="merge_rc_to_master" />
> > >>> > <antcall target="get_head_of_rc_branches" />
> > >>> > <antcall target="release.npm" />
> > >>> > <antcall target="update.versions" />
> > >>> > <antcall target="merge_rc_to_develop" />
> > >>> > <antcall target="release.maven.staging.repo" />
> > >>> >
> > >>> > One step previous was move in svn binaries from dev
> folder to
> > >>> release - I
> > >>> > omit that cause I did it already manually. Launching
> > following
> > >>> steps I
> > >>> > reached release.npm - Which requires login and
> password to
> > npm - I
> > >>> > omitted that as well. Next was update.versions and it
> failed
> > with
> > >>> following
> > >>> > stack trace [1]
> > >>> >
> > >>>
> > >>> The login and password is available in the private@
> archives.
> > >>>
> > >>>
> > >>> > In mentioned lines in the stacktrace I have:
> > >>> >
> > >>> > Line 1088:
> > >>> > <antcall target="update.versions" />
> > >>> >
> > >>> > Line 1216:
> > >>> > <exec executable="${git}" dir="${compiler}"
> > failonerror="true" >
> > >>> > <arg value="commit" />
> > >>> > <arg value="-m" />
> > >>> > <arg value="update version to
> > ${new.release.version}"
> > >>> />
> > >>> > </exec>
> > >>> >
> > >>> > [1]
> > >>>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=dkzkwLsdLkcWIlaMKSl1UnEC%2FPdA58uTM8mnbkRxkOM%3D&reserved=0
> > >>>
> > >>> You did not post the whole log, so it is possible you missed
> a
> > step.
> > >>> There is almost no way there shouldn't be changes and the
> head
> > should not
> > >>> be detached.
> > >>>
> > >>> -Alex
> > >>>
> > >>>
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=qbHIXUYLD6RrWIy2QcuiIGy0G1hUXm1P%2FbRj6yd0VBM%3D&reserved=0
> > >> <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=qbHIXUYLD6RrWIy2QcuiIGy0G1hUXm1P%2FbRj6yd0VBM%3D&reserved=0
> > >*
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=qbHIXUYLD6RrWIy2QcuiIGy0G1hUXm1P%2FbRj6yd0VBM%3D&reserved=0
> > > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=qbHIXUYLD6RrWIy2QcuiIGy0G1hUXm1P%2FbRj6yd0VBM%3D&reserved=0
> > >*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=qbHIXUYLD6RrWIy2QcuiIGy0G1hUXm1P%2FbRj6yd0VBM%3D&reserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=qbHIXUYLD6RrWIy2QcuiIGy0G1hUXm1P%2FbRj6yd0VBM%3D&reserved=0
> > >*
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648&sdata=qbHIXUYLD6RrWIy2QcuiIGy0G1hUXm1P%2FbRj6yd0VBM%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114688645&sdata=ebhgEzFuI5%2BXv5g7pwLsl86Q44JJ3JDNnC4dm5HMGpg%3D&reserved=0
> >*
>
>
>
[DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
Alex,
Can I just do that changes manually on release branch and merge stuff to
develop?
I just don't won't to spend any more minute on release process anymore.
1) I should change build properties
2) I should change all poms
Is there anymore place which I should know to change?
Thanks,
Piotr
On Fri, Oct 4, 2019, 7:41 PM Alex Harui <ah...@adobe.com.invalid> wrote:
> Piotr,
>
> Again, I am asking you to get in the mindset of a developer and not just a
> user. You can see that the Ant script is making some updates. You can
> verify that the release branch does not have 0.9.7 for the release.version
> in build.properties. You can see there is 1 commit pending in
> royale-asjs. You can see that the build.properties did get changed to have
> release.version=0.9.7.
>
> So, you will have to investigate further. What is in that commit? Is
> this output from a fresh start of cloning the repo or could that commit be
> from a previous run? How could Git change a file but not report it? Maybe
> add some <echo> tags or use -verbose to get more output. But just giving
> me minimal information and waiting for me to guess as to what to do next is
> not very efficient, IMO.
>
> Thanks,
> -Alex
>
> On 10/4/19, 4:01 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Hi Alex,
>
> Git status after failing for all 3 repos [1].
>
> Here is how build.properties look like after performing update.versions
> target [2].
>
> I will skip some part to move forward but update.versions is important.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=xBLjNOwyVKVNWQyKw%2F2%2F2pJD5KKl5ZgzxbCxoaVPrSI%3D&reserved=0
> [2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvou&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=nmPTpAqG5dWUT%2BglHfM%2BQwpUEzvL%2F59P9GQ%2BqYQUvEs%3D&reserved=0
>
> Thanks,
> Piotr
>
> czw., 3 paź 2019 o 17:49 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
>
> > What does "git status" show in the 3 repos?
> >
> > The update.versions should have at least changed the
> build.properties file
> > in the repo.
> >
> > You can try skipping over steps by listing the steps on the command
> line.
> > You might need to list some pre-requisite steps before or add them
> to the
> > "depends" of the step that needs it.
> >
> > ant -e -f releasecandidate.xml -Drelease.version=0.9.6 -Drc=3
> > update.versions merge_rc_to_develop release.maven.staging.repo
> >
> > -Alex
> >
> > On 10/3/19, 1:49 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Those are the steps from the script which need to be done still:
> >
> > 1) <antcall target="update.versions" />
> > 2) <antcall target="merge_rc_to_develop" />
> > 3) <antcall target="release.maven.staging.repo" />
> >
> > Number #1 is failing.
> >
> >
> > czw., 3 paź 2019 o 10:41 Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > napisał(a):
> >
> > > It looks like we already have:
> > > 1) Successfully published npm:
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=m35lsvR0DTt5MVy0Y5pgDbcIaUexq72ZnmMNjaeakJI%3D&reserved=0
> > > 2) Successfully published which can be updated on the website:
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=bHENqecd10JZ0BvQvyDsgYXNm%2FHSAIZYM%2F5aKmifyr8%3D&reserved=0
> > >
> > > Thanks,
> > > Piotr
> > >
> > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > > napisał(a):
> > >
> > >> I have used npm password from private and went trough
> publishing
> > npm and
> > >> it's failed on next step update.version with the same error.
> Here
> > you go
> > >> full log [1].
> > >>
> > >> What will happen if I run publish npm stuff again ? I can
> omit that
> > part
> > >> in the next attempt.
> > >>
> > >> Om can you check whether my npm publish stuff went ok ?
> > >>
> > >> [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=yusB%2Bj5z5%2BZZsOFkUS8X4FKK0OYJnRK0EvTf9aBK7Uo%3D&reserved=0
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> śr., 2 paź 2019 o 18:40 Alex Harui <ah...@adobe.com.invalid>
> > napisał(a):
> > >>
> > >>> Responses inline...
> > >>>
> > >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com>
> > >>> wrote:
> > >>>
> > >>> Just to understand something. releasecandidate script is
> using
> > tag
> > >>> instead
> > >>> release branch to whole operation of increase version ?
> > >>>
> > >>> No, the "get_head_of_rc_branches" target should get you the
> head.
> > >>>
> > >>> > Hi,
> > >>> >
> > >>> > I just tried releasecandidate script. It contains
> following
> > steps.
> > >>> >
> > >>> > <antcall target="release.tag" />
> > >>> > <!-- this is intended to merge the tag to
> master
> > because
> > >>> it should
> > >>> > have the right versions in it -->
> > >>> > <antcall target="merge_rc_to_master" />
> > >>> > <antcall target="get_head_of_rc_branches" />
> > >>> > <antcall target="release.npm" />
> > >>> > <antcall target="update.versions" />
> > >>> > <antcall target="merge_rc_to_develop" />
> > >>> > <antcall target="release.maven.staging.repo" />
> > >>> >
> > >>> > One step previous was move in svn binaries from dev
> folder to
> > >>> release - I
> > >>> > omit that cause I did it already manually. Launching
> > following
> > >>> steps I
> > >>> > reached release.npm - Which requires login and
> password to
> > npm - I
> > >>> > omitted that as well. Next was update.versions and it
> failed
> > with
> > >>> following
> > >>> > stack trace [1]
> > >>> >
> > >>>
> > >>> The login and password is available in the private@
> archives.
> > >>>
> > >>>
> > >>> > In mentioned lines in the stacktrace I have:
> > >>> >
> > >>> > Line 1088:
> > >>> > <antcall target="update.versions" />
> > >>> >
> > >>> > Line 1216:
> > >>> > <exec executable="${git}" dir="${compiler}"
> > failonerror="true" >
> > >>> > <arg value="commit" />
> > >>> > <arg value="-m" />
> > >>> > <arg value="update version to
> > ${new.release.version}"
> > >>> />
> > >>> > </exec>
> > >>> >
> > >>> > [1]
> > >>>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=j0L9S186%2Bv62nrVCd4%2FIla6M4FhuEHH%2FsPOvFOkEQEc%3D&reserved=0
> > >>>
> > >>> You did not post the whole log, so it is possible you missed
> a
> > step.
> > >>> There is almost no way there shouldn't be changes and the
> head
> > should not
> > >>> be detached.
> > >>>
> > >>> -Alex
> > >>>
> > >>>
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=BC3PliN2649MpSQtqofNyzCoRmayFyA%2BjWaqpRIyt0I%3D&reserved=0
> > >> <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> > >*
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> > > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> > >*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> > >*
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> >*
>
>
>
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Piotr,
Again, I am asking you to get in the mindset of a developer and not just a user. You can see that the Ant script is making some updates. You can verify that the release branch does not have 0.9.7 for the release.version in build.properties. You can see there is 1 commit pending in royale-asjs. You can see that the build.properties did get changed to have release.version=0.9.7.
So, you will have to investigate further. What is in that commit? Is this output from a fresh start of cloning the repo or could that commit be from a previous run? How could Git change a file but not report it? Maybe add some <echo> tags or use -verbose to get more output. But just giving me minimal information and waiting for me to guess as to what to do next is not very efficient, IMO.
Thanks,
-Alex
On 10/4/19, 4:01 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Hi Alex,
Git status after failing for all 3 repos [1].
Here is how build.properties look like after performing update.versions
target [2].
I will skip some part to move forward but update.versions is important.
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=xBLjNOwyVKVNWQyKw%2F2%2F2pJD5KKl5ZgzxbCxoaVPrSI%3D&reserved=0
[2] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvou&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=nmPTpAqG5dWUT%2BglHfM%2BQwpUEzvL%2F59P9GQ%2BqYQUvEs%3D&reserved=0
Thanks,
Piotr
czw., 3 paź 2019 o 17:49 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> What does "git status" show in the 3 repos?
>
> The update.versions should have at least changed the build.properties file
> in the repo.
>
> You can try skipping over steps by listing the steps on the command line.
> You might need to list some pre-requisite steps before or add them to the
> "depends" of the step that needs it.
>
> ant -e -f releasecandidate.xml -Drelease.version=0.9.6 -Drc=3
> update.versions merge_rc_to_develop release.maven.staging.repo
>
> -Alex
>
> On 10/3/19, 1:49 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Those are the steps from the script which need to be done still:
>
> 1) <antcall target="update.versions" />
> 2) <antcall target="merge_rc_to_develop" />
> 3) <antcall target="release.maven.staging.repo" />
>
> Number #1 is failing.
>
>
> czw., 3 paź 2019 o 10:41 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > It looks like we already have:
> > 1) Successfully published npm:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=m35lsvR0DTt5MVy0Y5pgDbcIaUexq72ZnmMNjaeakJI%3D&reserved=0
> > 2) Successfully published which can be updated on the website:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=bHENqecd10JZ0BvQvyDsgYXNm%2FHSAIZYM%2F5aKmifyr8%3D&reserved=0
> >
> > Thanks,
> > Piotr
> >
> > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> >> I have used npm password from private and went trough publishing
> npm and
> >> it's failed on next step update.version with the same error. Here
> you go
> >> full log [1].
> >>
> >> What will happen if I run publish npm stuff again ? I can omit that
> part
> >> in the next attempt.
> >>
> >> Om can you check whether my npm publish stuff went ok ?
> >>
> >> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=yusB%2Bj5z5%2BZZsOFkUS8X4FKK0OYJnRK0EvTf9aBK7Uo%3D&reserved=0
> >>
> >> Thanks,
> >> Piotr
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 2 paź 2019 o 18:40 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
> >>
> >>> Responses inline...
> >>>
> >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <pi...@gmail.com>
> >>> wrote:
> >>>
> >>> Just to understand something. releasecandidate script is using
> tag
> >>> instead
> >>> release branch to whole operation of increase version ?
> >>>
> >>> No, the "get_head_of_rc_branches" target should get you the head.
> >>>
> >>> > Hi,
> >>> >
> >>> > I just tried releasecandidate script. It contains following
> steps.
> >>> >
> >>> > <antcall target="release.tag" />
> >>> > <!-- this is intended to merge the tag to master
> because
> >>> it should
> >>> > have the right versions in it -->
> >>> > <antcall target="merge_rc_to_master" />
> >>> > <antcall target="get_head_of_rc_branches" />
> >>> > <antcall target="release.npm" />
> >>> > <antcall target="update.versions" />
> >>> > <antcall target="merge_rc_to_develop" />
> >>> > <antcall target="release.maven.staging.repo" />
> >>> >
> >>> > One step previous was move in svn binaries from dev folder to
> >>> release - I
> >>> > omit that cause I did it already manually. Launching
> following
> >>> steps I
> >>> > reached release.npm - Which requires login and password to
> npm - I
> >>> > omitted that as well. Next was update.versions and it failed
> with
> >>> following
> >>> > stack trace [1]
> >>> >
> >>>
> >>> The login and password is available in the private@ archives.
> >>>
> >>>
> >>> > In mentioned lines in the stacktrace I have:
> >>> >
> >>> > Line 1088:
> >>> > <antcall target="update.versions" />
> >>> >
> >>> > Line 1216:
> >>> > <exec executable="${git}" dir="${compiler}"
> failonerror="true" >
> >>> > <arg value="commit" />
> >>> > <arg value="-m" />
> >>> > <arg value="update version to
> ${new.release.version}"
> >>> />
> >>> > </exec>
> >>> >
> >>> > [1]
> >>>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=j0L9S186%2Bv62nrVCd4%2FIla6M4FhuEHH%2FsPOvFOkEQEc%3D&reserved=0
> >>>
> >>> You did not post the whole log, so it is possible you missed a
> step.
> >>> There is almost no way there shouldn't be changes and the head
> should not
> >>> be detached.
> >>>
> >>> -Alex
> >>>
> >>>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594&sdata=BC3PliN2649MpSQtqofNyzCoRmayFyA%2BjWaqpRIyt0I%3D&reserved=0
> >> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> >*
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> >*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
> >*
>
>
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153215593&sdata=bXLy3D4xuipGD5McAFmWZ%2FDzsrIWHa6BRXFZkImph0U%3D&reserved=0>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
Git status after failing for all 3 repos [1].
Here is how build.properties look like after performing update.versions
target [2].
I will skip some part to move forward but update.versions is important.
[1] https://paste.apache.org/l3zs9
[2] https://paste.apache.org/0zvou
Thanks,
Piotr
czw., 3 paź 2019 o 17:49 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> What does "git status" show in the 3 repos?
>
> The update.versions should have at least changed the build.properties file
> in the repo.
>
> You can try skipping over steps by listing the steps on the command line.
> You might need to list some pre-requisite steps before or add them to the
> "depends" of the step that needs it.
>
> ant -e -f releasecandidate.xml -Drelease.version=0.9.6 -Drc=3
> update.versions merge_rc_to_develop release.maven.staging.repo
>
> -Alex
>
> On 10/3/19, 1:49 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Those are the steps from the script which need to be done still:
>
> 1) <antcall target="update.versions" />
> 2) <antcall target="merge_rc_to_develop" />
> 3) <antcall target="release.maven.staging.repo" />
>
> Number #1 is failing.
>
>
> czw., 3 paź 2019 o 10:41 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > It looks like we already have:
> > 1) Successfully published npm:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810206817&sdata=4idQHiSsqaCC57d%2FMoZYx%2Bze3xZRLwrahAJhYykR2WI%3D&reserved=0
> > 2) Successfully published which can be updated on the website:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810206817&sdata=piwVUdIWhFhDZTIjKG9CCTkJBuzx5QKitI%2F%2BYSYyv0A%3D&reserved=0
> >
> > Thanks,
> > Piotr
> >
> > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> >> I have used npm password from private and went trough publishing
> npm and
> >> it's failed on next step update.version with the same error. Here
> you go
> >> full log [1].
> >>
> >> What will happen if I run publish npm stuff again ? I can omit that
> part
> >> in the next attempt.
> >>
> >> Om can you check whether my npm publish stuff went ok ?
> >>
> >> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810206817&sdata=K3Jqc8tjhRGyCjE2vHIzVyDQ070L3HYxLzjBNFzrtdI%3D&reserved=0
> >>
> >> Thanks,
> >> Piotr
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 2 paź 2019 o 18:40 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
> >>
> >>> Responses inline...
> >>>
> >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <pi...@gmail.com>
> >>> wrote:
> >>>
> >>> Just to understand something. releasecandidate script is using
> tag
> >>> instead
> >>> release branch to whole operation of increase version ?
> >>>
> >>> No, the "get_head_of_rc_branches" target should get you the head.
> >>>
> >>> > Hi,
> >>> >
> >>> > I just tried releasecandidate script. It contains following
> steps.
> >>> >
> >>> > <antcall target="release.tag" />
> >>> > <!-- this is intended to merge the tag to master
> because
> >>> it should
> >>> > have the right versions in it -->
> >>> > <antcall target="merge_rc_to_master" />
> >>> > <antcall target="get_head_of_rc_branches" />
> >>> > <antcall target="release.npm" />
> >>> > <antcall target="update.versions" />
> >>> > <antcall target="merge_rc_to_develop" />
> >>> > <antcall target="release.maven.staging.repo" />
> >>> >
> >>> > One step previous was move in svn binaries from dev folder to
> >>> release - I
> >>> > omit that cause I did it already manually. Launching
> following
> >>> steps I
> >>> > reached release.npm - Which requires login and password to
> npm - I
> >>> > omitted that as well. Next was update.versions and it failed
> with
> >>> following
> >>> > stack trace [1]
> >>> >
> >>>
> >>> The login and password is available in the private@ archives.
> >>>
> >>>
> >>> > In mentioned lines in the stacktrace I have:
> >>> >
> >>> > Line 1088:
> >>> > <antcall target="update.versions" />
> >>> >
> >>> > Line 1216:
> >>> > <exec executable="${git}" dir="${compiler}"
> failonerror="true" >
> >>> > <arg value="commit" />
> >>> > <arg value="-m" />
> >>> > <arg value="update version to
> ${new.release.version}"
> >>> />
> >>> > </exec>
> >>> >
> >>> > [1]
> >>>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=Rh%2BpFQBRbL6mWzbRaSdIWJV3zA1N0rjMbHDUTGGLzsA%3D&reserved=0
> >>>
> >>> You did not post the whole log, so it is possible you missed a
> step.
> >>> There is almost no way there shouldn't be changes and the head
> should not
> >>> be detached.
> >>>
> >>> -Alex
> >>>
> >>>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0
> >> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0
> >*
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0
> >*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0
> >*
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Alex Harui <ah...@adobe.com.INVALID>.
What does "git status" show in the 3 repos?
The update.versions should have at least changed the build.properties file in the repo.
You can try skipping over steps by listing the steps on the command line. You might need to list some pre-requisite steps before or add them to the "depends" of the step that needs it.
ant -e -f releasecandidate.xml -Drelease.version=0.9.6 -Drc=3 update.versions merge_rc_to_develop release.maven.staging.repo
-Alex
On 10/3/19, 1:49 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Those are the steps from the script which need to be done still:
1) <antcall target="update.versions" />
2) <antcall target="merge_rc_to_develop" />
3) <antcall target="release.maven.staging.repo" />
Number #1 is failing.
czw., 3 paź 2019 o 10:41 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> It looks like we already have:
> 1) Successfully published npm:
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-js&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810206817&sdata=4idQHiSsqaCC57d%2FMoZYx%2Bze3xZRLwrahAJhYykR2WI%3D&reserved=0
> 2) Successfully published which can be updated on the website:
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810206817&sdata=piwVUdIWhFhDZTIjKG9CCTkJBuzx5QKitI%2F%2BYSYyv0A%3D&reserved=0
>
> Thanks,
> Piotr
>
> czw., 3 paź 2019 o 10:33 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> I have used npm password from private and went trough publishing npm and
>> it's failed on next step update.version with the same error. Here you go
>> full log [1].
>>
>> What will happen if I run publish npm stuff again ? I can omit that part
>> in the next attempt.
>>
>> Om can you check whether my npm publish stuff went ok ?
>>
>> [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06d&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810206817&sdata=K3Jqc8tjhRGyCjE2vHIzVyDQ070L3HYxLzjBNFzrtdI%3D&reserved=0
>>
>> Thanks,
>> Piotr
>>
>> Thanks,
>> Piotr
>>
>> śr., 2 paź 2019 o 18:40 Alex Harui <ah...@adobe.com.invalid> napisał(a):
>>
>>> Responses inline...
>>>
>>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <pi...@gmail.com>
>>> wrote:
>>>
>>> Just to understand something. releasecandidate script is using tag
>>> instead
>>> release branch to whole operation of increase version ?
>>>
>>> No, the "get_head_of_rc_branches" target should get you the head.
>>>
>>> > Hi,
>>> >
>>> > I just tried releasecandidate script. It contains following steps.
>>> >
>>> > <antcall target="release.tag" />
>>> > <!-- this is intended to merge the tag to master because
>>> it should
>>> > have the right versions in it -->
>>> > <antcall target="merge_rc_to_master" />
>>> > <antcall target="get_head_of_rc_branches" />
>>> > <antcall target="release.npm" />
>>> > <antcall target="update.versions" />
>>> > <antcall target="merge_rc_to_develop" />
>>> > <antcall target="release.maven.staging.repo" />
>>> >
>>> > One step previous was move in svn binaries from dev folder to
>>> release - I
>>> > omit that cause I did it already manually. Launching following
>>> steps I
>>> > reached release.npm - Which requires login and password to npm - I
>>> > omitted that as well. Next was update.versions and it failed with
>>> following
>>> > stack trace [1]
>>> >
>>>
>>> The login and password is available in the private@ archives.
>>>
>>>
>>> > In mentioned lines in the stacktrace I have:
>>> >
>>> > Line 1088:
>>> > <antcall target="update.versions" />
>>> >
>>> > Line 1216:
>>> > <exec executable="${git}" dir="${compiler}" failonerror="true" >
>>> > <arg value="commit" />
>>> > <arg value="-m" />
>>> > <arg value="update version to ${new.release.version}"
>>> />
>>> > </exec>
>>> >
>>> > [1]
>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=Rh%2BpFQBRbL6mWzbRaSdIWJV3zA1N0rjMbHDUTGGLzsA%3D&reserved=0
>>>
>>> You did not post the whole log, so it is possible you missed a step.
>>> There is almost no way there shouldn't be changes and the head should not
>>> be detached.
>>>
>>> -Alex
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0
>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0>*
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809&sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3D&reserved=0>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
Those are the steps from the script which need to be done still:
1) <antcall target="update.versions" />
2) <antcall target="merge_rc_to_develop" />
3) <antcall target="release.maven.staging.repo" />
Number #1 is failing.
czw., 3 paź 2019 o 10:41 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> It looks like we already have:
> 1) Successfully published npm:
> https://www.npmjs.com/package/@apache-royale/royale-js
> 2) Successfully published which can be updated on the website:
> https://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz
>
> Thanks,
> Piotr
>
> czw., 3 paź 2019 o 10:33 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> I have used npm password from private and went trough publishing npm and
>> it's failed on next step update.version with the same error. Here you go
>> full log [1].
>>
>> What will happen if I run publish npm stuff again ? I can omit that part
>> in the next attempt.
>>
>> Om can you check whether my npm publish stuff went ok ?
>>
>> [1] https://paste.apache.org/yl06d
>>
>> Thanks,
>> Piotr
>>
>> Thanks,
>> Piotr
>>
>> śr., 2 paź 2019 o 18:40 Alex Harui <ah...@adobe.com.invalid> napisał(a):
>>
>>> Responses inline...
>>>
>>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <pi...@gmail.com>
>>> wrote:
>>>
>>> Just to understand something. releasecandidate script is using tag
>>> instead
>>> release branch to whole operation of increase version ?
>>>
>>> No, the "get_head_of_rc_branches" target should get you the head.
>>>
>>> > Hi,
>>> >
>>> > I just tried releasecandidate script. It contains following steps.
>>> >
>>> > <antcall target="release.tag" />
>>> > <!-- this is intended to merge the tag to master because
>>> it should
>>> > have the right versions in it -->
>>> > <antcall target="merge_rc_to_master" />
>>> > <antcall target="get_head_of_rc_branches" />
>>> > <antcall target="release.npm" />
>>> > <antcall target="update.versions" />
>>> > <antcall target="merge_rc_to_develop" />
>>> > <antcall target="release.maven.staging.repo" />
>>> >
>>> > One step previous was move in svn binaries from dev folder to
>>> release - I
>>> > omit that cause I did it already manually. Launching following
>>> steps I
>>> > reached release.npm - Which requires login and password to npm - I
>>> > omitted that as well. Next was update.versions and it failed with
>>> following
>>> > stack trace [1]
>>> >
>>>
>>> The login and password is available in the private@ archives.
>>>
>>>
>>> > In mentioned lines in the stacktrace I have:
>>> >
>>> > Line 1088:
>>> > <antcall target="update.versions" />
>>> >
>>> > Line 1216:
>>> > <exec executable="${git}" dir="${compiler}" failonerror="true" >
>>> > <arg value="commit" />
>>> > <arg value="-m" />
>>> > <arg value="update version to ${new.release.version}"
>>> />
>>> > </exec>
>>> >
>>> > [1]
>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Ca6fd586ab1f044a4b2c408d74713bf65%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056022453516542&sdata=usDOkcnLx4HhZJSYsMde5pnvgQMDyKLSIKeOccmCJkc%3D&reserved=0
>>>
>>> You did not post the whole log, so it is possible you missed a step.
>>> There is almost no way there shouldn't be changes and the head should not
>>> be detached.
>>>
>>> -Alex
>>>
>>>
>>
>> --
>>
>> 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>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
It looks like we already have:
1) Successfully published npm:
https://www.npmjs.com/package/@apache-royale/royale-js
2) Successfully published which can be updated on the website:
https://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz
Thanks,
Piotr
czw., 3 paź 2019 o 10:33 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> I have used npm password from private and went trough publishing npm and
> it's failed on next step update.version with the same error. Here you go
> full log [1].
>
> What will happen if I run publish npm stuff again ? I can omit that part
> in the next attempt.
>
> Om can you check whether my npm publish stuff went ok ?
>
> [1] https://paste.apache.org/yl06d
>
> Thanks,
> Piotr
>
> Thanks,
> Piotr
>
> śr., 2 paź 2019 o 18:40 Alex Harui <ah...@adobe.com.invalid> napisał(a):
>
>> Responses inline...
>>
>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>>
>> Just to understand something. releasecandidate script is using tag
>> instead
>> release branch to whole operation of increase version ?
>>
>> No, the "get_head_of_rc_branches" target should get you the head.
>>
>> > Hi,
>> >
>> > I just tried releasecandidate script. It contains following steps.
>> >
>> > <antcall target="release.tag" />
>> > <!-- this is intended to merge the tag to master because it
>> should
>> > have the right versions in it -->
>> > <antcall target="merge_rc_to_master" />
>> > <antcall target="get_head_of_rc_branches" />
>> > <antcall target="release.npm" />
>> > <antcall target="update.versions" />
>> > <antcall target="merge_rc_to_develop" />
>> > <antcall target="release.maven.staging.repo" />
>> >
>> > One step previous was move in svn binaries from dev folder to
>> release - I
>> > omit that cause I did it already manually. Launching following
>> steps I
>> > reached release.npm - Which requires login and password to npm - I
>> > omitted that as well. Next was update.versions and it failed with
>> following
>> > stack trace [1]
>> >
>>
>> The login and password is available in the private@ archives.
>>
>>
>> > In mentioned lines in the stacktrace I have:
>> >
>> > Line 1088:
>> > <antcall target="update.versions" />
>> >
>> > Line 1216:
>> > <exec executable="${git}" dir="${compiler}" failonerror="true" >
>> > <arg value="commit" />
>> > <arg value="-m" />
>> > <arg value="update version to ${new.release.version}" />
>> > </exec>
>> >
>> > [1]
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Ca6fd586ab1f044a4b2c408d74713bf65%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056022453516542&sdata=usDOkcnLx4HhZJSYsMde5pnvgQMDyKLSIKeOccmCJkc%3D&reserved=0
>>
>> You did not post the whole log, so it is possible you missed a step.
>> There is almost no way there shouldn't be changes and the head should not
>> be detached.
>>
>> -Alex
>>
>>
>
> --
>
> 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: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
I have used npm password from private and went trough publishing npm and
it's failed on next step update.version with the same error. Here you go
full log [1].
What will happen if I run publish npm stuff again ? I can omit that part in
the next attempt.
Om can you check whether my npm publish stuff went ok ?
[1] https://paste.apache.org/yl06d
Thanks,
Piotr
Thanks,
Piotr
śr., 2 paź 2019 o 18:40 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> Responses inline...
>
> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Just to understand something. releasecandidate script is using tag
> instead
> release branch to whole operation of increase version ?
>
> No, the "get_head_of_rc_branches" target should get you the head.
>
> > Hi,
> >
> > I just tried releasecandidate script. It contains following steps.
> >
> > <antcall target="release.tag" />
> > <!-- this is intended to merge the tag to master because it
> should
> > have the right versions in it -->
> > <antcall target="merge_rc_to_master" />
> > <antcall target="get_head_of_rc_branches" />
> > <antcall target="release.npm" />
> > <antcall target="update.versions" />
> > <antcall target="merge_rc_to_develop" />
> > <antcall target="release.maven.staging.repo" />
> >
> > One step previous was move in svn binaries from dev folder to
> release - I
> > omit that cause I did it already manually. Launching following steps
> I
> > reached release.npm - Which requires login and password to npm - I
> > omitted that as well. Next was update.versions and it failed with
> following
> > stack trace [1]
> >
>
> The login and password is available in the private@ archives.
>
>
> > In mentioned lines in the stacktrace I have:
> >
> > Line 1088:
> > <antcall target="update.versions" />
> >
> > Line 1216:
> > <exec executable="${git}" dir="${compiler}" failonerror="true" >
> > <arg value="commit" />
> > <arg value="-m" />
> > <arg value="update version to ${new.release.version}" />
> > </exec>
> >
> > [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Ca6fd586ab1f044a4b2c408d74713bf65%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056022453516542&sdata=usDOkcnLx4HhZJSYsMde5pnvgQMDyKLSIKeOccmCJkc%3D&reserved=0
>
> You did not post the whole log, so it is possible you missed a step.
> There is almost no way there shouldn't be changes and the head should not
> be detached.
>
> -Alex
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Responses inline...
On 10/2/19, 1:37 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Just to understand something. releasecandidate script is using tag instead
release branch to whole operation of increase version ?
No, the "get_head_of_rc_branches" target should get you the head.
> Hi,
>
> I just tried releasecandidate script. It contains following steps.
>
> <antcall target="release.tag" />
> <!-- this is intended to merge the tag to master because it should
> have the right versions in it -->
> <antcall target="merge_rc_to_master" />
> <antcall target="get_head_of_rc_branches" />
> <antcall target="release.npm" />
> <antcall target="update.versions" />
> <antcall target="merge_rc_to_develop" />
> <antcall target="release.maven.staging.repo" />
>
> One step previous was move in svn binaries from dev folder to release - I
> omit that cause I did it already manually. Launching following steps I
> reached release.npm - Which requires login and password to npm - I
> omitted that as well. Next was update.versions and it failed with following
> stack trace [1]
>
The login and password is available in the private@ archives.
> In mentioned lines in the stacktrace I have:
>
> Line 1088:
> <antcall target="update.versions" />
>
> Line 1216:
> <exec executable="${git}" dir="${compiler}" failonerror="true" >
> <arg value="commit" />
> <arg value="-m" />
> <arg value="update version to ${new.release.version}" />
> </exec>
>
> [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Ca6fd586ab1f044a4b2c408d74713bf65%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056022453516542&sdata=usDOkcnLx4HhZJSYsMde5pnvgQMDyKLSIKeOccmCJkc%3D&reserved=0
You did not post the whole log, so it is possible you missed a step. There is almost no way there shouldn't be changes and the head should not be detached.
-Alex
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
Just to understand something. releasecandidate script is using tag instead
release branch to whole operation of increase version ?
Cause on release branch I have already version increased, so what's the
point of doing anything using tag ?
śr., 2 paź 2019 o 10:27 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi,
>
> I just tried releasecandidate script. It contains following steps.
>
> <antcall target="release.tag" />
> <!-- this is intended to merge the tag to master because it should
> have the right versions in it -->
> <antcall target="merge_rc_to_master" />
> <antcall target="get_head_of_rc_branches" />
> <antcall target="release.npm" />
> <antcall target="update.versions" />
> <antcall target="merge_rc_to_develop" />
> <antcall target="release.maven.staging.repo" />
>
> One step previous was move in svn binaries from dev folder to release - I
> omit that cause I did it already manually. Launching following steps I
> reached release.npm - Which requires login and password to npm - I
> omitted that as well. Next was update.versions and it failed with following
> stack trace [1]
>
> In mentioned lines in the stacktrace I have:
>
> Line 1088:
> <antcall target="update.versions" />
>
> Line 1216:
> <exec executable="${git}" dir="${compiler}" failonerror="true" >
> <arg value="commit" />
> <arg value="-m" />
> <arg value="update version to ${new.release.version}" />
> </exec>
>
> [1] https://paste.apache.org/15biu
>
> Thanks,
> Piotr
>
>
>
> śr., 2 paź 2019 o 02:54 OmPrakash Muppirala <bi...@gmail.com>
> napisał(a):
>
>> On Tue, Oct 1, 2019 at 8:32 AM Alex Harui <ah...@adobe.com.invalid>
>> wrote:
>>
>> > The releasecandidate.xml script will tell you what to do on
>> > repository.apache.org to release the Maven stuff, and release the npm
>> > stuff as well. The whole point of these scripts is so you don't have to
>> > ask for help. If you do end up needing help, then the scripts need
>> > improving. We want to capture knowledge in these scripts and on the
>> wiki.
>> >
>> >
>> Alex, did you merge your fixes to the npm related stuff into the release
>> branch? If yes, I think we should be good to go.
>>
>> Thanks,
>> Om
>>
>>
>> > -Alex
>> >
>> > On 10/1/19, 12:30 AM, "Piotr Zarzycki" <pi...@gmail.com>
>> wrote:
>> >
>> > Hi Om,
>> >
>> > What I need to do in order to release stuff on npm. Can you do this
>> > for me
>> > once I push release to svn ?
>> >
>> > Thanks,
>> > Piotr
>> >
>> > wt., 1 paź 2019 o 09:25 Piotr Zarzycki <pi...@gmail.com>
>> > napisał(a):
>> >
>> > > Hi Harbs,
>> > >
>> > > I think we have enough votes. I still have to gather info how
>> > actually
>> > > release Maven artifacts. However I'm going to push binaries today
>> in
>> > svn.
>> > >
>> > > Thanks,
>> > > Piotr
>> > >
>> > > sob., 28 wrz 2019 o 20:02 Harbs <ha...@gmail.com>
>> napisał(a):
>> > >
>> > >> FYI, I will not be able to test the release until Wednesday.
>> > >>
>> > >> If the vote is still open, I plan on testing then.
>> > >>
>> > >> Thanks,
>> > >> Harbs
>> > >>
>> > >> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <
>> > piotrzarzycki21@gmail.com>
>> > >> wrote:
>> > >> >
>> > >> > Ok, new and hopefully the last one RC3. I didn't run
>> ApproveScript
>> > >> myself
>> > >> > yet, but will do that tomorrow or next week.
>> > >> >
>> > >> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>> > >> apacheroyaleci@gmail.com>
>> > >> > napisał(a):
>> > >> >
>> > >> >> This is the discussion thread.
>> > >> >>
>> > >> >> Thanks,
>> > >> >> Piotr
>> > >> >
>> > >> >
>> > >> >
>> > >> > --
>> > >> >
>> > >> > Piotr Zarzycki
>> > >> >
>> > >> > Patreon: *
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
>> > >> > <
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
>> > >*
>> > >>
>> > >>
>> > >
>> > > --
>> > >
>> > > Piotr Zarzycki
>> > >
>> > > Patreon: *
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
>> > > <
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
>> > >*
>> > >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
>> > <
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
>> > >*
>> >
>> >
>> >
>>
>
>
> --
>
> 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: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi,
I just tried releasecandidate script. It contains following steps.
<antcall target="release.tag" />
<!-- this is intended to merge the tag to master because it should
have the right versions in it -->
<antcall target="merge_rc_to_master" />
<antcall target="get_head_of_rc_branches" />
<antcall target="release.npm" />
<antcall target="update.versions" />
<antcall target="merge_rc_to_develop" />
<antcall target="release.maven.staging.repo" />
One step previous was move in svn binaries from dev folder to release - I
omit that cause I did it already manually. Launching following steps I
reached release.npm - Which requires login and password to npm - I
omitted that as well. Next was update.versions and it failed with following
stack trace [1]
In mentioned lines in the stacktrace I have:
Line 1088:
<antcall target="update.versions" />
Line 1216:
<exec executable="${git}" dir="${compiler}" failonerror="true" >
<arg value="commit" />
<arg value="-m" />
<arg value="update version to ${new.release.version}" />
</exec>
[1] https://paste.apache.org/15biu
Thanks,
Piotr
śr., 2 paź 2019 o 02:54 OmPrakash Muppirala <bi...@gmail.com>
napisał(a):
> On Tue, Oct 1, 2019 at 8:32 AM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
> > The releasecandidate.xml script will tell you what to do on
> > repository.apache.org to release the Maven stuff, and release the npm
> > stuff as well. The whole point of these scripts is so you don't have to
> > ask for help. If you do end up needing help, then the scripts need
> > improving. We want to capture knowledge in these scripts and on the
> wiki.
> >
> >
> Alex, did you merge your fixes to the npm related stuff into the release
> branch? If yes, I think we should be good to go.
>
> Thanks,
> Om
>
>
> > -Alex
> >
> > On 10/1/19, 12:30 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Hi Om,
> >
> > What I need to do in order to release stuff on npm. Can you do this
> > for me
> > once I push release to svn ?
> >
> > Thanks,
> > Piotr
> >
> > wt., 1 paź 2019 o 09:25 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> > > Hi Harbs,
> > >
> > > I think we have enough votes. I still have to gather info how
> > actually
> > > release Maven artifacts. However I'm going to push binaries today
> in
> > svn.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > sob., 28 wrz 2019 o 20:02 Harbs <ha...@gmail.com>
> napisał(a):
> > >
> > >> FYI, I will not be able to test the release until Wednesday.
> > >>
> > >> If the vote is still open, I plan on testing then.
> > >>
> > >> Thanks,
> > >> Harbs
> > >>
> > >> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <
> > piotrzarzycki21@gmail.com>
> > >> wrote:
> > >> >
> > >> > Ok, new and hopefully the last one RC3. I didn't run
> ApproveScript
> > >> myself
> > >> > yet, but will do that tomorrow or next week.
> > >> >
> > >> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
> > >> apacheroyaleci@gmail.com>
> > >> > napisał(a):
> > >> >
> > >> >> This is the discussion thread.
> > >> >>
> > >> >> Thanks,
> > >> >> Piotr
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> >
> > >> > Piotr Zarzycki
> > >> >
> > >> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> > >> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> > >*
> > >>
> > >>
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> > > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> > >*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> > >*
> >
> >
> >
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Oct 1, 2019 at 8:32 AM Alex Harui <ah...@adobe.com.invalid> wrote:
> The releasecandidate.xml script will tell you what to do on
> repository.apache.org to release the Maven stuff, and release the npm
> stuff as well. The whole point of these scripts is so you don't have to
> ask for help. If you do end up needing help, then the scripts need
> improving. We want to capture knowledge in these scripts and on the wiki.
>
>
Alex, did you merge your fixes to the npm related stuff into the release
branch? If yes, I think we should be good to go.
Thanks,
Om
> -Alex
>
> On 10/1/19, 12:30 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Hi Om,
>
> What I need to do in order to release stuff on npm. Can you do this
> for me
> once I push release to svn ?
>
> Thanks,
> Piotr
>
> wt., 1 paź 2019 o 09:25 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Hi Harbs,
> >
> > I think we have enough votes. I still have to gather info how
> actually
> > release Maven artifacts. However I'm going to push binaries today in
> svn.
> >
> > Thanks,
> > Piotr
> >
> > sob., 28 wrz 2019 o 20:02 Harbs <ha...@gmail.com> napisał(a):
> >
> >> FYI, I will not be able to test the release until Wednesday.
> >>
> >> If the vote is still open, I plan on testing then.
> >>
> >> Thanks,
> >> Harbs
> >>
> >> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> >> wrote:
> >> >
> >> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
> >> myself
> >> > yet, but will do that tomorrow or next week.
> >> >
> >> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
> >> apacheroyaleci@gmail.com>
> >> > napisał(a):
> >> >
> >> >> This is the discussion thread.
> >> >>
> >> >> Thanks,
> >> >> Piotr
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Piotr Zarzycki
> >> >
> >> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> >> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> >*
> >>
> >>
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> >*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> >*
>
>
>
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Alex Harui <ah...@adobe.com.INVALID>.
The releasecandidate.xml script will tell you what to do on repository.apache.org to release the Maven stuff, and release the npm stuff as well. The whole point of these scripts is so you don't have to ask for help. If you do end up needing help, then the scripts need improving. We want to capture knowledge in these scripts and on the wiki.
-Alex
On 10/1/19, 12:30 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Hi Om,
What I need to do in order to release stuff on npm. Can you do this for me
once I push release to svn ?
Thanks,
Piotr
wt., 1 paź 2019 o 09:25 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi Harbs,
>
> I think we have enough votes. I still have to gather info how actually
> release Maven artifacts. However I'm going to push binaries today in svn.
>
> Thanks,
> Piotr
>
> sob., 28 wrz 2019 o 20:02 Harbs <ha...@gmail.com> napisał(a):
>
>> FYI, I will not be able to test the release until Wednesday.
>>
>> If the vote is still open, I plan on testing then.
>>
>> Thanks,
>> Harbs
>>
>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <pi...@gmail.com>
>> wrote:
>> >
>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>> myself
>> > yet, but will do that tomorrow or next week.
>> >
>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>> apacheroyaleci@gmail.com>
>> > napisał(a):
>> >
>> >> This is the discussion thread.
>> >>
>> >> Thanks,
>> >> Piotr
>> >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
>> > <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0>*
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0>*
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516&sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3D&reserved=0>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Releasecandidate.xml can't do steps on repository.apache.org. It will remind you to go there and release the staged artifacts.
-Alex
On 10/1/19, 6:55 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
I see that releasecandidate.xml script can help me with last steps. Does it
doing Maven releases as well ?
That steps includes also push to svn - I just did it manually, so I will
probably comment out commit part and run script. - I think tomorrow.
wt., 1 paź 2019 o 09:29 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi Om,
>
> What I need to do in order to release stuff on npm. Can you do this for me
> once I push release to svn ?
>
> Thanks,
> Piotr
>
> wt., 1 paź 2019 o 09:25 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> Hi Harbs,
>>
>> I think we have enough votes. I still have to gather info how actually
>> release Maven artifacts. However I'm going to push binaries today in svn.
>>
>> Thanks,
>> Piotr
>>
>> sob., 28 wrz 2019 o 20:02 Harbs <ha...@gmail.com> napisał(a):
>>
>>> FYI, I will not be able to test the release until Wednesday.
>>>
>>> If the vote is still open, I plan on testing then.
>>>
>>> Thanks,
>>> Harbs
>>>
>>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <pi...@gmail.com>
>>> wrote:
>>> >
>>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>>> myself
>>> > yet, but will do that tomorrow or next week.
>>> >
>>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>>> apacheroyaleci@gmail.com>
>>> > napisał(a):
>>> >
>>> >> This is the discussion thread.
>>> >>
>>> >> Thanks,
>>> >> Piotr
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > Piotr Zarzycki
>>> >
>>> > Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152&sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3D&reserved=0
>>> > <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152&sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3D&reserved=0>*
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152&sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3D&reserved=0
>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152&sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3D&reserved=0>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152&sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3D&reserved=0
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152&sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3D&reserved=0>*
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152&sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152&sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3D&reserved=0>*
Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
I see that releasecandidate.xml script can help me with last steps. Does it
doing Maven releases as well ?
That steps includes also push to svn - I just did it manually, so I will
probably comment out commit part and run script. - I think tomorrow.
wt., 1 paź 2019 o 09:29 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi Om,
>
> What I need to do in order to release stuff on npm. Can you do this for me
> once I push release to svn ?
>
> Thanks,
> Piotr
>
> wt., 1 paź 2019 o 09:25 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> Hi Harbs,
>>
>> I think we have enough votes. I still have to gather info how actually
>> release Maven artifacts. However I'm going to push binaries today in svn.
>>
>> Thanks,
>> Piotr
>>
>> sob., 28 wrz 2019 o 20:02 Harbs <ha...@gmail.com> napisał(a):
>>
>>> FYI, I will not be able to test the release until Wednesday.
>>>
>>> If the vote is still open, I plan on testing then.
>>>
>>> Thanks,
>>> Harbs
>>>
>>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <pi...@gmail.com>
>>> wrote:
>>> >
>>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>>> myself
>>> > yet, but will do that tomorrow or next week.
>>> >
>>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>>> apacheroyaleci@gmail.com>
>>> > napisał(a):
>>> >
>>> >> This is the discussion thread.
>>> >>
>>> >> Thanks,
>>> >> Piotr
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > 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>*
>>
>
>
> --
>
> 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: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Om,
What I need to do in order to release stuff on npm. Can you do this for me
once I push release to svn ?
Thanks,
Piotr
wt., 1 paź 2019 o 09:25 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi Harbs,
>
> I think we have enough votes. I still have to gather info how actually
> release Maven artifacts. However I'm going to push binaries today in svn.
>
> Thanks,
> Piotr
>
> sob., 28 wrz 2019 o 20:02 Harbs <ha...@gmail.com> napisał(a):
>
>> FYI, I will not be able to test the release until Wednesday.
>>
>> If the vote is still open, I plan on testing then.
>>
>> Thanks,
>> Harbs
>>
>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <pi...@gmail.com>
>> wrote:
>> >
>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>> myself
>> > yet, but will do that tomorrow or next week.
>> >
>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>> apacheroyaleci@gmail.com>
>> > napisał(a):
>> >
>> >> This is the discussion thread.
>> >>
>> >> Thanks,
>> >> Piotr
>> >
>> >
>> >
>> > --
>> >
>> > 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>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*