Howdy, The more detail the better. I much prefer seeing more detail, because it is actually useful for people that want to know the specifics of how Parrot is progressing.
"Various bugfixes and updates" is so worthlessly ambiguous that we might as well not say it. I have spent time adding to the list of tests that have been translated and I was going to make it complete and now it seems that it is not wanted. That frustrates me. We do a lot of work between releases. Our NEWS file should reflect that. Duke On Mon, Dec 14, 2009 at 8:41 AM, jerry gay <[email protected]> wrote: > On Mon, Dec 14, 2009 at 08:12, Richard Hainsworth <[email protected]> > wrote: >> Gerd Pokorra wrote: >>> >>> Hi, >>> >>> Parrot 1.9.0 (Blue-fronted Amazon) is due to be released on Tuesday, >>> December 15th. >>> >> >> <snip> >>> >>> + investigate gc >>> >>> >> >> Seems odd to add what the developers are doing to news about a release. Also >> gc means a lot to Parrot people, but how much to someone with a more casual >> interest. >> >> Maybe a note at the end of the announcement about the location of the >> strategy and milestones would cover the gc point and more. >> > i've modified NEWS so it now reads: > > New in 1.9.0 > - Core > + Converted Contexts to garbage collectable structures > + Made profiling runcore output format configurable and extensible > options include "pprof" and "none" ("binary" and "callgrind" are planned) > + Added environment variables to specify profiling output type and filename > (PARROT_PROFILING_OUTPUT and PARROT_PROFILING_FILENAME) > + Began merging Freeze/Thaw and Bytecode generator/loader > - Compilers > + Included latest nqp-rx compiler, with many improvements > - Miscellaneous > + Portability updates for RTEMS, and Intel architectures with GNU compilers > + Completed conversion of ticket tracking system from RT to Trac > + Several (build time, runtime) performance improvements > + Converted many tests to PIR, reducing test execution time > + Various bugfixes, code cleanups, and coding standard fixes > > this level of detail seems more appropriate for the audience of our > release announcements. please feel free to correct or update the file > where appropriate. > ~jerry > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > -- Jonathan "Duke" Leto [email protected] http://leto.net _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
