lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy" <digyd...@gmail.com>
Subject RE: svn commit: r1072121 - /incubator/lucene.net/branches/vs2010/
Date Fri, 18 Feb 2011 22:10:25 GMT
What I meant was a binary release.
DIGY.

-----Original Message-----
From: Sergey Mirvoda [mailto:sergey@mirvoda.com] 
Sent: Saturday, February 19, 2011 12:02 AM
To: lucene-net-dev@lucene.apache.org
Subject: Re: svn commit: r1072121 - /incubator/lucene.net/branches/vs2010/

4.0 rules them all. You can release 2.0 3.5 and 4.0 versions with 4.0
multitargeting

On Sat, Feb 19, 2011 at 2:59 AM, Digy <digydigy@gmail.com> wrote:

> Why not having a release targeting 2.0, 3.5 and 4.0, then updating the
> project to 4.0
> DIGY
>
> -----Original Message-----
> From: Sergey Mirvoda [mailto:sergey@mirvoda.com]
> Sent: Friday, February 18, 2011 11:56 PM
> To: lucene-net-dev@lucene.apache.org
> Subject: Re: svn commit: r1072121 - /incubator/lucene.net/branches/vs2010/
>
> Why with 2.0 and not with 4.0 targeting 2.0?
>
> On Sat, Feb 19, 2011 at 2:54 AM, Wyatt Barnett
> <wyatt.barnett@gmail.com>wrote:
>
> > For folks who badly need to compile it, why not just add a batch file
> > to build the project. It is one line:
> >
> > %windir%\Microsoft.NET\Framework\v2.0.50727\msbuild lucene.net.csproj
> > /t:Clean;Rebuild /p:Configuration=Release
> >
> > On Fri, Feb 18, 2011 at 4:38 PM, Troy Howard <thoward37@gmail.com>
> wrote:
> > > It's a common practice for developers to create a branch to work on a
> > > new feature, then merge that branch back into trunk later when the
> > > changes are complete, then delete the branch.
> > >
> > > The goal is to ensure that incremental commits, performed now against
> > > the branch instead of trunk, don't leave trunk in a incompatible,
> > > unstable or un-buildable state.
> > >
> > > Perhaps that's Prescott's intention with the new vs2010 branch?
> > >
> > > Thanks,
> > > Troy
> > >
> > >
> > > On Fri, Feb 18, 2011 at 1:31 PM, Sergey Mirvoda <sergey@mirvoda.com>
> > wrote:
> > >> +1 for only one trunk upgraded to VS2010
> > >>
> > >> On Sat, Feb 19, 2011 at 2:27 AM, Lombard, Scott <
> > slombard@kingindustries.com
> > >>> wrote:
> > >>
> > >>> I agree with DIGY.
> > >>>
> > >>> Although why wait until after the official release?
> > >>>
> > >>> Scott
> > >>>
> > >>>
> > >>>
> > >>> -----Original Message-----
> > >>> From: Digy [mailto:digydigy@gmail.com]
> > >>> Sent: Friday, February 18, 2011 3:38 PM
> > >>> To: lucene-net-dev@lucene.apache.org
> > >>> Subject: RE: svn commit: r1072121 - /incubator/
> > lucene.net/branches/vs2010/
> > >>>
> > >>> Do we really need a VS2010 branch?. Since there isn't any release
> since
> > >>> v2.0 and people have to compile the source by yourselves it has been
> > good to
> > >>> support older versions of VS. But after having an offical release,
we
> > could
> > >>> update the trunk to support VS2010.
> > >>>
> > >>> Now for each change in trunk (for v2.9.3, 2.9.4 & 2.9.5) we have
to
> > update
> > >>> another repository also.
> > >>>
> > >>> DIGY
> > >>>
> > >>> -----Original Message-----
> > >>> From: pnasser@apache.org [mailto:pnasser@apache.org]
> > >>> Sent: Friday, February 18, 2011 10:11 PM
> > >>> To: lucene-net-commits@lucene.apache.org
> > >>> Subject: svn commit: r1072121 - /incubator/
> lucene.net/branches/vs2010/
> > >>>
> > >>> Author: pnasser
> > >>> Date: Fri Feb 18 20:10:54 2011
> > >>> New Revision: 1072121
> > >>>
> > >>> URL: http://svn.apache.org/viewvc?rev=1072121&view=rev
> > >>> Log: (empty)
> > >>>
> > >>> Added:
> > >>>    incubator/lucene.net/branches/vs2010/
> > >>>      - copied from r1069573, incubator/lucene.net/trunk/
> > >>>
> > >>>
> > >>>
> > >>> This message (and any associated files) is intended only for the
> > >>> use of the individual or entity to which it is addressed and may
> > >>> contain information that is confidential, subject to copyright or
> > >>> constitutes a trade secret. If you are not the intended recipient
> > >>> you are hereby notified that any dissemination, copying or
> > >>> distribution of this message, or files associated with this message,
> > >>> is strictly prohibited. If you have received this message in error,
> > >>> please notify us immediately by replying to the message and deleting
> > >>> it from your computer.  Thank you, King Industries, Inc.
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> --Regards, Sergey Mirvoda
> > >>
> > >
> >
>
>
>
> --
> --Regards, Sergey Mirvoda
>
>


-- 
--Regards, Sergey Mirvoda


Mime
View raw message