architecture rules 2.1.1
5 views
Skip to first unread message
Mike Nereson
Jul 10, 2008, 11:11:07 PM7/10/08
to architecture...@googlegroups.com, architectur...@googlegroups.com
So, Architecture Rules 2.1.0 was released past week. Things seemed great, but it turns outs they weren't all that great.
I wrote about it here, but to summarize: 2.1.0 got a lot of press leading to 120 new downloads (only 220 the entire rest of the year), but it turns out there was a bug in the AbstractRulesService that was introduced the day before the release. So now we have all of these new users, using a busted tool, many of which have probably already scrapped it and won't come back. All we can do is hope that many of them are see the value of this tool and want to mitigate architectural risks, and will come back looking for the next release with the fixed bug. The good news is that if they didn't use wildcards, the bug will not manifest. The bad news is, they probably used wildcards.
For all of you, 2.1.1 is up and ready. The only change is this bug should be fixed. You can get the new release here.
I got a ton of email from new users this past week. Many with great comments about the project, and a few who had some recommendations. It seems like some of you might be interested in contributing to the project, which I am excited about and open to. If this is something that interests you, a great way to start is by creating new issues in the issue tracker, and then fixing the issue and attaching the patch, like the way that Oliver did here. For those of you looking to get involved, but don't know what you can do come right this way... I just setup the maven checkstyle plugin. I want the project to conform the Sun coding standards, which it does not in anyway resemble at this time... So if you want to help, you can fix issues on the Find Bugs report or the Checkstyle report which is currently horrendus. So, just find something to fix, create a new issue here , fix it, attach the patch to the issue and, if you want, you will probably be a bonafide commiter in no time.
Thanks everyone. Thanks for giving us another try, and thanks for your contributions.
PS. If you want to help get architecturerules.org for the site and package name, you can help by donating a few dollars here I'd like to secure the $30 to register the domain for 3 years. I would appreciate any help with this, and it would help us get to org.architecturerules sooner rather than later. Thanks again.
~ Mike Nereson
~ http://72miles.com/blog
I wrote about it here, but to summarize: 2.1.0 got a lot of press leading to 120 new downloads (only 220 the entire rest of the year), but it turns out there was a bug in the AbstractRulesService that was introduced the day before the release. So now we have all of these new users, using a busted tool, many of which have probably already scrapped it and won't come back. All we can do is hope that many of them are see the value of this tool and want to mitigate architectural risks, and will come back looking for the next release with the fixed bug. The good news is that if they didn't use wildcards, the bug will not manifest. The bad news is, they probably used wildcards.
For all of you, 2.1.1 is up and ready. The only change is this bug should be fixed. You can get the new release here.
I got a ton of email from new users this past week. Many with great comments about the project, and a few who had some recommendations. It seems like some of you might be interested in contributing to the project, which I am excited about and open to. If this is something that interests you, a great way to start is by creating new issues in the issue tracker, and then fixing the issue and attaching the patch, like the way that Oliver did here. For those of you looking to get involved, but don't know what you can do come right this way... I just setup the maven checkstyle plugin. I want the project to conform the Sun coding standards, which it does not in anyway resemble at this time... So if you want to help, you can fix issues on the Find Bugs report or the Checkstyle report which is currently horrendus. So, just find something to fix, create a new issue here , fix it, attach the patch to the issue and, if you want, you will probably be a bonafide commiter in no time.
Thanks everyone. Thanks for giving us another try, and thanks for your contributions.
PS. If you want to help get architecturerules.org for the site and package name, you can help by donating a few dollars here I'd like to secure the $30 to register the domain for 3 years. I would appreciate any help with this, and it would help us get to org.architecturerules sooner rather than later. Thanks again.
~ Mike Nereson
~ http://72miles.com/blog
Reply all
Reply to author
Forward
0 new messages