[Kstars-devel] KDE feature freeze

[Jason Harris]

Hi Akarsh,

On Wednesday 01 August 2007 11:23, Akarsh Simha wrote:
> Hi Jason.
>
> I can handle some simple testing / debugging.
>
Thanks, that would be great.

> I don't know much about the manual.
>
> By the way, me being new to development, can you tell me what the "trunk"
> is and what "message-frozen" and "feature-frozen" mean?
>
"trunk" is the main branch of development in the SVN repository; it is the 
codebase that will eventually be tagged and released as KDE-4.0.  
"feature-frozen" simply means that no new features can be committed to trunk, 
only bugfixes.  Trunk is frozen in order to ensure that developers spend time 
fixing and optimizing their code prior to a release, so that the release is 
stable and polished.  When trunk is "message-frozen" on Aug. 20th, it means 
that no user-visible strings can be changed anymore, except to fix typos or 
other problems.  This is done in order to give the 40+ translation teams time 
to localize all of KDE into their language, without having to work against a 
moving target.

See the KDE-4.0 release schedule here:
http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule

We can create branches in which feature development can continue while trunk 
is frozen (e.g., James's kdeedu_kstars_htm branch).  However, I would rather 
we concentrate on fixing/polishing kstars in trunk.

HTH,
Jason

> Thanks.
>
> On 8/1/07, Jason Harris <kstars at 30doradus.org> wrote:
> > Hello,
> >
> > As you may know, KDE4.0-beta1 is currently being tagged in preparation
> > for release.  This means that trunk is now feature-frozen, and it will be
> > message-frozen on August 20th.
> >
> > So, no more feature commits in trunk until after KDE4.0 is released.  I
> > had
> > some things I had wanted to add for 4.0, but I simply didn't have time to
> > work on KStars at all the past several weeks. :(
> >
> > Time to work on bugfixing and optimization for 4.0.  I could really use
> > help
> > with this; is anyone available?  Even simply testing the program to
> > identify
> > problems would be a big help.  At some point we'll need to write our
> > usual QA
> > list of KStars expected behaviors, and test each of them.
> >
> > Since we can still change strings until Aug 20th, it would be a good idea
> > to
> > go through the manual to make sure everything there is up to date. 
> > Anyone want to volunteer for this?
> >
> > thanks,
> > Jason
> >
> > --
> > KStars: KDE Desktop Planetarium
> > kstars at 30doradus.org
> > _______________________________________________
> > Kstars-devel mailing list
> > Kstars-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/kstars-devel

-- 
Jason Harris
jharris at 30doradus.org