You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by "Tom Barber(Alabs)" <to...@analytical-labs.com> on 2014/07/18 09:53:03 UTC
Filemgr Tests
Shifted some development wishes from private@ to dev@ for Chris ;)
Na I'm only messing, but I do think more care should be taken with
commits vs the test suite because I would like to do the Tika upgrade,
fix the database dialects etc, but I only feel comfortable hacking
around with that stuff if we know the tests work because I don't know
enough about the feature set of the components that I've not used and as
such rely on the tests to tell me what I've borked or not.
Equally should I break a test I'd expect my commits to be reverted and
I'd be asked to fix them before recommitting instead of just putting up
with broken tests.
Lets make it so! ;)
Tom
Re: Filemgr Tests
Posted by "Verma, Rishi (398J)" <Ri...@jpl.nasa.gov>.
Tom,
I think your comments hit home. This is exactly what we need to be doing. I think Sean Kelly is trying to set up a call/coordination meeting, did you see the message for that?
> c) Are there any better ways of sorting out, planning, roadmaps, meetings, community stuff, and collaboration on tasks, that we can take from other Apache projects, because, whilst I enjoy OODT, and the ideas behind it (and I appreciate within the NASA bunch there is probably more cohesion), it seems a little rudderless in terms of direction. Feel free to flame me at this point lovely community people.
Yeah - mailing lists are good but I think what would help is definitely a "road map" document, perhaps on the wiki or even the website. i.e. what the goal is for the next release, and how far off are we? JIRA has some tools to support this we may want to leverage. Will look more at it.
Rishi
On Jul 18, 2014, at 5:21 PM, Tom Barber wrote:
> Hello OODT Development Team
>
> I was wondering if
> a) it would make sense for us to either have a call at some point, or just get a thread/jira started that allows us to get a rough idea of what aspects of OODT people are working on, what they need etc as currently I don't think many of us have a real clue
> b) On the new website, would it be worth publishing a "roadmap" cause, I have no clue where the project is going
> c) Are there any better ways of sorting out, planning, roadmaps, meetings, community stuff, and collaboration on tasks, that we can take from other Apache projects, because, whilst I enjoy OODT, and the ideas behind it (and I appreciate within the NASA bunch there is probably more cohesion), it seems a little rudderless in terms of direction. Feel free to flame me at this point lovely community people.
>
> Regards
>
> Tom
Re: Filemgr Tests
Posted by Tom Barber <to...@meteorite.bi>.
One thing that did cross my mind is with everything being so user/data
driven it might make sense to add a TDD/BDD test suite as it would allow
people to write functional tests.... and living documentation! ;)
But again that requires s stable base to create one off.
On 19 Jul 2014 07:51, "Tom Barber" <to...@meteorite.bi> wrote:
> Well like I said, let me know if I can help finish the tests off.
>
> Tom
> On 19 Jul 2014 00:34, "Lewis John Mcgibbney" <le...@gmail.com>
> wrote:
>
>> I'm going to let this stew over the weekend and come up with some comments
>> of my own Tom.
>> There is a LOT for discussion.
>>
>>
>> On Fri, Jul 18, 2014 at 5:21 PM, Tom Barber <to...@meteorite.bi>
>> wrote:
>>
>> > Hello OODT Development Team
>> >
>> > I was wondering if
>> > a) it would make sense for us to either have a call at some point, or
>> just
>> > get a thread/jira started that allows us to get a rough idea of what
>> > aspects of OODT people are working on, what they need etc as currently I
>> > don't think many of us have a real clue
>> > b) On the new website, would it be worth publishing a "roadmap" cause, I
>> > have no clue where the project is going
>> > c) Are there any better ways of sorting out, planning, roadmaps,
>> meetings,
>> > community stuff, and collaboration on tasks, that we can take from other
>> > Apache projects, because, whilst I enjoy OODT, and the ideas behind it
>> (and
>> > I appreciate within the NASA bunch there is probably more cohesion), it
>> > seems a little rudderless in terms of direction. Feel free to flame me
>> at
>> > this point lovely community people.
>> >
>> > Regards
>> >
>> > Tom
>> >
>>
>>
>>
>> --
>> *Lewis*
>>
>
Re: Filemgr Tests
Posted by Tom Barber <to...@meteorite.bi>.
Well like I said, let me know if I can help finish the tests off.
Tom
On 19 Jul 2014 00:34, "Lewis John Mcgibbney" <le...@gmail.com>
wrote:
> I'm going to let this stew over the weekend and come up with some comments
> of my own Tom.
> There is a LOT for discussion.
>
>
> On Fri, Jul 18, 2014 at 5:21 PM, Tom Barber <to...@meteorite.bi>
> wrote:
>
> > Hello OODT Development Team
> >
> > I was wondering if
> > a) it would make sense for us to either have a call at some point, or
> just
> > get a thread/jira started that allows us to get a rough idea of what
> > aspects of OODT people are working on, what they need etc as currently I
> > don't think many of us have a real clue
> > b) On the new website, would it be worth publishing a "roadmap" cause, I
> > have no clue where the project is going
> > c) Are there any better ways of sorting out, planning, roadmaps,
> meetings,
> > community stuff, and collaboration on tasks, that we can take from other
> > Apache projects, because, whilst I enjoy OODT, and the ideas behind it
> (and
> > I appreciate within the NASA bunch there is probably more cohesion), it
> > seems a little rudderless in terms of direction. Feel free to flame me at
> > this point lovely community people.
> >
> > Regards
> >
> > Tom
> >
>
>
>
> --
> *Lewis*
>
Re: Filemgr Tests
Posted by Tom Barber <to...@meteorite.bi>.
Eh?
On 25 Jul 2014 08:05, "Lewis John Mcgibbney" <le...@gmail.com>
wrote:
> Reversed Tom.
>
>
>
> On Mon, Jul 21, 2014 at 4:49 AM, Tom Barber <to...@meteorite.bi>
> wrote:
>
> > Hows the stew? ;)
> >
> >
> > On 19/07/14 00:33, Lewis John Mcgibbney wrote:
> >
> >> I'm going to let this stew over the weekend and come up with some
> comments
> >> of my own Tom.
> >> There is a LOT for discussion.
> >>
> >>
> >> On Fri, Jul 18, 2014 at 5:21 PM, Tom Barber <to...@meteorite.bi>
> >> wrote:
> >>
> >> Hello OODT Development Team
> >>>
> >>> I was wondering if
> >>> a) it would make sense for us to either have a call at some point, or
> >>> just
> >>> get a thread/jira started that allows us to get a rough idea of what
> >>> aspects of OODT people are working on, what they need etc as currently
> I
> >>> don't think many of us have a real clue
> >>> b) On the new website, would it be worth publishing a "roadmap" cause,
> I
> >>> have no clue where the project is going
> >>> c) Are there any better ways of sorting out, planning, roadmaps,
> >>> meetings,
> >>> community stuff, and collaboration on tasks, that we can take from
> other
> >>> Apache projects, because, whilst I enjoy OODT, and the ideas behind it
> >>> (and
> >>> I appreciate within the NASA bunch there is probably more cohesion), it
> >>> seems a little rudderless in terms of direction. Feel free to flame me
> at
> >>> this point lovely community people.
> >>>
> >>> Regards
> >>>
> >>> Tom
> >>>
> >>>
> >>
> >>
> >
> > --
> > *Tom Barber* | Technical Director
> >
> > meteorite bi
> > *T:* +44 20 8133 3730
> > *W:* www.meteorite.bi | *Skype:* meteorite.consulting
> > *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG,
> UK
> >
>
>
>
> --
> *Lewis*
>
Re: Filemgr Tests
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Reversed Tom.
On Mon, Jul 21, 2014 at 4:49 AM, Tom Barber <to...@meteorite.bi> wrote:
> Hows the stew? ;)
>
>
> On 19/07/14 00:33, Lewis John Mcgibbney wrote:
>
>> I'm going to let this stew over the weekend and come up with some comments
>> of my own Tom.
>> There is a LOT for discussion.
>>
>>
>> On Fri, Jul 18, 2014 at 5:21 PM, Tom Barber <to...@meteorite.bi>
>> wrote:
>>
>> Hello OODT Development Team
>>>
>>> I was wondering if
>>> a) it would make sense for us to either have a call at some point, or
>>> just
>>> get a thread/jira started that allows us to get a rough idea of what
>>> aspects of OODT people are working on, what they need etc as currently I
>>> don't think many of us have a real clue
>>> b) On the new website, would it be worth publishing a "roadmap" cause, I
>>> have no clue where the project is going
>>> c) Are there any better ways of sorting out, planning, roadmaps,
>>> meetings,
>>> community stuff, and collaboration on tasks, that we can take from other
>>> Apache projects, because, whilst I enjoy OODT, and the ideas behind it
>>> (and
>>> I appreciate within the NASA bunch there is probably more cohesion), it
>>> seems a little rudderless in terms of direction. Feel free to flame me at
>>> this point lovely community people.
>>>
>>> Regards
>>>
>>> Tom
>>>
>>>
>>
>>
>
> --
> *Tom Barber* | Technical Director
>
> meteorite bi
> *T:* +44 20 8133 3730
> *W:* www.meteorite.bi | *Skype:* meteorite.consulting
> *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG, UK
>
--
*Lewis*
Re: Filemgr Tests
Posted by Tom Barber <to...@meteorite.bi>.
Hows the stew? ;)
On 19/07/14 00:33, Lewis John Mcgibbney wrote:
> I'm going to let this stew over the weekend and come up with some comments
> of my own Tom.
> There is a LOT for discussion.
>
>
> On Fri, Jul 18, 2014 at 5:21 PM, Tom Barber <to...@meteorite.bi> wrote:
>
>> Hello OODT Development Team
>>
>> I was wondering if
>> a) it would make sense for us to either have a call at some point, or just
>> get a thread/jira started that allows us to get a rough idea of what
>> aspects of OODT people are working on, what they need etc as currently I
>> don't think many of us have a real clue
>> b) On the new website, would it be worth publishing a "roadmap" cause, I
>> have no clue where the project is going
>> c) Are there any better ways of sorting out, planning, roadmaps, meetings,
>> community stuff, and collaboration on tasks, that we can take from other
>> Apache projects, because, whilst I enjoy OODT, and the ideas behind it (and
>> I appreciate within the NASA bunch there is probably more cohesion), it
>> seems a little rudderless in terms of direction. Feel free to flame me at
>> this point lovely community people.
>>
>> Regards
>>
>> Tom
>>
>
>
--
*Tom Barber* | Technical Director
meteorite bi
*T:* +44 20 8133 3730
*W:* www.meteorite.bi | *Skype:* meteorite.consulting
*A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG, UK
Re: Filemgr Tests
Posted by Lewis John Mcgibbney <le...@gmail.com>.
I'm going to let this stew over the weekend and come up with some comments
of my own Tom.
There is a LOT for discussion.
On Fri, Jul 18, 2014 at 5:21 PM, Tom Barber <to...@meteorite.bi> wrote:
> Hello OODT Development Team
>
> I was wondering if
> a) it would make sense for us to either have a call at some point, or just
> get a thread/jira started that allows us to get a rough idea of what
> aspects of OODT people are working on, what they need etc as currently I
> don't think many of us have a real clue
> b) On the new website, would it be worth publishing a "roadmap" cause, I
> have no clue where the project is going
> c) Are there any better ways of sorting out, planning, roadmaps, meetings,
> community stuff, and collaboration on tasks, that we can take from other
> Apache projects, because, whilst I enjoy OODT, and the ideas behind it (and
> I appreciate within the NASA bunch there is probably more cohesion), it
> seems a little rudderless in terms of direction. Feel free to flame me at
> this point lovely community people.
>
> Regards
>
> Tom
>
--
*Lewis*
Re: Filemgr Tests
Posted by Tom Barber <to...@meteorite.bi>.
Hello OODT Development Team
I was wondering if
a) it would make sense for us to either have a call at some point, or
just get a thread/jira started that allows us to get a rough idea of
what aspects of OODT people are working on, what they need etc as
currently I don't think many of us have a real clue
b) On the new website, would it be worth publishing a "roadmap" cause, I
have no clue where the project is going
c) Are there any better ways of sorting out, planning, roadmaps,
meetings, community stuff, and collaboration on tasks, that we can take
from other Apache projects, because, whilst I enjoy OODT, and the ideas
behind it (and I appreciate within the NASA bunch there is probably more
cohesion), it seems a little rudderless in terms of direction. Feel free
to flame me at this point lovely community people.
Regards
Tom
Re: Filemgr Tests
Posted by Tom Barber <to...@meteorite.bi>.
Hey Lewis,
I know that may have come across like a gripe at you, it certainly
wasn't, just a general moan about the state of the test suite :)
I certainly like anything that feeds back to users regarding commits
either blame emails, jira comments, flashing red hazard lights, you know
the usual :)
Hopefully now I have a few weeks of hacking time until baby number 2
(then I may have even more if it keeps me awake all night ;) ), I know
you've put a lot of effort into the f******g tests and I don't know what
state of repair they are in, but if I can help out with getting them
running let me know.
Regards
Tom
On 18/07/14 12:46, Lewis John Mcgibbney wrote:
> Hi Tom,
> To be honest I've no idea when filemgr (or more generally OODT) tests
> broke... it's been a good while now and we keep the last 50 builds so the
> exact date is most likely deep into the event horizonby now.
> Anyway's, I agree with your comments. It is only fair for us to keep the
> codebase _stable_. Unstable commits should most likely be reverted ASAP.
> What I like about OODT though is that review board is heavily in use.
> I should also mention that we *may* wish to set up a pre-commit test
> configuration where a bot will take our patch on Jira and run a build on
> Jenkins then post a comment to the Jenkins issue telling us whether the
> patch meets certain criteria, etc. If you want to do this then I can maybe
> look into it.
> Apart from that I am still butchering the filemgr tests little by little
> and will have a review board up soon. I also may get hit by a bus soon, or
> get sucked down the plug hole in my hotel room bath. ;)
> Lewis
>
>
>
> On Fri, Jul 18, 2014 at 3:53 AM, Tom Barber(Alabs) <to...@analytical-labs.com>
> wrote:
>
>> Shifted some development wishes from private@ to dev@ for Chris ;)
>>
>> Na I'm only messing, but I do think more care should be taken with commits
>> vs the test suite because I would like to do the Tika upgrade, fix the
>> database dialects etc, but I only feel comfortable hacking around with that
>> stuff if we know the tests work because I don't know enough about the
>> feature set of the components that I've not used and as such rely on the
>> tests to tell me what I've borked or not.
>>
>> Equally should I break a test I'd expect my commits to be reverted and I'd
>> be asked to fix them before recommitting instead of just putting up with
>> broken tests.
>>
>> Lets make it so! ;)
>>
>> Tom
>>
>
>
--
*Tom Barber* | Technical Director
meteorite bi
*T:* +44 20 8133 3730
*W:* www.meteorite.bi | *Skype:* meteorite.consulting
*A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG, UK
Re: Filemgr Tests
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi Tom,
To be honest I've no idea when filemgr (or more generally OODT) tests
broke... it's been a good while now and we keep the last 50 builds so the
exact date is most likely deep into the event horizonby now.
Anyway's, I agree with your comments. It is only fair for us to keep the
codebase _stable_. Unstable commits should most likely be reverted ASAP.
What I like about OODT though is that review board is heavily in use.
I should also mention that we *may* wish to set up a pre-commit test
configuration where a bot will take our patch on Jira and run a build on
Jenkins then post a comment to the Jenkins issue telling us whether the
patch meets certain criteria, etc. If you want to do this then I can maybe
look into it.
Apart from that I am still butchering the filemgr tests little by little
and will have a review board up soon. I also may get hit by a bus soon, or
get sucked down the plug hole in my hotel room bath. ;)
Lewis
On Fri, Jul 18, 2014 at 3:53 AM, Tom Barber(Alabs) <to...@analytical-labs.com>
wrote:
> Shifted some development wishes from private@ to dev@ for Chris ;)
>
> Na I'm only messing, but I do think more care should be taken with commits
> vs the test suite because I would like to do the Tika upgrade, fix the
> database dialects etc, but I only feel comfortable hacking around with that
> stuff if we know the tests work because I don't know enough about the
> feature set of the components that I've not used and as such rely on the
> tests to tell me what I've borked or not.
>
> Equally should I break a test I'd expect my commits to be reverted and I'd
> be asked to fix them before recommitting instead of just putting up with
> broken tests.
>
> Lets make it so! ;)
>
> Tom
>
--
*Lewis*