Dear Saros Developers, since we switched to Git last week and we are short on experience in releasing our marvelous project in a non-SVN environment, Holger proposed to do a "dry" release. The aim of such a release would be to gain experience and confidence -- the actual outcome in terms of working software is secondary. The lessons learned from this release will hopefully form some valuable input for the renovation of our release process [1].
In order to have our new release process field-tested and documented as soon as possible, I scheduled a dry release for the next week, beginning on Monday, 7th May. I propose the following deviations compared with the currently stated roles and tasks [2]: * DM: Because of a shortage in human resources the Documentation Manager role is "hibernated". * There will be no acceptance test. In general, the dry release should be authentic, so some discovered bugs during the internal testing phase would be nice :) I further propose the following cast: * DM: (hibernated) * RM: Holger Freyther * ARM: Franz Zieris * TM: Norman Warnatsch * ATM: Maria Spiering Please let me know if somebody is not OK with that or has some comments. Best Regards, Franz Links [1] http://www.saros-project.org/ReleaseProcess [2] http://www.saros-project.org/ReleaseProcess#Roles ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dpp-devel mailing list Dpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
