subject:"\[DISCUSS\] Discuss Release Apache FlexJS 0.8.0 RC1"

I just dig into old BlazeDS release [1] and I see that Chris put it into some
folder. I think if I run Maven "apache-release" profile I think I may be
able to put them into some folder here [2].

We will see if someone help me with this keys for signing process.

[1]
http://apache-flex-development.247.n4.nabble.com/VOTE-BlazeDS-Release-of-Apache-BlazeDS-4-7-0-RC2-td45328.html#a45344
[2] https://repository.apache.org/content/repositories/

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62443.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

It look like I'm stuck with this one. :/

I did generate key and push it to the public serever [1], but if I correct
understand you I still need to push it on my private space id.apache.org.

Maybe it's enough to sign artifacts ?

[1]
http://p80.pool.sks-keyservers.net/pks/lookup?op=get=0x6B0A7EC905061FC8

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62442.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi Alex,

This instruction [1] is saying:

"To use key-based login, you need to generate the key on your local desktop
(do not use a publicly accessible server for this) and then add your public
key to LDAP using the self-service app at https://id.apache.org;

Is this the key which I've generated for signing process ? Is this the same
?

[1] https://www.apache.org/dev/new-committers-guide#ssh-setup

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62441.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-17 Thread Alex Harui

Hi Piotr,

SFTP is used to access home.apache.org.  Search for "home.apache.org" on
this page: https://www.apache.org/dev/committers.html

I'm not sure I did all of those steps.  The one remaining thing I think
you need to do is add your key to our KEYS file as described later in [2].

HTH,
-Alex

On 6/17/17, 5:28 AM, "piotrz"  wrote:

>Hi,
>
>I'm going through instruction of keys generation and last thing which I
>need
>to do is publish myfile.asc to home.apache.org. In order to have something
>like that [1]. I have instruction [2], but do not understand how can I
>connect and upload to public_home this as file - Any idea ?
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apache.
>org%2F~rdonkin%2FA6EE6908.asc=02%7C01%7C%7C36a7dd909bea4eaf30b808d4b5
>7e9b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636333002763014731
>ta=G6aXecFfV7s4iv6WqBYEwVPMDn6vCmo%2BkksnAYXT4rw%3D=0
>[2] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apach
>e.org%2Fdev%2Fopenpgp.html%23update=02%7C01%7C%7C36a7dd909bea4eaf30b8
>08d4b57e9b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6363330027630147
>31=j8yBvnoKoGaq3GkI1ypDtY2dxNf7mEIM7Zj2zYU74Pg%3D=0
>
>Thanks,
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>S-0-8-0-RC1-tp62274p62437.html=02%7C01%7C%7C36a7dd909bea4eaf30b808d4b
>57e9b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636333002763014731
>ata=ynL7w0tOcE6Pnv%2F9JhWyL1szC1Xw%2B%2F1GGACNUy4MFaU%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi,

I'm going through instruction of keys generation and last thing which I need
to do is publish myfile.asc to home.apache.org. In order to have something
like that [1]. I have instruction [2], but do not understand how can I
connect and upload to public_home this as file - Any idea ?

[1] http://home.apache.org/~rdonkin/A6EE6908.asc
[2] https://www.apache.org/dev/openpgp.html#update

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62437.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-16 Thread Alex Harui

If you look up past BlazeDS releases, which are Maven driven, I'm pretty
sure the artifacts are put in a staging repository for examination.
Somehow, testers will pull the artifacts from this place instead of the
final home on Maven Central.

At least, that's how I understood it, but I could certainly be wrong.

-Alex

On 6/16/17, 2:52 PM, "piotrz"  wrote:

>Alex,
>
>What do you mean by "staging" repository ? Let's wait for opinion from
>other
>PMC. I will try to go over signing instruction from Josh.
>
>Let's make this release finally happen!
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>S-0-8-0-RC1-tp62274p62434.html=02%7C01%7C%7Cd16e648ca71941af8b7708d4b
>5044518%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636332477340747670
>ata=PfAoVjSWQ0XWtXvHvg6ePcgUG6Hb7F6yqKRSQ7xHCFg%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Alex,

What do you mean by "staging" repository ? Let's wait for opinion from other
PMC. I will try to go over signing instruction from Josh.

Let's make this release finally happen! 

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62434.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-16 Thread Alex Harui

And Nexus isn't an Apache thing AFAICT.  You might have to read up on how
it integrates with Maven.

Thanks for offering to help out on the Maven side.  I'm concerned that you
can't just take manually/locally built artifacts and follow the steps to
publish those artifacts.  I think those steps might be expecting a staging
repository with artifacts produced from a branch it created in earlier
steps.

Regardless, we need to get more consensus around whether we will try
process #3.

-Alex

On 6/16/17, 12:08 PM, "Josh Tynjala"  wrote:

>You're going to want to get your signing key ready:
>
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apach
>e.org%2Fdev%2Frelease-signing.html=02%7C01%7C%7C473b0bd826324b2bdb730
>8d4b4eb24ab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63633236940145485
>9=NEAgBKcwNEQ3%2BAkmVD8Jg3cWL3So1TAYd2w45LSkvN4%3D=0
>
>- Josh
>
>On Fri, Jun 16, 2017 at 11:40 AM, piotrz 
>wrote:
>
>> Hi Alex,
>>
>> I think option 3 is almost what I think we should do.
>>
>> - Ant - examining should be same as it was by Approval script - No
>>change
>> here.
>>
>> - Maven:
>> 1) Build Maven from sources downloaded by Approval script (I think it
>> should
>> be possible to build FlexJS and Falcon) or checkout release branch and
>> build
>> it. Typedefs should also be examined by that.
>> 2) Perform Maven steps: - I think I can handle that. For this release we
>> will be able to do only part of those steps. Let me explain why:
>>
>> Step 1-2) Should be done as a first thing - cause as part of that step
>>we
>> are creating new branch for the release - We already have it.
>> ("release0.8.0) - As yo probably notice I did this steps and commit new
>> branch, but that was a mistake and Josh helped me understand it. - I did
>> revert. Almost manually changed develop to 0.9.0-SNAPSHOT
>>
>> Step 4) That's the mysterious for me a bit, cause as I understand after
>> step
>> 1-3 we have release branch where our version is 0.8.0-SNAPSHOT (That is
>>our
>> branch) and develop branch is in version 0.9.0-SNAPSHOT. - I did perform
>> this step cause we were in exactly this situation.
>>
>> Maven asked me about "next development version" when I was performing
>>this
>> step - Which was unnecessary, cause I did setup my development version
>>on
>> "develop", so I was trying to set "0.8.0", but it didn't work. I
>>decided to
>> do this manually on our "release0.8.0" branch.
>>
>> Steps 5 - 8) This is what I should do next if you Alex and of course
>>others
>> also agreed that we can start VOTE. I'm only concerns about signing
>> artifacts - not sure what is this mean, but I hope Maven will do this
>>for
>> me.
>>
>> As for the login to nexus - That is also what I need to figure out, but
>>I'm
>> assuming that as PMC I have access to Apache nexus.''
>>
>> Waiting for thoughts and green light.
>>
>> Thanks,
>> Piotr
>>
>>
>>
>>
>> -
>> Apache Flex PMC
>> piotrzarzyck...@gmail.com
>> --
>> View this message in context: http://apache-flex-
>> development.247.n4.nabble.com/DISCUSS-Discuss-Release-
>> Apache-FlexJS-0-8-0-RC1-tp62274p62431.html
>> Sent from the Apache Flex Development mailing list archive at
>>Nabble.com.
>>

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-16 Thread Josh Tynjala

You're going to want to get your signing key ready:

https://www.apache.org/dev/release-signing.html

- Josh

On Fri, Jun 16, 2017 at 11:40 AM, piotrz  wrote:

> Hi Alex,
>
> I think option 3 is almost what I think we should do.
>
> - Ant - examining should be same as it was by Approval script - No change
> here.
>
> - Maven:
> 1) Build Maven from sources downloaded by Approval script (I think it
> should
> be possible to build FlexJS and Falcon) or checkout release branch and
> build
> it. Typedefs should also be examined by that.
> 2) Perform Maven steps: - I think I can handle that. For this release we
> will be able to do only part of those steps. Let me explain why:
>
> Step 1-2) Should be done as a first thing - cause as part of that step we
> are creating new branch for the release - We already have it.
> ("release0.8.0) - As yo probably notice I did this steps and commit new
> branch, but that was a mistake and Josh helped me understand it. - I did
> revert. Almost manually changed develop to 0.9.0-SNAPSHOT
>
> Step 4) That's the mysterious for me a bit, cause as I understand after
> step
> 1-3 we have release branch where our version is 0.8.0-SNAPSHOT (That is our
> branch) and develop branch is in version 0.9.0-SNAPSHOT. - I did perform
> this step cause we were in exactly this situation.
>
> Maven asked me about "next development version" when I was performing this
> step - Which was unnecessary, cause I did setup my development version on
> "develop", so I was trying to set "0.8.0", but it didn't work. I decided to
> do this manually on our "release0.8.0" branch.
>
> Steps 5 - 8) This is what I should do next if you Alex and of course others
> also agreed that we can start VOTE. I'm only concerns about signing
> artifacts - not sure what is this mean, but I hope Maven will do this for
> me.
>
> As for the login to nexus - That is also what I need to figure out, but I'm
> assuming that as PMC I have access to Apache nexus.''
>
> Waiting for thoughts and green light.
>
> Thanks,
> Piotr
>
>
>
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/DISCUSS-Discuss-Release-
> Apache-FlexJS-0-8-0-RC1-tp62274p62431.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi Alex,

I think option 3 is almost what I think we should do.

- Ant - examining should be same as it was by Approval script - No change
here.

- Maven:
1) Build Maven from sources downloaded by Approval script (I think it should
be possible to build FlexJS and Falcon) or checkout release branch and build
it. Typedefs should also be examined by that.
2) Perform Maven steps: - I think I can handle that. For this release we
will be able to do only part of those steps. Let me explain why:

Step 1-2) Should be done as a first thing - cause as part of that step we
are creating new branch for the release - We already have it.
("release0.8.0) - As yo probably notice I did this steps and commit new
branch, but that was a mistake and Josh helped me understand it. - I did
revert. Almost manually changed develop to 0.9.0-SNAPSHOT

Step 4) That's the mysterious for me a bit, cause as I understand after step
1-3 we have release branch where our version is 0.8.0-SNAPSHOT (That is our
branch) and develop branch is in version 0.9.0-SNAPSHOT. - I did perform
this step cause we were in exactly this situation.

Maven asked me about "next development version" when I was performing this
step - Which was unnecessary, cause I did setup my development version on
"develop", so I was trying to set "0.8.0", but it didn't work. I decided to
do this manually on our "release0.8.0" branch.

Steps 5 - 8) This is what I should do next if you Alex and of course others
also agreed that we can start VOTE. I'm only concerns about signing
artifacts - not sure what is this mean, but I hope Maven will do this for
me.

As for the login to nexus - That is also what I need to figure out, but I'm
assuming that as PMC I have access to Apache nexus.''

Waiting for thoughts and green light.

Thanks,
Piotr

-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62431.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-16 Thread Alex Harui

I still don't think we have clarity on how to complete this release.

AIUI, nobody has run any of the Maven commands in [1].  Instead, versions
in POM files have been manually updated?

If I run my Ant scripts to produce another set of artifacts, who is going
to run what steps in order to produce maven artifacts?  It sounds like
there are some choices and I want to make sure we have agreement before I
go and spend any more time on this release.

1) Unpack the Ant source artifact, run Maven on it.  Manually copy the
Maven artifacts to Maven Central.  That's a lot of artifacts so sounds
really painful.  Voters are voting on the Ant-produced source packages.
2) Run the steps in [1].  Adjust my Ant scripts to work from the 3 source
artifacts produced by the steps in [1].  Vote on the 3 Maven source
packages.
3) Run the steps in [1].  Also run the Ant scripts to produce Ant-based
artifacts.  Manually verify that the source package produced by Maven is
"essentially the same" as the Ant-produced source packages.  Voters are
voting on the Ant-produced source packages and also have to verify the
Maven source is "essentially the same".
4) Same as 3 but voters have to examine and vote on both the 3 Maven
source packages and the 2 Ant-produced source packages.

There might be other ideas as well.  Essentially, I think it comes down to
how we want to interpret the rules about binary packages being produced
from source packages.  IMO, we could have just renamed some artifacts and
manually modified POMs and called it done.

Also, it sounds like for many of these choices I have to get a Nexus
account and run the steps in [1] or is some other volunteer going to do
that?

Thoughts?
-Alex

[1] 
https://cwiki.apache.org/confluence/display/FLEX/Releasing+FlexJS+with+Mave
n

On 6/15/17, 11:25 PM, "piotrz"  wrote:

>Ok build finished successfully.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>S-0-8-0-RC1-tp62274p62426.html=02%7C01%7C%7C9e81c80255204cac220f08d4b
>482bf22%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636331921022898890
>ata=h13qWlWNhCHcA3ZMsLMC8YI4nBwWwV4O5lab79CBqaY%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Ok build finished successfully.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62426.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi,

I just tested and pushed the changes to release branch, additionally fixed
one small bug. Once build [1] pass I think we are ready to go.

Fix for patching problem was also committed by Justin.

[1]
https://builds.apache.org/view/E-G/view/Flex/job/FlexJS%20Pipeline/job/release0.8.0/37/

Piotr





-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62425.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-15 Thread Justin Mclean

Hi,

> I did the changes, but need to do more test whether I didn't forget about
> something. I will push everything tomorrow - if there will not be any veto.

Just a friendly reminder that a -1 on a release vote is not a veto. You need 3 
+1’s and more +1’s than -1’s for a release vote to pass.

However a RM may still cancel a release if a serious issue is found and/or 
thinks another RC is needed.

Thanks,
Justin

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-15 Thread piotrz

I did the changes, but need to do more test whether I didn't forget about
something. I will push everything tomorrow - if there will not be any veto.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62419.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-15 Thread piotrz

Ahh! Ok so I will change the poms later today. 

Once Vote pass we will be able to deploy it to the apache maven central by
Chris instruction.

Got it!

Thanks Josh once again!
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62412.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-15 Thread Josh Tynjala

As I understand it, we need the pom.xml versions to be updated to 0.8.0
before we cut the RC. That was the biggest issue. The RC can't have
0.8.0-SNAPSHOT in it.

- Josh

On Thu, Jun 15, 2017 at 3:02 AM, piotrz  wrote:

> Hi,
>
> Here is my understanding what need to be done in this release.
> 1) Fix issue with patching typedefs
> 2) Cut next RC, if vote pass I will try to execute Chris's steps starting
> from p. 4 [1] (Josh help me to understand it.) in order to deploy released
> artifacts and change branch from 0.8.0-SNAPSHOT to 0.8.0.
>
> Does anyone see something more?
>
> Apart of that develop branch Maven build is failing after my switch to
> 0.9.0-SNAPSHOT. I'm pretty sure that we had similar issue and I think Josh
> last time fix it, but I'm not sure. Mys local build is working fine. I'll
> try to look into this later today.
>
> [1]
> https://cwiki.apache.org/confluence/display/FLEX/
> Releasing+FlexJS+with+Maven
>
> Piotr
>
>
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/DISCUSS-Discuss-Release-
> Apache-FlexJS-0-8-0-RC1-tp62274p62408.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-15 Thread piotrz

Hi,

Here is my understanding what need to be done in this release. 
1) Fix issue with patching typedefs
2) Cut next RC, if vote pass I will try to execute Chris's steps starting
from p. 4 [1] (Josh help me to understand it.) in order to deploy released
artifacts and change branch from 0.8.0-SNAPSHOT to 0.8.0.

Does anyone see something more? 

Apart of that develop branch Maven build is failing after my switch to
0.9.0-SNAPSHOT. I'm pretty sure that we had similar issue and I think Josh
last time fix it, but I'm not sure. Mys local build is working fine. I'll
try to look into this later today.

[1]
https://cwiki.apache.org/confluence/display/FLEX/Releasing+FlexJS+with+Maven

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62408.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-14 Thread piotrz

I forgot to post link, from pipeline [1]

[1]
https://builds.apache.org/view/E-G/view/Flex/job/FlexJS%20Pipeline/job/develop/75/console

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62399.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-14 Thread piotrz

I think I did update develop branch to 0.9.-SNAPSHOT. Build of compiler and
typedefs went fine, but FlexJS is failing and I'm not sure why.

It's searching this some swc [1] but with version + date:

Could not find artifact
org.apache.flex.flexjs.typedefs:flexjs-typedefs-parent:pom:0.9.0-20170614.163928-7

Any idea ?

[1] https://paste.apache.org/0OI4

Thanks,
Piotr




-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62398.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-13 Thread Alex Harui

Hi Christofer,

Does the RM execute these steps locally or on builds.a.o?
Do we need logins to Nexus?
Does "mvn release:perform" checkout from a tag, or head or something else?
 Could it checkout from a tag?

Thanks,
-Alex

On 6/13/17, 1:34 AM, "Christofer Dutz"  wrote:

>I just wrote down the process:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apa
>che.org%2Fconfluence%2Fdisplay%2FFLEX%2FReleasing%2BFlexJS%2Bwith%2BMaven&
>data=02%7C01%7C%7C14b48ccc0f22498c429508d4b2370041%7Cfa7b1b5a7b34438794aed
>2c178decee1%7C0%7C0%7C636329396675696127=r1Dt1o5D8Ycdsb5B%2FR%2BEZt5
>I2YiW0t29ITw9yOJSouE%3D=0
>
>Chris
>
>Am 13.06.17, 10:08 schrieb "piotrz" :
>
>Chris,
>
>If you are not going to do this, I can try but probably I will have a
>lot of
>questions and it's not going to happen soon. I will have time on
>maybe today
>(but cannot promise) and on wednesday.
>
>Just let me know. Even if you will do this I will pay attention to
>each of
>your commits in order to handle this one next time.
>
>Thanks,
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>S-0-8-0-RC1-tp62274p62373.html=02%7C01%7C%7C14b48ccc0f22498c429508d4b
>2370041%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636329396675696127
>ata=fXlDINoZYYIepDI6c%2BUID5eZRSr8tI3zjKrA13BkN5g%3D=0
>Sent from the Apache Flex Development mailing list archive at
>Nabble.com.
>
>

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-13 Thread piotrz

Hi Olaf,

I think we need to go through the steps which Chris provided and then we can
cut another RC.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62376.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-13 Thread Olaf Krueger

Hi guys,

>It seems to me there is some interest in the extended community to see a
release out

It's still hard for me to understand the technical details but it seems to
me that the discussion Maven over Ant has reached a new climax which is not
very helpful at least.

Maybe I got something wrong because of the language barrier but I miss some
appreciation to Alex being the RM, especially because it sounds like that he
has very little time which is maybe one reason for him to stick with Ant.

However, I'm not sure but it feels like there's no consensus about how to
proceed to get a release?
If that's the case could somebody summarize what's needed?

Thanks,
Olaf












--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62375.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

I just wrote down the process:
https://cwiki.apache.org/confluence/display/FLEX/Releasing+FlexJS+with+Maven

Chris

Am 13.06.17, 10:08 schrieb "piotrz" :

Chris,

If you are not going to do this, I can try but probably I will have a lot of
questions and it's not going to happen soon. I will have time on maybe today
(but cannot promise) and on wednesday.

Just let me know. Even if you will do this I will pay attention to each of
your commits in order to handle this one next time.

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62373.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-13 Thread piotrz

Chris,

If you are not going to do this, I can try but probably I will have a lot of
questions and it's not going to happen soon. I will have time on maybe today
(but cannot promise) and on wednesday.

Just let me know. Even if you will do this I will pay attention to each of
your commits in order to handle this one next time.

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62373.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

If we want to do a release of Maven artifacts, yes.

It’s quite easy with Maven, it’s only difficult doing Maven releases with Ant.


Chris

Am 13.06.17, 09:19 schrieb "piotrz" :

Hi Chris, 

I'm not sure from that point whether we can cut next RC or not. It seems
that we have to still make your steps which you described earlier? Am I
right? 

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62370.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-13 Thread piotrz

Hi Chris, 

I'm not sure from that point whether we can cut next RC or not. It seems
that we have to still make your steps which you described earlier? Am I
right? 

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62370.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-13 Thread Harbs

All Flex project repos are prefixed with flex-

> On Jun 13, 2017, at 9:59 AM, Christofer Dutz  
> wrote:
> 
> By the way … why is this directory called “flex-typedefs” and not 
> “flexjs-typedefs”?
> 
> Chris
> 
> Am 13.06.17, 08:55 schrieb "Christofer Dutz" :
> 
>Hi all,
> 
>Please don’t let this become another license discussion … I thought that 
> had been settled. I intentionally added that this was a technical issue in my 
> report. 
>If the flexjs-typedefs directory is going to be included in the compiler 
> package, the compiler packages pom needs an exclusion for the flexjs-typedefs 
> directory to avoid any problems like this. The content of the flesjs-typedefs 
> directory will be checked by the flexjs-typedefs build so in the end all is 
> checked. I’m just going to do this little tweak myself so if a new release 
> candidate is created, we have this “fix” in place.
> 
>Chris 
> 
>Am 13.06.17, 00:49 schrieb "Dave Fisher" :
> 
>Hi -
> 
>> On Jun 12, 2017, at 12:41 PM, Alex Harui  wrote:
>> 
>> I'm confused.  Can I get a summary?
>> 
>> Are there some files that are being caught by RAT?  If so, what are they?
>> 
>> Are we sure the process should be that the RM should switch away from
>> SNAPSHOT before the vote?  If a major problem is found in that RC,
>> wouldn't we have deployed bad artifacts under the final version number and
>> have to pull them back?  Or abandon that release version and use the next
>> version number?
> 
>The Tomcat project will user version numbers. If a version fails then 
> they advance to the next. They still produce changelings for the version that 
> is not released. You can see the gory details for version 7 here: 
> http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
> 
>Regards,
>Dave
> 
>> 
>> IMO, the main thing folks want from Maven are the JARs which aren't an
>> official ASF release anyway.  Seems like we should vote on a source
>> package, then set any version numbers and have Maven build the final jars
>> from there.  The differences in the source should only be in POMs and
>> other configs right?
>> 
>> What am I missing?
>> -Alex
>> 
>> On 6/12/17, 3:53 AM, "Christofer Dutz"  wrote:
>> 
>>> It should be between the Last call and opening the vote. It is equal to
>>> “cutting the release candidate”.
>>> 
>>> So, the LAST CALL thread is finished and the RM writes that he’s going to
>>> cut a release … AFTER THAT he does these steps and THEN he opens the vote
>>> thread. I never said anything else than that.
>>> 
>>> Chris
>>> 
>>> 
>>> Am 12.06.17, 12:30 schrieb "piotrz" :
>>> 
>>>  Chris,
>>> 
>>>  I'm a bit confused. You have said that I shouldn't do this as part of
>>>  VOTING, LAST CALL:
>>> 
>>>  "No,
>>> 
>>>  The removing the SNAPSHOT, tagging and setting the new version should
>>> be,
>>>  more or less, one step.
>>>  "
>>> 
>>>  Now you are saying just opposite. So again when I should do this
>>> (Last Call,
>>>  Voting) step ?
>>> 
>>>  "1) In order to have a proper Maven release, the versions of the
>>> maven build
>>>  should be changed to “0.8.0” (omit the SNAPSHOT). "
>>> 
>>>  Piotr
>>> 
>>> 
>>> 
>>>  -
>>>  Apache Flex PMC
>>>  piotrzarzyck...@gmail.com
>>>  --
>>>  View this message in context:
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>>> x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>>> S-0-8-0-RC1-tp62274p62341.html=02%7C01%7C%7C764b156340ed4161762808d4b
>>> 1813b7a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636328616008847001
>>> ata=pnXSK31V8HvCRI9NlEVlGD0SgCczOCQYlw0PyoVZnfQ%3D=0
>>>  Sent from the Apache Flex Development mailing list archive at
>>> Nabble.com.
>>> 
>>> 
>> 
> 
> 
> 
> 
>

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

By the way … why is this directory called “flex-typedefs” and not 
“flexjs-typedefs”?

Chris

Am 13.06.17, 08:55 schrieb "Christofer Dutz" :

Hi all,

Please don’t let this become another license discussion … I thought that 
had been settled. I intentionally added that this was a technical issue in my 
report. 
If the flexjs-typedefs directory is going to be included in the compiler 
package, the compiler packages pom needs an exclusion for the flexjs-typedefs 
directory to avoid any problems like this. The content of the flesjs-typedefs 
directory will be checked by the flexjs-typedefs build so in the end all is 
checked. I’m just going to do this little tweak myself so if a new release 
candidate is created, we have this “fix” in place.

Chris 

Am 13.06.17, 00:49 schrieb "Dave Fisher" :

Hi -

> On Jun 12, 2017, at 12:41 PM, Alex Harui  
wrote:
> 
> I'm confused.  Can I get a summary?
> 
> Are there some files that are being caught by RAT?  If so, what are 
they?
> 
> Are we sure the process should be that the RM should switch away from
> SNAPSHOT before the vote?  If a major problem is found in that RC,
> wouldn't we have deployed bad artifacts under the final version 
number and
> have to pull them back?  Or abandon that release version and use the 
next
> version number?

The Tomcat project will user version numbers. If a version fails then 
they advance to the next. They still produce changelings for the version that 
is not released. You can see the gory details for version 7 here: 
http://tomcat.apache.org/tomcat-7.0-doc/changelog.html

Regards,
Dave

> 
> IMO, the main thing folks want from Maven are the JARs which aren't an
> official ASF release anyway.  Seems like we should vote on a source
> package, then set any version numbers and have Maven build the final 
jars
> from there.  The differences in the source should only be in POMs and
> other configs right?
> 
> What am I missing?
> -Alex
> 
> On 6/12/17, 3:53 AM, "Christofer Dutz"  
wrote:
> 
>> It should be between the Last call and opening the vote. It is equal 
to
>> “cutting the release candidate”.
>> 
>> So, the LAST CALL thread is finished and the RM writes that he’s 
going to
>> cut a release … AFTER THAT he does these steps and THEN he opens the 
vote
>> thread. I never said anything else than that.
>> 
>> Chris
>> 
>> 
>> Am 12.06.17, 12:30 schrieb "piotrz" :
>> 
>>   Chris,
>> 
>>   I'm a bit confused. You have said that I shouldn't do this as part 
of
>>   VOTING, LAST CALL:
>> 
>>   "No,
>> 
>>   The removing the SNAPSHOT, tagging and setting the new version 
should
>> be,
>>   more or less, one step.
>>   "
>> 
>>   Now you are saying just opposite. So again when I should do this
>> (Last Call,
>>   Voting) step ?
>> 
>>   "1) In order to have a proper Maven release, the versions of the
>> maven build
>>   should be changed to “0.8.0” (omit the SNAPSHOT). "
>> 
>>   Piotr
>> 
>> 
>> 
>>   -
>>   Apache Flex PMC
>>   piotrzarzyck...@gmail.com
>>   --
>>   View this message in context:
>> 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>> 
x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>> 
S-0-8-0-RC1-tp62274p62341.html=02%7C01%7C%7C764b156340ed4161762808d4b
>> 
1813b7a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636328616008847001
>> ata=pnXSK31V8HvCRI9NlEVlGD0SgCczOCQYlw0PyoVZnfQ%3D=0
>>   Sent from the Apache Flex Development mailing list archive at
>> Nabble.com.
>> 
>> 
>

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi all,

Please don’t let this become another license discussion … I thought that had 
been settled. I intentionally added that this was a technical issue in my 
report. 
If the flexjs-typedefs directory is going to be included in the compiler 
package, the compiler packages pom needs an exclusion for the flexjs-typedefs 
directory to avoid any problems like this. The content of the flesjs-typedefs 
directory will be checked by the flexjs-typedefs build so in the end all is 
checked. I’m just going to do this little tweak myself so if a new release 
candidate is created, we have this “fix” in place.

Chris 

Am 13.06.17, 00:49 schrieb "Dave Fisher" :

Hi -

> On Jun 12, 2017, at 12:41 PM, Alex Harui  wrote:
> 
> I'm confused.  Can I get a summary?
> 
> Are there some files that are being caught by RAT?  If so, what are they?
> 
> Are we sure the process should be that the RM should switch away from
> SNAPSHOT before the vote?  If a major problem is found in that RC,
> wouldn't we have deployed bad artifacts under the final version number and
> have to pull them back?  Or abandon that release version and use the next
> version number?

The Tomcat project will user version numbers. If a version fails then they 
advance to the next. They still produce changelings for the version that is not 
released. You can see the gory details for version 7 here: 
http://tomcat.apache.org/tomcat-7.0-doc/changelog.html

Regards,
Dave

> 
> IMO, the main thing folks want from Maven are the JARs which aren't an
> official ASF release anyway.  Seems like we should vote on a source
> package, then set any version numbers and have Maven build the final jars
> from there.  The differences in the source should only be in POMs and
> other configs right?
> 
> What am I missing?
> -Alex
> 
> On 6/12/17, 3:53 AM, "Christofer Dutz"  wrote:
> 
>> It should be between the Last call and opening the vote. It is equal to
>> “cutting the release candidate”.
>> 
>> So, the LAST CALL thread is finished and the RM writes that he’s going to
>> cut a release … AFTER THAT he does these steps and THEN he opens the vote
>> thread. I never said anything else than that.
>> 
>> Chris
>> 
>> 
>> Am 12.06.17, 12:30 schrieb "piotrz" :
>> 
>>   Chris,
>> 
>>   I'm a bit confused. You have said that I shouldn't do this as part of
>>   VOTING, LAST CALL:
>> 
>>   "No,
>> 
>>   The removing the SNAPSHOT, tagging and setting the new version should
>> be,
>>   more or less, one step.
>>   "
>> 
>>   Now you are saying just opposite. So again when I should do this
>> (Last Call,
>>   Voting) step ?
>> 
>>   "1) In order to have a proper Maven release, the versions of the
>> maven build
>>   should be changed to “0.8.0” (omit the SNAPSHOT). "
>> 
>>   Piotr
>> 
>> 
>> 
>>   -
>>   Apache Flex PMC
>>   piotrzarzyck...@gmail.com
>>   --
>>   View this message in context:
>> 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>> 
x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>> 
S-0-8-0-RC1-tp62274p62341.html=02%7C01%7C%7C764b156340ed4161762808d4b
>> 
1813b7a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636328616008847001
>> ata=pnXSK31V8HvCRI9NlEVlGD0SgCczOCQYlw0PyoVZnfQ%3D=0
>>   Sent from the Apache Flex Development mailing list archive at
>> Nabble.com.
>> 
>> 
>

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-12 Thread Dave Fisher

Hi -

> On Jun 12, 2017, at 12:41 PM, Alex Harui  wrote:
> 
> I'm confused.  Can I get a summary?
> 
> Are there some files that are being caught by RAT?  If so, what are they?
> 
> Are we sure the process should be that the RM should switch away from
> SNAPSHOT before the vote?  If a major problem is found in that RC,
> wouldn't we have deployed bad artifacts under the final version number and
> have to pull them back?  Or abandon that release version and use the next
> version number?

The Tomcat project will user version numbers. If a version fails then they 
advance to the next. They still produce changelings for the version that is not 
released. You can see the gory details for version 7 here: 
http://tomcat.apache.org/tomcat-7.0-doc/changelog.html

Regards,
Dave

> 
> IMO, the main thing folks want from Maven are the JARs which aren't an
> official ASF release anyway.  Seems like we should vote on a source
> package, then set any version numbers and have Maven build the final jars
> from there.  The differences in the source should only be in POMs and
> other configs right?
> 
> What am I missing?
> -Alex
> 
> On 6/12/17, 3:53 AM, "Christofer Dutz"  wrote:
> 
>> It should be between the Last call and opening the vote. It is equal to
>> “cutting the release candidate”.
>> 
>> So, the LAST CALL thread is finished and the RM writes that he’s going to
>> cut a release … AFTER THAT he does these steps and THEN he opens the vote
>> thread. I never said anything else than that.
>> 
>> Chris
>> 
>> 
>> Am 12.06.17, 12:30 schrieb "piotrz" :
>> 
>>   Chris,
>> 
>>   I'm a bit confused. You have said that I shouldn't do this as part of
>>   VOTING, LAST CALL:
>> 
>>   "No,
>> 
>>   The removing the SNAPSHOT, tagging and setting the new version should
>> be,
>>   more or less, one step.
>>   "
>> 
>>   Now you are saying just opposite. So again when I should do this
>> (Last Call,
>>   Voting) step ?
>> 
>>   "1) In order to have a proper Maven release, the versions of the
>> maven build
>>   should be changed to “0.8.0” (omit the SNAPSHOT). "
>> 
>>   Piotr
>> 
>> 
>> 
>>   -
>>   Apache Flex PMC
>>   piotrzarzyck...@gmail.com
>>   --
>>   View this message in context:
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>> x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>> S-0-8-0-RC1-tp62274p62341.html=02%7C01%7C%7C764b156340ed4161762808d4b
>> 1813b7a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636328616008847001
>> ata=pnXSK31V8HvCRI9NlEVlGD0SgCczOCQYlw0PyoVZnfQ%3D=0
>>   Sent from the Apache Flex Development mailing list archive at
>> Nabble.com.
>> 
>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi,

> Justin - you did state that you consider this acceptable for this release and 
> that we can clean it up for the next.

Yes I stated that in my vote and that would be acceptable.

Thanks,
Justin

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-12 Thread Dave Fisher

Hi -

> On Jun 12, 2017, at 3:34 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Are there some files that are being caught by RAT?  If so, what are they?
> 
> I mentioned them in my vote email. [1] 3 patch files don’t have ASF headers.

We may need to revisit the project’s preferred way of doing this. From what I 
recall of the legal-discuss along with hallway discussions at Apachecon there 
is more than one way.

Justin - you did state that you consider this acceptable for this release and 
that we can clean it up for the next. I suggest that we take care of this 
immediately after the release.

> 
>> IMO, the main thing folks want from Maven are the JARs which aren't an
>> official ASF release anyway.  Seems like we should vote on a source
>> package, then set any version numbers and have Maven build the final jars
>> from there.  The differences in the source should only be in POMs and
>> other configs right?
> 
> Which is IMO not permitted by ASF release policy as the binary connivance 
> releases need to be made from the tagged source release. [2] (and elsewhere)

AFAIK this is correct. Renaming the artifact is ok but the convenience binaries 
should always be made from the tagged release. Note that different versions of 
JAVA on different OS may produce slightly differing Jars from the same source 
code. We will need to trust the release manager who signs with their personal 
key that this is correctly done.

Regards,
Dave

> 
> Thanks,
> Justin
> 
> 1. 
> https://lists.apache.org/thread.html/47ad4369d92791280f8cdfb0d1e208cafb7d58860f0f743b54a76599@%3Cdev.flex.apache.org%3E
>  
> 
> 2. http://www.apache.org/legal/release-policy.html#compiled-packages 
> 
> 

signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi,

> Are there some files that are being caught by RAT?  If so, what are they?

I mentioned them in my vote email. [1] 3 patch files don’t have ASF headers.

> IMO, the main thing folks want from Maven are the JARs which aren't an
> official ASF release anyway.  Seems like we should vote on a source
> package, then set any version numbers and have Maven build the final jars
> from there.  The differences in the source should only be in POMs and
> other configs right?

Which is IMO not permitted by ASF release policy as the binary connivance 
releases need to be made from the tagged source release. [2] (and elsewhere)

Thanks,
Justin

1. 
https://lists.apache.org/thread.html/47ad4369d92791280f8cdfb0d1e208cafb7d58860f0f743b54a76599@%3Cdev.flex.apache.org%3E
 

2. http://www.apache.org/legal/release-policy.html#compiled-packages

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Replying to Yishay and Alex:

Last time I took the release source bundle, changed the versions and ran a 
release build. Even if this worked, it was just a hack and technically we 
published release artifacts that are different than the version we voted on. 
So, someone who downloads the release archive will not be able to reproduce the 
build. I am not going to do this this time as I think this is not the Apache 
way.

The flex-typedefs is not a maven module from the point of view of the compiler 
build. So rat checks the content as part of the root modules check. It will 
check every file in that directory for license headers (even stuff in an 
eventually existing target directory). The exclusion instruction is in the 
pom.xml inside the flex-typedefs directory and isn’t acive when building the 
compiler (they are separate builds). One was to avoid this would be to exclude 
the flexjs-typedefs directory in the compilers rat-check (even if the orginal 
repo doesn’t contain that directory). The better solution would be to do 3 
releases and not integrate the typedefs in the compiler artifact (Which I think 
is the correct way to do it)

I think it is an issue … as a Maven artifact is the binaries plus the poms. 
Changes in the poms can greatly affect the functionality of the binaries. 

Chris

Am 12.06.17, 21:41 schrieb "Alex Harui" :

I'm confused.  Can I get a summary?

Are there some files that are being caught by RAT?  If so, what are they?

Are we sure the process should be that the RM should switch away from
SNAPSHOT before the vote?  If a major problem is found in that RC,
wouldn't we have deployed bad artifacts under the final version number and
have to pull them back?  Or abandon that release version and use the next
version number?

IMO, the main thing folks want from Maven are the JARs which aren't an
official ASF release anyway.  Seems like we should vote on a source
package, then set any version numbers and have Maven build the final jars
from there.  The differences in the source should only be in POMs and
other configs right?

What am I missing?
-Alex

On 6/12/17, 3:53 AM, "Christofer Dutz"  wrote:

>It should be between the Last call and opening the vote. It is equal to
>“cutting the release candidate”.
>
>So, the LAST CALL thread is finished and the RM writes that he’s going to
>cut a release … AFTER THAT he does these steps and THEN he opens the vote
>thread. I never said anything else than that.
>
>Chris
>
>
>Am 12.06.17, 12:30 schrieb "piotrz" :
>
>Chris,
>
>I'm a bit confused. You have said that I shouldn't do this as part of
>VOTING, LAST CALL:
>
>"No, 
>
>The removing the SNAPSHOT, tagging and setting the new version should
>be,
>more or less, one step.
>"
>
>Now you are saying just opposite. So again when I should do this
>(Last Call,
>Voting) step ?
>
>"1) In order to have a proper Maven release, the versions of the
>maven build
>should be changed to “0.8.0” (omit the SNAPSHOT). "
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>S-0-8-0-RC1-tp62274p62341.html=02%7C01%7C%7C764b156340ed4161762808d4b
>1813b7a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636328616008847001
>ata=pnXSK31V8HvCRI9NlEVlGD0SgCczOCQYlw0PyoVZnfQ%3D=0
>Sent from the Apache Flex Development mailing list archive at
>Nabble.com.
>
>

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-12 Thread Alex Harui

I'm confused.  Can I get a summary?

Are there some files that are being caught by RAT?  If so, what are they?

Are we sure the process should be that the RM should switch away from
SNAPSHOT before the vote?  If a major problem is found in that RC,
wouldn't we have deployed bad artifacts under the final version number and
have to pull them back?  Or abandon that release version and use the next
version number?

IMO, the main thing folks want from Maven are the JARs which aren't an
official ASF release anyway.  Seems like we should vote on a source
package, then set any version numbers and have Maven build the final jars
from there.  The differences in the source should only be in POMs and
other configs right?

What am I missing?
-Alex

On 6/12/17, 3:53 AM, "Christofer Dutz"  wrote:

>It should be between the Last call and opening the vote. It is equal to
>“cutting the release candidate”.
>
>So, the LAST CALL thread is finished and the RM writes that he’s going to
>cut a release … AFTER THAT he does these steps and THEN he opens the vote
>thread. I never said anything else than that.
>
>Chris
>
>
>Am 12.06.17, 12:30 schrieb "piotrz" :
>
>Chris,
>
>I'm a bit confused. You have said that I shouldn't do this as part of
>VOTING, LAST CALL:
>
>"No, 
>
>The removing the SNAPSHOT, tagging and setting the new version should
>be,
>more or less, one step.
>"
>
>Now you are saying just opposite. So again when I should do this
>(Last Call,
>Voting) step ?
>
>"1) In order to have a proper Maven release, the versions of the
>maven build
>should be changed to “0.8.0” (omit the SNAPSHOT). "
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FDISCUSS-Discuss-Release-Apache-FlexJ
>S-0-8-0-RC1-tp62274p62341.html=02%7C01%7C%7C764b156340ed4161762808d4b
>1813b7a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636328616008847001
>ata=pnXSK31V8HvCRI9NlEVlGD0SgCczOCQYlw0PyoVZnfQ%3D=0
>Sent from the Apache Flex Development mailing list archive at
>Nabble.com.
>
>

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-12 Thread yishayw

Doesn't this logic mean that all the releases up to now have been invalid? 

It seems to me there is some interest in the extended community to see a
release out. Looking at the RELEASE_NOTES I see lots of nice new features
and bug fixes, which would be beneficial to people who want to start using
FlexJS.



Carlos Rovira wrote
> Total agree since the main purpose of this process is in fact to make a
> "release" and if that release can't go to Maven-Central...is not valid at
> all...





--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62349.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi Piotr,

No … all good (

I’d be happy to document things that help someone that wants to dig into Maven. 
Right now, most of my free dev-time is going to other Apache projects so my 
time is limited, but documenting this a little should be ok.

 Chris


 

Am 12.06.17, 13:25 schrieb "piotrz" :

Chris,

I hope I didn't offend you or something. I would like to understand it
clearly in order to do this if you will not be available in the next release
cause of other tasks.

Do we have your steps on confluence ? If not will you have some time to put
there as part of release process ?

Thanks, Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62343.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Chris,

I hope I didn't offend you or something. I would like to understand it
clearly in order to do this if you will not be available in the next release
cause of other tasks.

Do we have your steps on confluence ? If not will you have some time to put
there as part of release process ?

Thanks, Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62343.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

It should be between the Last call and opening the vote. It is equal to 
“cutting the release candidate”.

So, the LAST CALL thread is finished and the RM writes that he’s going to cut a 
release … AFTER THAT he does these steps and THEN he opens the vote thread. I 
never said anything else than that.

Chris


Am 12.06.17, 12:30 schrieb "piotrz" :

Chris,

I'm a bit confused. You have said that I shouldn't do this as part of
VOTING, LAST CALL:

"No, 

The removing the SNAPSHOT, tagging and setting the new version should be,
more or less, one step. 
"

Now you are saying just opposite. So again when I should do this (Last Call,
Voting) step ?

"1) In order to have a proper Maven release, the versions of the maven build
should be changed to “0.8.0” (omit the SNAPSHOT). "

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62341.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Chris,

I'm a bit confused. You have said that I shouldn't do this as part of
VOTING, LAST CALL:

"No, 

The removing the SNAPSHOT, tagging and setting the new version should be,
more or less, one step. 
"

Now you are saying just opposite. So again when I should do this (Last Call,
Voting) step ?

"1) In order to have a proper Maven release, the versions of the maven build
should be changed to “0.8.0” (omit the SNAPSHOT). "

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62341.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

No, the steps should be done as part of creating the RC not after the vote.
Otherwise you would be releasing something different than what was voted on. I 
remember is doing that for the 0.7.0 and we got quite a lot of questions from 
the different bots doing their checks.

Chris



Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: piotrz <piotrzarzyck...@gmail.com>
Datum: 12.06.17 11:56 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Ok. So all your steps are required for post VOTING.

I didn't have problems when I was building sources downloaded by
ApproveFlexJS script, but I will try again at home to make sure that I
didn't have -Dskip.rat.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62337.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Ok. So all your steps are required for post VOTING.

I didn't have problems when I was building sources downloaded by
ApproveFlexJS script, but I will try again at home to make sure that I
didn't have -Dskip.rat.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62337.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

No,

The removing the SNAPSHOT, tagging and setting the new version should be, more 
or less, one step.

The maven-release-plugin handles almost all of this in one step. So if your do 
a release:prepare all of this should happen. You can then have others checkout 
the tag and if all give their go, you run “release:perform” to stage the 
release to nexus. Or you immediately stage the release after preparing, which 
is probably what is done in most cases. As soon as the release vote is 
successful the release manager logs in to Nexus and hits the “release repo” 
button and off goes the release. 

Chris

Am 12.06.17, 11:19 schrieb "piotrz" :

Chris,

I still didn't get clear answer to my question. I would like to understand
it in order to do this in the next release. I will try to clarify my
questions:

1) Once release manager make "Last Call" - Should I remove SNAPSHOT from all
poms on release branch ?
2) Should I do 1 during VOTING ?

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62335.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Chris,

I still didn't get clear answer to my question. I would like to understand
it in order to do this in the next release. I will try to clarify my
questions:

1) Once release manager make "Last Call" - Should I remove SNAPSHOT from all
poms on release branch ?
2) Should I do 1 during VOTING ?

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62335.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Actually not by removing the credentials … by using an empty settings.xml or 
none at all and having a default. My settings-test.xml only contains the 
location of the maven local repo and no other settings therefore Maven defaults 
to its built-in defaults (I did manually provide the artifacts the mavenizer 
would have created though)

Chris

Am 12.06.17, 11:23 schrieb "Justin Mclean" :

Hi,

> mvn clean install -Drat.skip=true -s ~/.m2/settings-test.xml
> 
> (My settings-test.xml simply excludes the Apache snapshot repo)

So by just removing this right?
 
   apache.snapshots.https
   jmclean
   X
 

If so I’m still getting this:
error: patch failed: js/target/downloads/svg.js:401
error: js/target/downloads/svg.js: patch does not apply

When compiling typedefs here:
apache-flex-falconjx-0.8.0-src/flex-typedefs

> Another thing I noticed, is that the build is producing SNAPSHOT versions 
and is referencing SNAPSHOT versions. We will not be able to publish these 
artifacts to Maven Central. Well we will also not be able to publish them to 
the Apache Repo for release.

So it likely in your opinion we need to make changes and publish another RC 
or perhaps even a 0.8.1?

> bash-3.2$ git --version
> git version 2.12.0

I have  2.11.0 I’ll try 2.12.0 and see if that makes any difference.

> But not being able to release stuff to Maven-Central is reason enough for 
a -1 … sorry for that … 

You'll need to do that in the [VOTE] thread for it to count.

Thanks,
Justin

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi,

> mvn clean install -Drat.skip=true -s ~/.m2/settings-test.xml
> 
> (My settings-test.xml simply excludes the Apache snapshot repo)

So by just removing this right?
 
   apache.snapshots.https
   jmclean
   X
 

If so I’m still getting this:
error: patch failed: js/target/downloads/svg.js:401
error: js/target/downloads/svg.js: patch does not apply

When compiling typedefs here:
apache-flex-falconjx-0.8.0-src/flex-typedefs

> Another thing I noticed, is that the build is producing SNAPSHOT versions and 
> is referencing SNAPSHOT versions. We will not be able to publish these 
> artifacts to Maven Central. Well we will also not be able to publish them to 
> the Apache Repo for release.

So it likely in your opinion we need to make changes and publish another RC or 
perhaps even a 0.8.1?

> bash-3.2$ git --version
> git version 2.12.0

I have  2.11.0 I’ll try 2.12.0 and see if that makes any difference.

> But not being able to release stuff to Maven-Central is reason enough for a 
> -1 … sorry for that … 

You'll need to do that in the [VOTE] thread for it to count.

Thanks,
Justin

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-12 Thread Carlos Rovira

2017-06-12 11:03 GMT+02:00 Christofer Dutz :

>
> But not being able to release stuff to Maven-Central is reason enough for
> a -1 … sorry for that … next RC should also handle the version numbers of
> the maven pom as I described them in my last post to this thread.
>
>
Total agree since the main purpose of this process is in fact to make a
"release" and if that release can't go to Maven-Central...is not valid at
all...

Thanks Chris for taking care of this

Carlos

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Ok … so I setup a build that doesn’t accidentally pull in SNAPSHOTS from the 
Apache repo: 

mvn clean install -Drat.skip=true -s ~/.m2/settings-test.xml

(My settings-test.xml simply excludes the Apache snapshot repo)

One thing I found (no this is not going to be a legal thing … I am reporting 
this as technical issue):
When building the compiler, this fails as inside the flex-typedefs directory 
there are 3 files without correct license headers (yes exactly those ones). If 
the typedefs repo is required to be nested inside the compiler, then the maven 
rat configuration needs to be made aware of that. Verifying a release candidate 
with switched off RAT doesn’t feel right … (Not enough for a -1 though)

Another thing I noticed, is that the build is producing SNAPSHOT versions and 
is referencing SNAPSHOT versions. We will not be able to publish these 
artifacts to Maven Central. Well we will also not be able to publish them to 
the Apache Repo for release.

I could build the typedefs however with: 
mvn clean install -s ~/.m2/settings-test.xml

So, I guess the problems others are having are related to them having different 
git executalbes (I remember having problems with older git versions)

bash-3.2$ git --version
git version 2.12.0

So, this works for me, but I still think relying on command-line tools in the 
build is bad and should be replaced by a java based patch solution.

But not being able to release stuff to Maven-Central is reason enough for a -1 
… sorry for that … next RC should also handle the version numbers of the maven 
pom as I described them in my last post to this thread.

Chris


Am 12.06.17, 10:33 schrieb "carlos.rov...@gmail.com im Auftrag von Carlos 
Rovira" :

Hi Piotrz,

sorry, but I almost sure we decided to put maven as main way of building. I
know how to build with ant with the approve xml, and did it other times for
other releases, but I think is totally wrong with what we agreed in this
list.

Maybe I'm wrong but if not, It's almost strange to me not find any maven
mention, and again ANT all over the place...

I think one of the things we did (and very good from my point of view) is
put maven in good shape and many of us are working with that build system.
As other things where enhanced, this is another want to take into account
and is very rare that for this 0.8.0 is like we don't get any progress in
maven build.

I prefer not to vote this release, but don't want to bother with my way of
thinking about maven-ant.

Thanks for your help Piotr!

Carlos






2017-06-10 21:14 GMT+02:00 piotrz :

> Hi Carlos,
>
> Unfortunately Maven is not the main way of building of FlexJS.
>
> - Flex installer still serves Ant build of FlexJS for the user.
> - Maven distribution package of FlexJS has some missing thing and it is 
not
> usable by IDE - jira has been raised.
>
> As for the tests:
> I did all tests as you mention, additionally I run ApproveFalcon.xml 
script
> which help you check everything and Ant build.
> Copy ApproveFalcon.xml to empty folder and run:
>
> ant -f ApproveFalcon.xml -Drelease.version=0.8.0
>
> Piotr
>
>
>
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/DISCUSS-Discuss-Release-
> Apache-FlexJS-0-8-0-RC1-tp62274p62299.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>



-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

http://www.avant2.es


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi,

Locally I have been using Maven for 4 months or so to build Falcon / FlexJS and 
haven’t run into any major issues expect when the dual branch was first merged 
and in the last couple of days so obviously something has changed recently that 
stops this from working.

Thanks,
Justin

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Carlos,

We had pretty long discussion on ApacheCon about that. I hope we will get
the point where Maven will be the main builder for the framework.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62327.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-12 Thread Carlos Rovira

Hi Piotrz,

sorry, but I almost sure we decided to put maven as main way of building. I
know how to build with ant with the approve xml, and did it other times for
other releases, but I think is totally wrong with what we agreed in this
list.

Maybe I'm wrong but if not, It's almost strange to me not find any maven
mention, and again ANT all over the place...

I think one of the things we did (and very good from my point of view) is
put maven in good shape and many of us are working with that build system.
As other things where enhanced, this is another want to take into account
and is very rare that for this 0.8.0 is like we don't get any progress in
maven build.

I prefer not to vote this release, but don't want to bother with my way of
thinking about maven-ant.

Thanks for your help Piotr!

Carlos






2017-06-10 21:14 GMT+02:00 piotrz :

> Hi Carlos,
>
> Unfortunately Maven is not the main way of building of FlexJS.
>
> - Flex installer still serves Ant build of FlexJS for the user.
> - Maven distribution package of FlexJS has some missing thing and it is not
> usable by IDE - jira has been raised.
>
> As for the tests:
> I did all tests as you mention, additionally I run ApproveFalcon.xml script
> which help you check everything and Ant build.
> Copy ApproveFalcon.xml to empty folder and run:
>
> ant -f ApproveFalcon.xml -Drelease.version=0.8.0
>
> Piotr
>
>
>
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/DISCUSS-Discuss-Release-
> Apache-FlexJS-0-8-0-RC1-tp62274p62299.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>



-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

http://www.avant2.es


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi,

> Flex-typedefs code should be packaged in the -falconjx packages.

I can see in that in the falcon source release when when I try to compile it I 
get the following error:

error: patch failed: js/target/downloads/svg.js:401
error: js/target/downloads/svg.js: patch does not apply

Thanks,
Justin

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi Chris,

But you are saying what should happened once we are after release, not
during Release Cut and Voting ? During that time we should still use
SNAPSHOT ?

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62323.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

You were probably getting the SNAPSHOTS from the Apache SNAPSHOT repo.

Ok … I promised not to invest any more of my time in issues related to the 
double-build-system, guess I’ll make an exception …

1) In order to have a proper Maven release, the versions of the maven build 
should be changed to “0.8.0” (omit the SNAPSHOT).
2) In order to have a proper Maven release, we would need a release for 
compiler, typedefs and framework (3 and not 2 releases)

So, the proper maven release would consist of these steps:
 
1) Update the version of all compiler artifacts to 0.8.0
2) Build, including tests
3) If the build was successful, tag the code
4) Update the compiler artifacts to the next version (0.9.0-SNAPSHOT)
5) Commit these changes
6) Checkout the tagged version
7) Do a build with the “apache-release” profile turned on (This will generate 
the Javadoc, source-bundles etc. and deploy them)

As soon as that’s done, go to typedefs
1) Adjust the variable “flexjs.compiler.version” in the root pom to the newly 
released compiler version 0.8.0
2) Do the same steps as with compiler

As soon as that’s done, go to framework
1) Adjust the variable “flexjs.compiler.version” to the newly released compiler 
version 0.8.0
2) Adjust the variable “flexjs.typedefs.version” to the newly released typedefs 
version 0.8.0
3) Do the same steps as with compiler

Most of the stuff is automated using the maven-release-plugin (except the 
manual adjustment of flexjs.compiler.version and flexjs.typedefs.version.

Everything in outside of that will cause problems. Now I’m going to check if 
the current RC works for me …


Chris




Am 12.06.17, 08:02 schrieb "piotrz" :

Hi Justin,

I didn't get it and I was building by Maven straight from the sources
downloaded by ApproveFlexJS script. Can you try build typedefs and later SDK
- what will happen ?

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62319.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

2017-06-12 Thread justin

Hi,

Here’s the link to the latest failure onto build server and you can see it’s 
typedef related.

https://builds.apache.org/job/FlexJS%20Framework%20(maven)/953/console

Thanks,
Justin

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1

Hi,

> I didn't get it and I was building by Maven straight from the sources
> downloaded by ApproveFlexJS script.

Are these the same sources that are in the release? Perhaps there’s an issue 
there

BTW I’m also see the issue on develop branch and so is the apache build server.

Thanks,
Justin

Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1