List Info

Thread: Planning MonoDevelop 1.0




Planning MonoDevelop 1.0
user name
2006-11-25 17:55:14
Yea, i think we really should look into this before 1.0.

On 11/25/06, Charlie Poole <charliepooleconsulting.com>
wrote:
> Hi Christian,
>
> Not sure if you intended this to be offline - you can
put us back
> on the list if you like.
>
> Bundling would be OK with me, although we may want to
think about
> how it impacts some of the distros. One thing I want to
do is
> speed up the access to new versions of NUnit on
different platforms
> by making packages available.
>
> Ideally - and this is really blue-sky stuff - MD would
find and
> hook up with whatever version of NUnit is present. I
think that
> we would have to provide some sort of shim assembly for
that
> to work.
>
> Charlie
>
> > -----Original Message-----
> > From: Christian Hergert
[mailto:christian.hergertgmail.com]
> > Sent: Friday, November 24, 2006 5:13 PM
> > To: Charlie Poole
> > Subject: Re: [MonoDevelop] Planning MonoDevelop
1.0
> >
> > can we start bundling nunit? its getting really
anoying
> > already when things dont compile. as it is on edgy
i just
> > --enable-nunit=no while working on the codebase.
> >
> > -- Christian
> >
> > On 11/24/06, Charlie Poole <charliepooleconsulting.com> wrote:
> > > Hi ALl,
> > >
> > > > -----Original Message-----
> > > > From: monodevelop-list-bounceslists.ximian.com
> > > > [mailto:monodevelop-list-bounceslists.ximian.com] On Behalf Of
> > > > Lluis Sanchez
> > > > Sent: Wednesday, November 22, 2006 3:29
PM
> > > > To: monodevelop-listlists.ximian.com
> > > > Subject: [MonoDevelop] Planning
MonoDevelop 1.0
> > >
> > > <snip/>
> > >
> > > >       * NUnit: It can be considered
feature complete for
> > 1.0. The only
> > > >         missing issue to resolve is what
to do with the NUnit
> > > >         dependency. Right now the add-in
can't be built
> > with recent
> > > >         NUnit versions since they have
breaking changes. I talked
> > > > about
> > > >         this with Charlie Poole in the
Mono summit and he
> > suggested to
> > > >         embed the most recent NUnit dlls
into the add-in,
> > since even
> > > > if
> > > >         the API has some breaking
changes, new NUnit versions can
> > > > still
> > > >         run tests written for all the
previous versions.
> > >
> > > For development purposes, I suggest moving to
the NUnit 2.4
> > Beta code.
> > > There are interface differences between 2.0
and 2.2.8 and further
> > > changes from 2.2.8 to 2.4. The 2.4 TestRunner
interface could still
> > > change a little, but only in the direction of
simplification.
> > >
> > > Charlie
> > >
> > >
> > >
_______________________________________________
> > > Monodevelop-list mailing list
> > > Monodevelop-listlists.ximian.com
> > > http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
> > >
> >
>
>
>
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
Planning MonoDevelop 1.0
user name
2006-11-25 18:23:57
Well, fortunately, my time frame for NUnit 2.4 is ahead of
the
timeframe for MD 1.0. I hope to have a Beta 3 release out in
a
week or so. After that, I want to freeze it functionally and
just work out any bugs. Production release should be by year
end.

Charlie

> -----Original Message-----
> From: Christian Hergert [mailto:christian.hergertgmail.com] 
> Sent: Saturday, November 25, 2006 9:55 AM
> To: Charlie Poole
> Cc: monodevelop
> Subject: Re: [MonoDevelop] Planning MonoDevelop 1.0
> 
> Yea, i think we really should look into this before
1.0.
> 
> On 11/25/06, Charlie Poole <charliepooleconsulting.com> wrote:
> > Hi Christian,
> >
> > Not sure if you intended this to be offline - you
can put 
> us back on 
> > the list if you like.
> >
> > Bundling would be OK with me, although we may want
to think 
> about how 
> > it impacts some of the distros. One thing I want
to do is 
> speed up the 
> > access to new versions of NUnit on different
platforms by making 
> > packages available.
> >
> > Ideally - and this is really blue-sky stuff - MD
would find 
> and hook 
> > up with whatever version of NUnit is present. I
think that we would 
> > have to provide some sort of shim assembly for
that to work.
> >
> > Charlie
> >
> > > -----Original Message-----
> > > From: Christian Hergert
[mailto:christian.hergertgmail.com]
> > > Sent: Friday, November 24, 2006 5:13 PM
> > > To: Charlie Poole
> > > Subject: Re: [MonoDevelop] Planning
MonoDevelop 1.0
> > >
> > > can we start bundling nunit? its getting
really anoying 
> already when 
> > > things dont compile. as it is on edgy i just 
> --enable-nunit=no while 
> > > working on the codebase.
> > >
> > > -- Christian
> > >
> > > On 11/24/06, Charlie Poole <charliepooleconsulting.com> wrote:
> > > > Hi ALl,
> > > >
> > > > > -----Original Message-----
> > > > > From: monodevelop-list-bounceslists.ximian.com
> > > > >
[mailto:monodevelop-list-bounceslists.ximian.com] On 
> Behalf Of 
> > > > > Lluis Sanchez
> > > > > Sent: Wednesday, November 22, 2006
3:29 PM
> > > > > To: monodevelop-listlists.ximian.com
> > > > > Subject: [MonoDevelop] Planning
MonoDevelop 1.0
> > > >
> > > > <snip/>
> > > >
> > > > >       * NUnit: It can be considered
feature complete for
> > > 1.0. The only
> > > > >         missing issue to resolve is
what to do with the NUnit
> > > > >         dependency. Right now the
add-in can't be built
> > > with recent
> > > > >         NUnit versions since they
have breaking changes. I 
> > > > > talked about
> > > > >         this with Charlie Poole in
the Mono summit and he
> > > suggested to
> > > > >         embed the most recent NUnit
dlls into the add-in,
> > > since even
> > > > > if
> > > > >         the API has some breaking
changes, new NUnit versions 
> > > > > can still
> > > > >         run tests written for all
the previous versions.
> > > >
> > > > For development purposes, I suggest
moving to the NUnit 2.4
> > > Beta code.
> > > > There are interface differences between
2.0 and 2.2.8 
> and further 
> > > > changes from 2.2.8 to 2.4. The 2.4
TestRunner interface could 
> > > > still change a little, but only in the
direction of 
> simplification.
> > > >
> > > > Charlie
> > > >
> > > >
> > > >
_______________________________________________
> > > > Monodevelop-list mailing list
> > > > Monodevelop-listlists.ximian.com
> > > > http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
> > > >
> > >
> >
> >
> >
> 


_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )