-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this still being maintained? #131
Comments
As you may have noticed, we have a bit of a committer crisis. We did some work on it last year, but have been too busy with the day job and not working much in Java. We invited a couple of people to get involved but then they got busy too (getting volunteers is never a problem, getting active volunteers is). Personally, I have some ideas about how the library should evolve but got stuck. I'm now thinking that we should take proposals for people who want to become committers. S On 23 Dec 2015, at 09:28, Zac Sweers notifications@github.com wrote:
|
@sf105 I'm interested in becoming a hamcrest committer. Should I send some kind of introduction? I couldn't find your email address anywhere. |
@sf105 I would like to raise my hand. |
@sf105 You can also count on me |
@sf105 could you please reply for any of us? Thanks. |
@sf105 at your service :) |
@sf105 any update, please? |
@sf105 1 year since the first volunteer, lucky 1.3 is rock solid for most use cases Is there a roadmap of outstanding features before it can be released? |
Any news on this? |
Is there any way to know pending tasks on this project? I will be able to help this month in any way possible. Any mailing list where we can discuss? I am interested in the priority of the issue list so I can start looking into the issues where possible. |
You'll noticed that @tumbarumba has been doing some sterling work to sort out a new generation of releases. There is a list on hamcrest-dev@googlegroups.com |
Thanks, Steve! Well, #224 is done. I haven't really thought about the priority of other issues, or a roadmap. I see that that @sf105 has been applying the I'm going to close this issue, as I'm planning on sticking around for a bit. If the project appears to be non-responsive again in the future, feel free to jump right in! |
Noticed that there's been no commits since june, no documentation on the v2 release, and no responses to issues or PRs in the past 2-3 months.
The text was updated successfully, but these errors were encountered: