On Sun, Nov 30, 2014 at 9:25 AM, Duncan Jones <djo...@apache.org> wrote:
> On 29 Nov 2014 10:53, "Benedikt Ritter" <brit...@apache.org> wrote: > > > > Hi all, > > > > currently I feel really overwhelmed by the stuff I'd like to do at > commons > > and the little time I can spend for it. Here is an (incomplete) list of > the > > things I'd like to work on: > > > > - get a new release of the build plugin out of the door for auto creating > > README.md and CONTRIBUTING.md > > - Work on [VALIDATOR] and get a new release out of the door > > - Work on [DBUTILS] and get a new release out of the door > > - Push [lang] 3.4 out of the door > > - Have a look at [compress] 2.0 > > - Backport important fixes from [collections] 4.0 to 3.x and create a > last > > service update > > - work on [text] > > - help releasing [imaging] 1.0 > > - Improve docs on how to get involved at commons > > - Organize a logo contest for commons > > - ... many more > > > > I wonder how you feel about this. I have the feeling that a lot of people > > ask us to fix stuff and release components but we don't really catch up > > with this. This will give people the feeling that we are slow or we > simply > > don't care. > > Is the release process unnecessarily cumbersome for the RM? RM'ing is a PITA IMO. I do not see it changing any time soon. The dual distribution to Maven Central and the Apache Dist server complicates things of course. It's plain silly IMO, we should just push to an Apache Maven repo and be done. But... that's a topic for Apache at large. > If so, perhaps > some time spent automating more of the procedure would be worthwhile. > > Maybe we could consider some guidelines for when a release is needed. E.g. > After X fixes or Y new features then a release ought to happen unless there > is a strong reason not to. > While I appreciate the good intention, you still need a volunteer RM. It does not matter how many fixes are pending and whether we have rules that say we must release. I like RERO myself but the release gymnastics are lame... but that is what we have now and I do not see change it an easy thing to do... Perhaps we can pick some topics to discuss individually. Gary > > Duncan > > > Whenever I see someone posting on JIRA "can you please fix this, we need > > this in out application" and nobody is reacting, I feel tempted to jump > > right in, even if I don't know the component (which adds another entry to > > the list above). > > I don't see a way how we can improve this. My feeling is, that we need > more > > committers. But then I have the comments of people I've talked to in my > > ear: "to old school", "to difficult to get involved", "to slow > development > > process", "to unwelcoming community". So what do we do? Do we need help? > > > > I'm excited to hear your thoughts :-) > > > > Best regards, > > Benedikt > > > > > > -- > > http://people.apache.org/~britter/ > > http://www.systemoutprintln.de/ > > http://twitter.com/BenediktRitter > > http://github.com/britter > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
