phpgroupware-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Phpgroupware-developers] Release planning (was XSLT-version)


From: Dave Hall
Subject: RE: [Phpgroupware-developers] Release planning (was XSLT-version)
Date: Fri, 15 Oct 2004 22:05:20 +1000

On Thu, 2004-10-14 at 23:40, Brian Johnson wrote:
> So your in favour of making .16 into HEAD and progressing from there for .18?
> (of course we should save the HEAD code in a separate branch while we scavenge
> code from it that we intend to keep
> 
> Could you please review and comment to this list on the outline at
> http://wiki.phpgroupware.org/index.php?page=release_plan (I've stuck in a
> bunch of tracking tickets to give people an idea of what could be included ..
> do we need to be that specific?)

I have just something quick to say about what is currently in the wiki.

1.0RC1 should be 0.9.18.001.  Nothing new should go into the 1.0 branch.

> 
> 
> Christian Boettger - Mailings (address@hidden) wrote:
> >
> > Hi,
> >
> > > From: Brian Johnson [mailto:address@hidden
> > > Sent: Thursday, October 14, 2004 2:38 PM
> > > To: address@hidden
> > > Subject: RE: [Phpgroupware-developers] Release planning (was
> > > XSLT-version)
> > >
> > >
> > > I think that if pb has stuff to contribute, then great!!  But
> > > it needs to be submitted unless they are committing it themselves.
> >
> > well:
> > 0.9.16 is feature-frozen, which is OK. This includes a ban on any database
> > change (if if it's more a bugfix than a feature).
> >
> > So we can't possibly submit anything to 0.9.16 or even commit ourselves.
> >
> > HEAD is not in a working state, worse: it's in an undefined state. So we
> > can't really commit anything there which is based on 0.9.16 code (which is
> > newer than HEAD code).
> >
> > So we don't really have a target to commit into.
> >
> > We would urgently need a real development branch, where developments based
> > on 0.9.16 can be submitted to. Obviously, everything worth salvaging from
> > the current HEAD should be included there as well.
> >
> > > In general I think that any contribution that does not
> > > greatly change the function of an app should be accepted.  Any greater
> > change
> > > should be discussed on the dev list first.
> >
> > at the moment, there is a strict feature freeze for 0.9.16, may it be minor
> > or major changes. And this is OK, otherwise this version will still be
> > called 0.9.16 in ten years time...
> >
> > > Can we establish written rules for committing changes?
> >
> > not really, I'm afraid.
> >
> > Regards
> >
> > CB aka bofh42
> >
> > 30539 Hannover
> > Tel.: 05 11 / 6 00 66-331
> > Fax: 05 11 / 6 00 66 -355
> >
> > e-mail: address@hidden
> > Internet: http://www.probusiness.de/
> > Online Demos auf http://www.pbdemo.de/
> >
> > *****    Open Source und Linux im professionellen Einsatz    *****
> > **  komplexe Mailserver, Groupware, Office: sprechen Sie uns an **
> >
> >
> > *********************************************************
> > Wir freuen uns auf Ihren Besuch:
> >     SYSTEMS 2004: probusiness in Halle B3, Stand 345
> >     LinuxWorld 2004: probusiness in Halle 4, Stand B06
> >
> > Besuchen Sie ausserdem unsere Technologietage
> > am 05.10./07.10./21.10.04 in Hannover, Dresden und Berlin
> > *********************************************************
> >
> >
> >
> >
> > _______________________________________________
> > Phpgroupware-developers mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
> >
> >
> 
> 
> 
> _______________________________________________
> Phpgroupware-developers mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
-- 
Dave Hall
Dave Hall Consulting
p +61 3 9754 5276
m +61 410 47 42 55
f +61 3 8610 0029
e address@hidden
-- 
Dave Hall (aka skwashd)
API Coordinator
phpGroupWare





reply via email to

[Prev in Thread] Current Thread [Next in Thread]