I have nothing against, only I wanted to warn these decisions for the
future.

In my opinion you should do following scenario:
Major version - new features, changes in used technology
Minor versions - stabilizing the new features, tweaking them
minor subversions - bugfixies

I even call for releasing patches at the time the patch is released like
in following scenario:

Release 2.6.1
-patch 1
-patch 2
-patch 3

release 2.6.2 which is 2.6.1 + all released patches and possible small
changes bringing minor features

I even believe, that 2.7 is useless if you plan 3.0 in a month and I
disagree we should release new version that removes php5 unless you have
a very important reason.
Why simply not let people live with bugfixies following 30 days and then
offer them 3.0? Do you plan to keep two branches simultaneously?

Ondra

Paul Baranowski píše v út 10. 10. 2006 v 12:33 -0400:
> I just want to confirm that Campsite 2.7 is going to require PHP5. I
> will assume this is the case unless someone says otherwise.
>
> - Paul

In that case you confuse all users. Do not release 2.7 at all and simply
insert it to the radiopackage. Or call it campsite-radiopackage-1.0.
simply call it differently, so that users know, that "this campsite is
not ment to be used by standard newspapers".

Ondra

Paul Baranowski píše v út 10. 10. 2006 v 13:38 -0400:
> Campsite 2.7 and 3.0 are different than previous releases - 2.7 will not
> be officially supported, while 3.0 will be. You can think of this in a
> similar way to Ubuntu releasing Dapper, a long-term supported release,
> and then doing Edgy, a more experimental version.
>
> The target audience for Campsite 2.7 is the Radio Package people and it
> is not meant for general use. We had to do it in this way in order to
> meet the deadline.
>
> - Paul
>
>
> Ondra Koutek wrote:
> > I have nothing against, only I wanted to warn these decisions for the
> > future.
> >
> > In my opinion you should do following scenario:
> > Major version - new features, changes in used technology
> > Minor versions - stabilizing the new features, tweaking them
> > minor subversions - bugfixies
> >
> > I even call for releasing patches at the time the patch is released like
> > in following scenario:
> >
> > Release 2.6.1
> > -patch 1
> > -patch 2
> > -patch 3
> >
> > release 2.6.2 which is 2.6.1 + all released patches and possible small
> > changes bringing minor features
> >
> > I even believe, that 2.7 is useless if you plan 3.0 in a month and I
> > disagree we should release new version that removes php5 unless you have
> > a very important reason.
> > Why simply not let people live with bugfixies following 30 days and then
> > offer them 3.0? Do you plan to keep two branches simultaneously?
> >
> > Ondra
> >
> > Paul Baranowski píše v út 10. 10. 2006 v 12:33 -0400:
> >> I just want to confirm that Campsite 2.7 is going to require PHP5. I
> >> will assume this is the case unless someone says otherwise.
> >>
> >> - Paul
> >
> >