--- Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> I also would prefer to wait a bit to create the
> ANT_17_BRANCH.
> 
> For Ant 1.8, I have in mind some refactoring, like
> maybe splitting the source tree per jar.
> Documentation could also be split by theme such as
> property tasks, resource based tasks, SCM tasks
> rather than the current distinction core/optional
> which is not so nice.

While we're on the subject, note that in Java6,
<script> is no longer an optional task.  ;)

-Matt

> 
> If such refactoring happens, merging changes between
> two source trees which look different is a pain.
> 
> Regards,
> 
> Antoine
> -------- Original-Nachricht --------
> Datum: Fri, 22 Dec 2006 22:05:12 +0100
> Von: Martijn Kruithof <[EMAIL PROTECTED]>
> An: Ant Developers List <dev@ant.apache.org>
> Betreff: Re: Branch
> 
> > Matt Benson schreef:
> > > --- Martijn Kruithof <[EMAIL PROTECTED]>
> wrote:
> > >
> > >   
> > >> Have we already created an ANT_17_BRANCH?
> > >>     
> > >
> > > Not that I know of.  We did pretty well
> restraining
> > > ourselves from committing to HEAD just before
> the
> > > release.  :)  Should we wait on branching until
> nearer
> > > to 1.7.1, or until we know we want to put
> something in
> > > that should be for 1.8?
> > >
> > > -Matt
> > >
> > >   
> > I think we should create a branch as soon as the
> 1.7 "version series" 
> > stabilizes. (and only make things public that
> should be in 1.8 after the 
> > 1.7 series has become oficially stable)
> > 
> > Martijn
> > >>     
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to