Re: [Tikiwiki-devel] Troubles at tikiwiki.org + 1.8 stabilization problems

[Jan D. <jan...@ti...>]

Yes,

I agree too.
A release candidate should be feature frozen and if it passes testing it wi=
ll=20
become a release. Adding features to a release candidate should be extremel=
y=20
rare, that is new features are added only if it makes other features=20
completery unusable or if there are security problems.

Tiki has grown rather large and, with many developpers and more project=20
dicipline is needed in order to achive one of Tiki's goals (super stable). =
I=20
think it is a mistake to wait with setting up a good release process unitil=
l=20
all features are there, since then people involved with the project will gr=
ow=20
bad habits.

One sugestion for a better realse process is:

1. Decide which features will be in an realease.
2 Once they are implemented and is in a state that it is time for an releas=
e=20
candidate (this may be decided in some other way), make a release branch on=
=20
wich all bugfixing for that relase happens. (e.g RC1, RC2  release; 1.x.0,=
=20
pathches: 1.x.1, etc). During this period new features may be added on the=
=20
main branch.

Right now it feels that 1.x.y version works as release candidates - which m=
ay=20
scare new users.

Also the page named Relse process 1.x on tw.org is in my oppinon not an rel=
ase=20
procesess but a relase plan for a specific vers (i..e wich features goes in=
,=20
which bugs _must_ be corrected and which bugs will not be corrected.

A relase process is something more the two points I describes above (but mo=
re=20
details wrt. what goes where in CVS test process etc.

Otherwise i think Tiki is a great product (i use it)

I hope this post will help the TE project. If you have questions or objecti=
ons=20
do nothesitate to contact me,

Best regards - Jan

=2D-=20
Jan Docekal
Bysmedjev=E4gen 18
233 91 Svedala
040-48 32 18, 0709-633 673
jan...@ti..., jan...@ne...
www.neonchart.com

On Sunday 30 November 2003 03:38, Oliver Hertel wrote:
> On 29 Nov 2003 at 19:24, Philippe Cloutier wrote:
> > 1.8 Stabilization problems
> > I'm not talking about something new here, but many user (and also devs!)
> > currently feel frustrated about its instability. Remember, it is named
> > "Release Candidate 2"...
>
> I already said that it is bad that we still implement features in RC
> versions.
>
> Lots of people complain about tiki releases being somewhat 'incomplete' a=
nd
> developers going on implementing even MORE things in next release instead
> of fixing old bugs / instabilities first.
>
>
> Bye,
>
> Oliver
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Tikiwiki-devel mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel