Hi Tobias, Le 04/11/2010 17:28, Tobias Schlitt a écrit : > docs/release_process.txt It is a very interesting and useful synthesis. Thank you. > The document summarizes the requirements for releases roughly and then > tries to relealize these in a release process specific to Zeta. > > There are some open issues marked with notes in this document, which > need to be decided on. I read the document and I focused on the two next issues (or notes) :
.. note:: Incubating phase (around line 118) I don't understand what is the matter with this one. Could you tell me more please ? .. note:: Determine release times. (around line 155) It seems that a full package release is a packaging of all last *stable* component releases. Hence, a full package release could be rolled automatically after every component release. So, I see full package release as a sub part of component release process, which involves that : - There is no need for release time. - There is no need for votes. This possibility relies on the assumption that a full package release hasn't more value-added (or worth) than sum of stable component releases. It means that there is no additional deployment mechanism in full package releases for instance. Here comes questions : A/ What is your opinion about the proposal automate full package release ? B/ What are advantages of separating full package release process from component release process ? (It should probably be my first question before writing all this stuff :-)) Thank you for the doc. Regards. Thomas. > Regards, > Toby
