On 26/02/15 10:36, Andrea Aime wrote: > On Tue, Feb 24, 2015 at 9:47 PM, Ben Caradoc-Davies <[email protected]> > wrote: >> Sampo, >> this new feature surely merits a mention. >> Developers, I wonder if we need a process to help accumulate a list of >> new features for each release? A wiki page page, perhaps? Rather than >> last-minute blog changes. This would in my view ease the release process. > We always worked off jira changelogs, and proposals to get a bit more of > explanation > over ther larger changes, maintaining manually a third separate list > certainly looks > like an un-necessary overhead that, personally, I'm not willing to support.
I am thinking more of a blog-drafting area to make things easier for the poor old release engineer. The current approach requires trawling though Jira and proposals, and I find it quite hard to distinguish and describe incremental and major improvements well enough to select them for marketing purposes (blog post). Many Jira records are terse. The current practice requires all feature authors to be available at release time. Perhaps an alternative practice would be to start drafting and reviewing the release blog post two weeks before the release itself? This would give more opportunity to gather contributions and improve the quality of the blog post. Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineer Transient Software <http://transient.nz> New Zealand ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
