You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-dev@incubator.apache.org by Roman Shaposhnik <ro...@shaposhnik.org> on 2015/01/06 00:54:51 UTC
Re: Determining next steps for the NPanday
Guys, I'm afraid with such a low level of response to the
idea of 1.5.0 release we'd have to proceed under the
assumption that there are no community cycles available
to make it happen within couple of weeks.
Fair?
Thanks,
Roman.
On Fri, Dec 19, 2014 at 9:06 PM, Konstantin Boudnik <co...@apache.org> wrote:
> So, any thoughts about the 1.5.0 release? Any volunteers to step up as the
> release manager?
>
> Happy holidays everyone.
> Cos
>
> On Tue, Dec 16, 2014 at 04:25AM, Konstantin Boudnik wrote:
>> 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 <da...@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 <da...@akehurst.net> wrote:
>> > >
>> > >> Yes please release 1.5
>> > >>
>> > >>
>> > >>
>> > >> On Monday, 15 December 2014, Lars Corneliussen // Zen <me@lcorneliussen.de
>> > >> <javascript:_e(%7B%7D,'cvml','me@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: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] Im Auftrag von
>> > >>> Roman Shaposhnik
>> > >>> Gesendet: Sonntag, 14. Dezember 2014 19:29
>> > >>> An: npanday-dev@incubator.apache.org
>> > >>> Cc: npanday-users@incubator.apache.org
>> > >>> Betreff: Re: Determining next steps for the NPanday
>> > >>>
>> > >>> On Sun, Dec 14, 2014 at 2:08 AM, David Akehurst <da...@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.
>> > >>>
>> > >>>
Re: Determining next steps for the NPanday
Posted by Konstantin Boudnik <co...@apache.org>.
Also, I presume the report won't happen this time around as noone has answered
my email from a few days ago.
Cos
On Mon, Jan 05, 2015 at 04:54PM, Roman Shaposhnik wrote:
> Guys, I'm afraid with such a low level of response to the
> idea of 1.5.0 release we'd have to proceed under the
> assumption that there are no community cycles available
> to make it happen within couple of weeks.
>
> Fair?
>
> Thanks,
> Roman.
>
> On Fri, Dec 19, 2014 at 9:06 PM, Konstantin Boudnik <co...@apache.org> wrote:
> > So, any thoughts about the 1.5.0 release? Any volunteers to step up as the
> > release manager?
> >
> > Happy holidays everyone.
> > Cos
> >
> > On Tue, Dec 16, 2014 at 04:25AM, Konstantin Boudnik wrote:
> >> 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 <da...@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 <da...@akehurst.net> wrote:
> >> > >
> >> > >> Yes please release 1.5
> >> > >>
> >> > >>
> >> > >>
> >> > >> On Monday, 15 December 2014, Lars Corneliussen // Zen <me@lcorneliussen.de
> >> > >> <javascript:_e(%7B%7D,'cvml','me@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: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] Im Auftrag von
> >> > >>> Roman Shaposhnik
> >> > >>> Gesendet: Sonntag, 14. Dezember 2014 19:29
> >> > >>> An: npanday-dev@incubator.apache.org
> >> > >>> Cc: npanday-users@incubator.apache.org
> >> > >>> Betreff: Re: Determining next steps for the NPanday
> >> > >>>
> >> > >>> On Sun, Dec 14, 2014 at 2:08 AM, David Akehurst <da...@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.
> >> > >>>
> >> > >>>
Re: Determining next steps for the NPanday
Posted by Konstantin Boudnik <co...@apache.org>.
What Roman said. I am happy to help with the release process from guidance
standpoint, but I won't be able to help with the release itself as I don't
have the knowledge in the project's mechanics.
Cos
On Thu, Jan 08, 2015 at 06:52AM, Roman Shaposhnik wrote:
> On Tue, Jan 6, 2015 at 3:04 PM, me@lcorneliussen.de <me...@lcorneliussen.de> wrote:
> > http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/developers/releasing.html
> >
> > I'm sure Brett is happy to assist (I have never done a release either...)
>
> Sure. The question is: who does have cycles to go through all of these steps?
> I sure don't. My original offer was only to vote on a tarball prepared by the
> community. That preparation -- I can NOT help with it.
>
> If the community doesn't have cycles as well, I'm afraid, we'd have to proceed
> with the retirement part of the discussion without waiting for a release.
>
> Thanks,
> Roman.
Re: Determining next steps for the NPanday
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Tue, Jan 6, 2015 at 3:04 PM, me@lcorneliussen.de <me...@lcorneliussen.de> wrote:
> http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/developers/releasing.html
>
> I'm sure Brett is happy to assist (I have never done a release either...)
Sure. The question is: who does have cycles to go through all of these steps?
I sure don't. My original offer was only to vote on a tarball prepared by the
community. That preparation -- I can NOT help with it.
If the community doesn't have cycles as well, I'm afraid, we'd have to proceed
with the retirement part of the discussion without waiting for a release.
Thanks,
Roman.
Re: Determining next steps for the NPanday
Posted by "me@lcorneliussen.de" <me...@lcorneliussen.de>.
http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/developers/releasing.html
I'm sure Brett is happy to assist (I have never done a release either...)
_
Mobil versendet
> Am 06.01.2015 um 07:42 schrieb David Akehurst <da...@akehurst.net>:
>
> I would be willing to work on the release, but am not sure how to do it.
>
>> On Tuesday, 6 January 2015, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>>
>> Guys, I'm afraid with such a low level of response to the
>> idea of 1.5.0 release we'd have to proceed under the
>> assumption that there are no community cycles available
>> to make it happen within couple of weeks.
>>
>> Fair?
>>
>> Thanks,
>> Roman.
>>
>> On Fri, Dec 19, 2014 at 9:06 PM, Konstantin Boudnik <cos@apache.org
>> <javascript:;>> wrote:
>>> So, any thoughts about the 1.5.0 release? Any volunteers to step up as
>> the
>>> release manager?
>>>
>>> Happy holidays everyone.
>>> Cos
>>>
>>>> On Tue, Dec 16, 2014 at 04:25AM, Konstantin Boudnik wrote:
>>>> 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 <dave@akehurst.net
>> <javascript:;>> 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 <dave@akehurst.net
>> <javascript:;>> wrote:
>>>>>>
>>>>>>> Yes please release 1.5
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Monday, 15 December 2014, Lars Corneliussen // Zen <
>> me@lcorneliussen.de <javascript:;>
>>>>>>> <javascript:_e(%7B%7D,'cvml','me@lcorneliussen.de <javascript:;>');>>
>> 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: shaposhnik@gmail.com <javascript:;> [mailto:
>> shaposhnik@gmail.com <javascript:;>] Im Auftrag von
>>>>>>>> Roman Shaposhnik
>>>>>>>> Gesendet: Sonntag, 14. Dezember 2014 19:29
>>>>>>>> An: npanday-dev@incubator.apache.org <javascript:;>
>>>>>>>> Cc: npanday-users@incubator.apache.org <javascript:;>
>>>>>>>> Betreff: Re: Determining next steps for the NPanday
>>>>>>>>
>>>>>>>> On Sun, Dec 14, 2014 at 2:08 AM, David Akehurst <
>> dave@akehurst.net <javascript:;>>
>>>>>>>> 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.
>>
Re: Determining next steps for the NPanday
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Thu, Jan 8, 2015 at 12:50 AM, David Akehurst <da...@akehurst.net> wrote:
> I will try
What's the timeline on this?
Thanks,
Roman.
Re: Determining next steps for the NPanday
Posted by David Akehurst <da...@akehurst.net>.
I will try
On 6 January 2015 at 19:37, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> On Mon, Jan 5, 2015 at 10:42 PM, David Akehurst <da...@akehurst.net> wrote:
> > I would be willing to work on the release, but am not sure how to do it.
>
> At this point, what would be required from you is producing a tarball
> containing what you would want to publish as a release. Do you think
> you can accomplish this in two weeks or so?
>
> Thanks,
> Roman.
>
Re: Determining next steps for the NPanday
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Jan 5, 2015 at 10:42 PM, David Akehurst <da...@akehurst.net> wrote:
> I would be willing to work on the release, but am not sure how to do it.
At this point, what would be required from you is producing a tarball
containing what you would want to publish as a release. Do you think
you can accomplish this in two weeks or so?
Thanks,
Roman.
Re: Determining next steps for the NPanday
Posted by David Akehurst <da...@akehurst.net>.
I would be willing to work on the release, but am not sure how to do it.
On Tuesday, 6 January 2015, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> Guys, I'm afraid with such a low level of response to the
> idea of 1.5.0 release we'd have to proceed under the
> assumption that there are no community cycles available
> to make it happen within couple of weeks.
>
> Fair?
>
> Thanks,
> Roman.
>
> On Fri, Dec 19, 2014 at 9:06 PM, Konstantin Boudnik <cos@apache.org
> <javascript:;>> wrote:
> > So, any thoughts about the 1.5.0 release? Any volunteers to step up as
> the
> > release manager?
> >
> > Happy holidays everyone.
> > Cos
> >
> > On Tue, Dec 16, 2014 at 04:25AM, Konstantin Boudnik wrote:
> >> 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 <dave@akehurst.net
> <javascript:;>> 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 <dave@akehurst.net
> <javascript:;>> wrote:
> >> > >
> >> > >> Yes please release 1.5
> >> > >>
> >> > >>
> >> > >>
> >> > >> On Monday, 15 December 2014, Lars Corneliussen // Zen <
> me@lcorneliussen.de <javascript:;>
> >> > >> <javascript:_e(%7B%7D,'cvml','me@lcorneliussen.de <javascript:;>');>>
> 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: shaposhnik@gmail.com <javascript:;> [mailto:
> shaposhnik@gmail.com <javascript:;>] Im Auftrag von
> >> > >>> Roman Shaposhnik
> >> > >>> Gesendet: Sonntag, 14. Dezember 2014 19:29
> >> > >>> An: npanday-dev@incubator.apache.org <javascript:;>
> >> > >>> Cc: npanday-users@incubator.apache.org <javascript:;>
> >> > >>> Betreff: Re: Determining next steps for the NPanday
> >> > >>>
> >> > >>> On Sun, Dec 14, 2014 at 2:08 AM, David Akehurst <
> dave@akehurst.net <javascript:;>>
> >> > >>> 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.
> >> > >>>
> >> > >>>
>