Actually, my hope was to have someone here say "c'mon, not bumping to Java6? Are you nuts?" and then continue with, "listen, you code _today_ something that will be hopefully used 3-4 years from today. But, you are _prevented_ to leave something that is already dead _today_ for 3 years (will be 6-7 years during hopeful use of this release), you are prevented to bump the source to something that _will be dead_ in months from _today_... it does not make sense, especially as this is a major 5.x release....". Also, someone else could chime in with "those locked to java 5 and java 4 should seriously stop and think a bit". And another with "we [ASF] are an open, non-profit OSS forge, doing development for our own sake and love. so did the company [since it's not a natural person I hope] making you wont-fix this Java6 bump at least a golden sponsor of next upcoming ApacheCon?" and so on :D
etc. Thanks, ~t~ On Wed, Sep 12, 2012 at 11:34 AM, Anders Hammar <[email protected]> wrote: > Should MINDEXER-60 really have a fix version as it is won't fix? It > could trick people just browsing the list of tickets associated with > this relaese to think this has been introduced. > > /Anders > > On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák <[email protected]> > wrote: > > Howdy, > > > > there are a notable changes in trunk of MI: > > > https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC > > > > https://github.com/apache/maven-indexer/commits/trunk?page=1 > > > > > > So, I'd like to spin a release of it. > > > > Any objections to this? Any last minute wish? > > > > > > Thanks, > > ~t~ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
