The question is whether we can continue with such limited developer involvement - for whatever reason.
Our test instance on CloudBees is still being tested (usually a new user / every other day) (which surprised me) but the release is really old. D. On Mon, May 28, 2012 at 1:54 PM, Ethan Jewett <[email protected]> wrote: > Hi, > > For me it is definitely a back-burner project at the moment. On the > other hand, I do plan to continuing doing some cleanup and refactoring > work. Just my 2 cents. Sorry not be reply at more length. I've got > limited internet access at the moment but wanted to contribute my > status to the conversation. > > Cheers, > Ethan > > On Tue, May 22, 2012 at 1:35 PM, Richard Hirsch <[email protected]> wrote: >> Hi, >> >> I'd like to start our discussion about ESME and its future. >> >> Let's take a look at current state: >> >> * Development >> >> -The last commit from Ethan was 6 weeks ago and the last commit before >> that was from Vladimir and was 4 months ago. >> -There have been no new Jira items created this year >> - Last release (1.3) was in 08/2011 >> >> * Mailing lists >> >> Here are the stats for the last 5 months >> >> Apr 2012: 1 >> Mar 2012: 1 >> Feb 2012: 15 >> Jan 2012: 6 >> Dec 2011: 6 >> >> Many of these emails concerned build problems associated with Jenkins. >> >> These are all indicators that activity in the ESME community has all >> but ceased to exist. >> >> My intention isn't to make anyone feel guilty for not being active - I >> also have much less time for ESME than I did in the past - but to >> start a discussion thread discussing if and how we want to deal with >> this issue. >> >> D.
