nunit-dev team mailing list archive

["Justin Daubenmire" <jdaubenmire@xxxxxxxxx>]

Hi Charlie,

Pardon my ignorance - I've never used lp. How do we check out the source 
code from lp?

when you mention cvs for source control, do you mean subversion?

/Justin

----- Original Message ----- 
From: "Charlie Poole" <charlie@xxxxxxxxx>
To: <nunit-dev@xxxxxxxxxxxxxxxxxxx>
Sent: Friday, July 10, 2009 10:44 PM
Subject: Re: [Nunit-dev] What should we do about lp:nunit-2.5?


> I have removed the branch from Launchpad. We'll just
> move on to NUnit 3.0.
>
> Charlie
>
> > -----Original Message-----
> > From: nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxxx
> > [mailto:nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxx
> > t] On Behalf Of Charlie Poole
> > Sent: Wednesday, July 08, 2009 5:30 PM
> > To: nunit-dev@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Nunit-dev] What should we do about lp:nunit-2.5?
> >
> > I have confirmation that the bug blocking our imports to
> > Launchpad will not be fixed. I plan to delete the mirror of
> > NUnit 2.5 in the next day or two.
> >
> > Charlie
> >
> > > -----Original Message-----
> > > From: nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxxx
> > > [mailto:nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxx
> > > t] On Behalf Of Charlie Poole
> > > Sent: Tuesday, July 07, 2009 3:06 PM
> > > To: nunit-dev@xxxxxxxxxxxxxxxxxxx
> > > Subject: [Nunit-dev] What should we do about lp:nunit-2.5?
> > >
> > > Hi All,
> > >
> > > The nunit 2.5 mirror on launchpad can no longer be updated.
> > I merged
> > > changes from the 2.5 branch to head so that they would be available
> > > for import to launchpad but ran into a bug in the
> > conversion program
> > > which makes it impossible to import a cvs project which has
> > added any
> > > files to head as the result of a merge. The bug is two
> > years old, so
> > > it doesn't seem likely that it will be fixed.
> > >
> > > I don't want to leave it up as it is, because that
> > encourages people
> > > to branch from old code. That seems to leave two options,
> > at least as
> > > far as I can see...
> > >
> > > 1. Delete the NUnit 2.5 project on Launchpad and just fix bugs as
> > > needed through cvs.
> > >
> > > 2. Delete the branch - but not the project - and start a
> > new branch on
> > > launchpad without the cvs history. Continue to fix bugs on
> > launchpad
> > > until there is a new release.
> > >
> > > I lean toward #1 myself, since I see no reason to make it
> > especially
> > > easy for folks to extend 2.5 - I'd rather see the effort go toward
> > > 3.0.
> > >
> > > What do others think?
> > >
> > > Charlie
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Mailing list: https://launchpad.net/~nunit-dev
> > > Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
> > > Unsubscribe : https://launchpad.net/~nunit-dev
> > > More help   : https://help.launchpad.net/ListHelp
> > >
> >
> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~nunit-dev
> > Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~nunit-dev
> > More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~nunit-dev
> Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~nunit-dev
> More help   : https://help.launchpad.net/ListHelp