17:01:04 #startmeeting Murano 17:01:05 Meeting started Mon May 27 17:01:04 2013 UTC. The chair is dnosovitsky. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:08 The meeting name has been set to 'murano' 17:01:23 Hello everyone 17:01:38 #topic Agenda 17:01:47 Our today's topics: 17:01:51 1) Murano release code freeze 17:01:57 2) Release management 17:02:05 Let's start with the easy one: 17:02:08 #topic Code freeze 17:02:31 As far as I know, all features are ready, and we can make a release branch 17:03:24 #info May 28 is going to be Phase I release feature freeze 17:03:34 Let me clarify: 17:03:58 #info our feature freeze just means creating a release branch. 17:04:46 Our master branch will continue on receiving commits, 17:04:58 but our release branch will be open for no development except bugfixing 17:05:33 When we have tested and have proven it to be stable, we release this frozen branch 17:05:46 Questions? 17:05:57 If no, let me go on 17:06:24 #topic Release management 17:06:48 The important question is our release naming scheme 17:07:26 Let me suggest the the following release naming scheme: 17:07:51 .[..] 17:08:15 Numbering starts with zero 17:09:37 if everyone is ok with my suggestion, our current release will be be 0.6 17:11:50 Regarding our code branch name, I suggest "Release 0-6" 17:12:00 correspondingly 17:12:02 Why not to use just release version? 17:12:32 major.minor 17:12:53 you mean in the branch name? To make it clear what this branch is about 17:13:00 iteration is something internal. Why it should be in the release version? 17:13:22 Release-0.1 17:13:27 or just 0.1 17:14:02 yes, it is ok to name it 0.1 17:14:19 Release-0.1, I mean 17:15:31 #agreed Suggested branch name for tomorrow: Release 0.1 17:16:11 #topic Misc 17:16:18 Any questions? 17:16:31 Suggestions? 17:17:12 I think that's all for today 17:17:21 Thanks to everyone 17:17:40 #endmeeting