You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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 Hamcrest future label. There needs to be a discussion (on the mailing list, perhaps) about what the future of Hamcrest should be. However, there are always documentation updates and bug fixes. Pull requests are always appreciated!
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!
Activity
sf105 commentedon Dec 31, 2015
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:
erosb commentedon Jan 4, 2016
@sf105 I'm interested in becoming a hamcrest committer. Should I send some kind of introduction? I couldn't find your email address anywhere.
npathai commentedon Jan 7, 2016
@sf105 I would like to raise my hand.
trirano commentedon Jan 9, 2016
@sf105 You can also count on me
erosb commentedon Jan 18, 2016
@sf105 could you please reply for any of us? Thanks.
gokhanbarisaker commentedon Jan 23, 2016
@sf105 at your service :)
erosb commentedon Mar 11, 2016
@sf105 any update, please?
TWiStErRob commentedon Jan 30, 2017
@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?
Edit: just found 2.0.0.0, but it's not on https://github.com/hamcrest/JavaHamcrest/releases
sandra-thieme commentedon Oct 7, 2017
Any news on this?
tusharjoshi commentedon Dec 8, 2018
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.
sf105 commentedon Dec 12, 2018
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
tumbarumba commentedon Dec 26, 2018
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
Hamcrest futurelabel. There needs to be a discussion (on the mailing list, perhaps) about what the future of Hamcrest should be. However, there are always documentation updates and bug fixes. Pull requests are always appreciated!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!