Hi Justin, thanks for looking into this. I'll go through your comments one by one: - I tagged the release RC1 cause it was the RC1 and I remember having trouble deleting and re-adding a tag. If it's not a problem to delete a tag, I'd be glad to change this. - Do you suggest to call the artifacts "apache-flex-messageing-{module}"? What do the others think about this? How about changing that to from "flex-messaging" to "apache-blazeds"? - Didn't Alex change this to 20XX-2015? Gee ... just saw this was only on the NOTICE in the root ... not the modules directory :-( - I removed the part about the bugfixes in the Readme, as not a single real bugfix was applied since the donation. What happened before that ... I don't know. - Adjusted the README to no longer reference the modules directory - Found another problem in the README in which I referenced the "Flex Tool API" instead of "Apache BlazeDS" ... fixed that too.
I'll wait another day till I spin up another RC assuming that your +0 will become a +1 as soon as these things are addressed and I want to give others a chance to find more stuff. Chris -----Ursprüngliche Nachricht----- Von: Justin Mclean [mailto:jus...@classsoftware.com] Gesendet: Sonntag, 1. März 2015 08:13 An: dev@flex.apache.org Betreff: Re: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1 Hi, One thing I did noticed about the code is the large number of @author tags. This is generally frowned on in Apache. [1][2] Should we remove them? Thanks, Justin 1. http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_09_22.txt (read 7F) 2 http://opensource.com/law/14/2/copyright-statements-source-files