You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Christofer Dutz <ch...@c-ware.de> on 2014/11/16 22:47:35 UTC
[DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Hi,
so I learned a lot more this time.
First of all: If you follow the normal release path of "mvn release:prepare" "mvn release:perform" the tags arent created correctly. You have to set the version to the release version and set the tag property manually, commit and tag that commit manually. After that a "mvn -P apache-release deploy" has to be issued to stage the release candidate. As soon as that was successfully, update the version to the next development version and set the tag back to HEAD. (I just thught I'd post that for documenting it)
Also I left the staging repo open the last time. This time I closed it which makes Nexus do all sorts of PGP checks as well as checks if the poms respect the apache release policy and all mandatory fields contain valid values. After the repo is closed you actually get a public url for testing the RC:
https://repository.apache.org/content/repositories/orgapacheflex-1001?
Think with this it's a lot easier to check.
Chris
AW: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Christofer Dutz <ch...@c-ware.de>.
Having a look at this, I have to agree that the RC3 was pretty ugly. Fortunately I have gotten fast with creating new RCs so I create an RC4:
https://repository.apache.org/content/repositories/orgapacheflex-1003/
Starting the new VOTE thread right away.
Chris
________________________________________
Von: Justin Mclean <ju...@classsoftware.com>
Gesendet: Dienstag, 18. November 2014 10:48
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Hi,
Just had a look at RC3 and looks like with still have the pom tag issue;
<tag>apache-flex-tool-api-1.0.0-RC3</tag>
Shouldn't this point what what teh tag will be when the software is released?
Justin
Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Justin, Erik is right. You should try to be more careful.
I do try to be careful but I made a mistake. I have no issue with constructive criticism. My response was trying to inject a little humour into the situation and perhaps point out we're being IMO a little silly about this. There should be no need to clog up the mailing list with messages about misspelling the word "rhe".
Thanks,
Justin
RE: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
One of the phrases I try to practice is this [1]. It gives the assumption that the text doesn't convey jokes and sarcasm well.
[1] "Assume positive intent".
-Mark
Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Erik de Bruin <er...@ixsoftware.nl>.
>
> Erik, I’m not sure Justin takes criticism very well from you. It might be
> more effective if you leave that to someone else.
>
I'm afraid you're right :-(
Thanks for taking this one. I'll refrain from commenting any more on this
or future instances (of which I hope there will be few).
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Harbs <ha...@gmail.com>.
Justin, Erik is right. You should try to be more careful. I’m a native English speaker and I had to read it more than once to make sure I read it right. I was not sure if you were referring to a specific tag. There’s no reason to get defensive. Take it for what it was: constructive criticism.
Erik, I’m not sure Justin takes criticism very well from you. It might be more effective if you leave that to someone else.
Harbs
On Nov 18, 2014, at 12:50 PM, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
>> "what what teh"?
>
> I don't think we need remind people every time they get a a letter out of place or autocorrect picks the wrong word. Not matter how careful you are mistakes are sill going to slip though.
>
> Also:
> Aoccdrnig to rscheearch at Cmabrigde Uinervtisy, it deosn't mttaer in waht oredr the ltteers in a wrod are, the olny iprmoetnt tihng is taht the frist and lsat ltteer be at the rghit pclae. The rset can be a toatl mses and you can sitll raed it wouthit a porbelm. Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef, but the wrod as a wlohe.
>
> Most people can read above just as easily as the correct spelling and in fact may not even notice that words are misspelled.
>
> Thanks,
> Justin
Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> "what what teh"?
I don't think we need remind people every time they get a a letter out of place or autocorrect picks the wrong word. Not matter how careful you are mistakes are sill going to slip though.
Also:
Aoccdrnig to rscheearch at Cmabrigde Uinervtisy, it deosn't mttaer in waht oredr the ltteers in a wrod are, the olny iprmoetnt tihng is taht the frist and lsat ltteer be at the rghit pclae. The rset can be a toatl mses and you can sitll raed it wouthit a porbelm. Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef, but the wrod as a wlohe.
Most people can read above just as easily as the correct spelling and in fact may not even notice that words are misspelled.
Thanks,
Justin
Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Erik de Bruin <er...@ixsoftware.nl>.
>
> Shouldn't this point what what teh tag will be when the software is
> released?
>
"what what teh"?
Please be more careful writing emails, as per our recent consensus on email
etiquette. Mistakes in spelling easily translate into misunderstandings
about intend. There is no hurry when dealing with these types of issues, so
if you don't have time to re-read emails and make sure they are properly
spelled etc., please hold off on sending until you do.
Thanks,
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Just had a look at RC3 and looks like with still have the pom tag issue;
<tag>apache-flex-tool-api-1.0.0-RC3</tag>
Shouldn't this point what what teh tag will be when the software is released?
Justin
AW: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok ... so after all adjusting the files again, I fixed the README again and staged RC3 ... hopefully now all will be sattisfied :-)
Chris
PS: Starting the new vote thread now ....
________________________________________
Von: Erik de Bruin <er...@ixsoftware.nl>
Gesendet: Montag, 17. November 2014 09:28
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
I ran rat, it didn't catch anything but the DEPENDENCIES, for which I added
an exception. Are these files platform specific?
And the 'nits', you can basically do what you think is best, but at the
risk of starting another huge thread about nothing: either en_US or en_GB
are perfectly fine for the rest of the world, and I think native speakers
at both ends of the ocean will be able to figure out how to use Google
Translate if they don't understand one form or the other ...
EdB
On Mon, Nov 17, 2014 at 8:42 AM, Alex Harui <ah...@adobe.com> wrote:
> Ugh, somehow we all missed the fact that there aren’t Apache headers on
> assembly/assemble*.xml. Can anyone think of a way we can make an
> exception? Are they auto-generated? Did they come from somewhere else?
> Do the lack any creativity? Otherwise we have to roll an RC3. I checked
> in Apache headers on those files.
>
> And if we do make an RC3, I also fixed a couple of minor nits in the
> README and RELEASE_NOTES.
>
> Thoughts?
> -Alex
>
> On 11/16/14, 1:47 PM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>
> >Hi,
> >
> >
> >so I learned a lot more this time.
> >
> >First of all: If you follow the normal release path of "mvn
> >release:prepare" "mvn release:perform" the tags arent created correctly.
> >You have to set the version to the release version and set the tag
> >property manually, commit and tag that commit manually. After that a "mvn
> >-P apache-release deploy" has to be issued to stage the release
> >candidate. As soon as that was successfully, update the version to the
> >next development version and set the tag back to HEAD. (I just thught I'd
> >post that for documenting it)
> >
> >Also I left the staging repo open the last time. This time I closed it
> >which makes Nexus do all sorts of PGP checks as well as checks if the
> >poms respect the apache release policy and all mandatory fields contain
> >valid values. After the repo is closed you actually get a public url for
> >testing the RC:
> >
> >
> >https://repository.apache.org/content/repositories/orgapacheflex-1001?
> >
> >
> >Think with this it's a lot easier to check.
> >
> >
> >Chris
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I ran rat, it didn't catch anything but the DEPENDENCIES, for which I added
an exception. Are these files platform specific?
And the 'nits', you can basically do what you think is best, but at the
risk of starting another huge thread about nothing: either en_US or en_GB
are perfectly fine for the rest of the world, and I think native speakers
at both ends of the ocean will be able to figure out how to use Google
Translate if they don't understand one form or the other ...
EdB
On Mon, Nov 17, 2014 at 8:42 AM, Alex Harui <ah...@adobe.com> wrote:
> Ugh, somehow we all missed the fact that there aren’t Apache headers on
> assembly/assemble*.xml. Can anyone think of a way we can make an
> exception? Are they auto-generated? Did they come from somewhere else?
> Do the lack any creativity? Otherwise we have to roll an RC3. I checked
> in Apache headers on those files.
>
> And if we do make an RC3, I also fixed a couple of minor nits in the
> README and RELEASE_NOTES.
>
> Thoughts?
> -Alex
>
> On 11/16/14, 1:47 PM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>
> >Hi,
> >
> >
> >so I learned a lot more this time.
> >
> >First of all: If you follow the normal release path of "mvn
> >release:prepare" "mvn release:perform" the tags arent created correctly.
> >You have to set the version to the release version and set the tag
> >property manually, commit and tag that commit manually. After that a "mvn
> >-P apache-release deploy" has to be issued to stage the release
> >candidate. As soon as that was successfully, update the version to the
> >next development version and set the tag back to HEAD. (I just thught I'd
> >post that for documenting it)
> >
> >Also I left the staging repo open the last time. This time I closed it
> >which makes Nexus do all sorts of PGP checks as well as checks if the
> >poms respect the apache release policy and all mandatory fields contain
> >valid values. After the repo is closed you actually get a public url for
> >testing the RC:
> >
> >
> >https://repository.apache.org/content/repositories/orgapacheflex-1001?
> >
> >
> >Think with this it's a lot easier to check.
> >
> >
> >Chris
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Posted by Alex Harui <ah...@adobe.com>.
Ugh, somehow we all missed the fact that there aren’t Apache headers on
assembly/assemble*.xml. Can anyone think of a way we can make an
exception? Are they auto-generated? Did they come from somewhere else?
Do the lack any creativity? Otherwise we have to roll an RC3. I checked
in Apache headers on those files.
And if we do make an RC3, I also fixed a couple of minor nits in the
README and RELEASE_NOTES.
Thoughts?
-Alex
On 11/16/14, 1:47 PM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Hi,
>
>
>so I learned a lot more this time.
>
>First of all: If you follow the normal release path of "mvn
>release:prepare" "mvn release:perform" the tags arent created correctly.
>You have to set the version to the release version and set the tag
>property manually, commit and tag that commit manually. After that a "mvn
>-P apache-release deploy" has to be issued to stage the release
>candidate. As soon as that was successfully, update the version to the
>next development version and set the tag back to HEAD. (I just thught I'd
>post that for documenting it)
>
>Also I left the staging repo open the last time. This time I closed it
>which makes Nexus do all sorts of PGP checks as well as checks if the
>poms respect the apache release policy and all mandatory fields contain
>valid values. After the repo is closed you actually get a public url for
>testing the RC:
>
>
>https://repository.apache.org/content/repositories/orgapacheflex-1001?
>
>
>Think with this it's a lot easier to check.
>
>
>Chris