There was a number of discussions to get 1.5 out of the doors in the last few months. And I think it even got to the point where it was literally almost ready for it. But then Brett had to take care about other things and the momentum was gone again.
If there's a champion that can do the release, I as a mentor will be happy to help with it from the IPMC standpoint. And even if later we'll decide that no more releases are needed - as it might have matured enough or for another reason - it will at least have a logical end-point of its life-cycle. So, shall we release it in the next say 2 weeks? Cos On Mon, Dec 15, 2014 at 06:00PM, Roman Shaposhnik wrote: > If you guys think that the state of the code based is such > that you can do a release I can most likely help get you > 3 IPMC members to vote on it. > > Then we can do one final release and retire the poddling. > > Thanks, > Roman. > > On Mon, Dec 15, 2014 at 11:21 AM, David Akehurst <d...@akehurst.net> wrote: > > How. I'll do it if no one else does! > > > > Might even clone the code and release it myself anyways. > > > > On Monday, 15 December 2014, David Akehurst <d...@akehurst.net> wrote: > > > >> Yes please release 1.5 > >> > >> > >> > >> On Monday, 15 December 2014, Lars Corneliussen // Zen > >> <m...@lcorneliussen.de > >> <javascript:_e(%7B%7D,'cvml','m...@lcorneliussen.de');>> wrote: > >> > >>> Hi Roman, > >>> > >>> even though it "hurts" I think retiring the project is the right thing to > >>> do. > >>> Not because of the quality of NPanday, but just because the (developer!) > >>> community is effectively gone. > >>> > >>> While I'm still using NPanday every day (1.5 snapshot), it is all on the > >>> same project and there is no need for further development currently. > >>> > >>> And just the fact that we haven't been able to release 1.5 for ages shows > >>> the lack of a functioning community. > >>> > >>> I might invest in releasing 1.5 - but I might also keep saying this the > >>> years to come. > >>> > >>> Although for releasing 1.5 we wouldn't need more than somebody just doing > >>> the release with how 1.5 is now. > >>> > >>> http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/developers/releasing.html > >>> > >>> So if someone volunteers - just go ahead. > >>> _ > >>> Lars > >>> > >>> -----Ursprüngliche Nachricht----- > >>> Von: shaposh...@gmail.com [mailto:shaposh...@gmail.com] Im Auftrag von > >>> Roman Shaposhnik > >>> Gesendet: Sonntag, 14. Dezember 2014 19:29 > >>> An: npanday-dev@incubator.apache.org > >>> Cc: npanday-us...@incubator.apache.org > >>> Betreff: Re: Determining next steps for the NPanday > >>> > >>> On Sun, Dec 14, 2014 at 2:08 AM, David Akehurst <d...@akehurst.net> > >>> wrote: > >>> > I would like it to stay > >>> > I have done some development for it > >>> > >>> Please note that retirement doesn't make source code go away -- it will > >>> still be available for you to use and hack on. > >>> > >>> Retirement is ASF's way of telling outside world that even though source > >>> is still there and available, the community is gone. Now, as I said, the > >>> measure of the community "being there" could be interpreted as *at the > >>> very > >>> least* having 3 active participants since all decisions would require 3 > >>> votes minimum. > >>> > >>> Not sure if NPanday has that, but would love to be contradicted. > >>> > >>> Thanks, > >>> Roman. > >>> > >>> P.S. Finally, should 3 active participants show up after the retirement, > >>> reviving the project takes very little time. > >>> Hence its not like a permanent state of things. > >>> > >>>
