[CP2K:508] Re: cp2k release goals

[Teodoro Laino]

Hi Axel,

Good Idea! I like that and it should be quite easy to implement at  
the parsing level.
Let me work on that and will be back to you. This would be anyway the  
very first step
towards a systematic release planning (i.e. decide all together what  
to have or not
in the release). And it would also make more automatic for the future  
when planning a new release (i.e.
when there's a certain number of keywords/sections upgraded from  
unsupported to supported)..
yep.. I really like it!!

teo

On 5 Jan 2008, at 22:31, Axel wrote:

> as written before, the most important decision would be to
> identify features, that should be labeled as supported. i would
> recommend to not remove anything from the release version, but
> rather add a flag to check clear supported features. the input could
> have a keyword (in &GLOBAL) ENABLE_UNSUPPORTED_FEATURES which
> would be set to false by default in releases and true in developement
> versions. that would make maintenance easier and every developer of
> a subsystem can decide on a fine grained level whether a feature
> is production ready or not.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cp2k.org/archives/cp2k-user/attachments/20080105/5af02bb0/attachment.htm>