Hi, I will integrate these feedback into the wiki before we can remove the Draft status. My work here is to document what is really happening in the development process. So this document is descriptive, not prescriptive. I want to discuss the changes that I think that we need to make in the documentation: * Goal of the documentation [Remove Explain the process to SUSE employees. ] """ The goal of this document is to: - Serve as main reference to the existing documentation around the process. - Provide the big picture of the process to the existing community and those new to it - Help us to detect areas for improvements. """ * openSUSE Dev. and Int. Process High Level Description [Reference T1.3 for a better explanation of the process. Reference the mailing list. Downgrade openFATE as a documentation tool] """ - Roadmap and Feature Planning. The Release Manager creates the initial roadmap [1] [2] [3] by putting in the number of milestones, betas and release candidates that need to be released for the distribution. The schedule is adjusted taking into consideration vacations and other constraints described in the Roadmap Process. In parallel, developers from the community will decide a set of technical goals for the distribution based on the projected release and freeze dates [4] [5], using the mailing list and documenting these features in openFATE [6][7] or in a dedicated wiki page per project (see T1.3 for a further description about how the features are decided). The feature freezes are scheduled as part of this task. """ * Product Manager Looks like that there is some agreement that this role is a SUSE role, and that the name is not precise enough. I propose to change this name and the description in the documentation. I can propose something like "Project Coordinator", "Project Representative", I don't know. If there is not consensus, I propose that at least we include a note in the role description that the Product Manager is not an openSUSE role, but a SUSE one * Roadmap and Feature Planning [Add more relevance to the mailing list, and less to openFATE] """ - T1.3 Determine the new features. On the mailing list (as the primary channel for discussing ideas and features) and through other community communication channels the new features expected for this release are discussed and defined. Some of those features can be documented on openFATE [6] (not widely used) or the wiki [3]. The features are decided inside the community (in this moment this is done only by a really small number of contributors) or internally in SUSE when there is a relation between SLE and openSUSE: a developer can create a feature in FATE for SLE and then add openSUSE afterward (this kind of feature is not visible outside) At this moment we do not have a strict policy on using openFATE. Some features are also decided later without planning and documentation. If the feature is implemented after the freeze calendar, and explicit approval from the Factory Maintainer is needed for the integration. """ * Devel Project Integration [Add the Package Maintainer in the decision to submit to factory] """ - T3.4 Submit to Factory. Once the Package or Project Maintainer considers the package(s) in his project good enough he/she creates a submit request for Factory. """ [Fix a contradiction in X3.1] """ - X3.1 The Package or Project Maintainer creates a submit request for Factory """ * Factory Integration Comment from Robert: It appears that in "Factory Integration" the tasks for feeding back changes from "The Factory Maintainer decides to fix an issue inside Factory" to the devel project are missing. I think that this is T5.5. If the Factory Maintainer decides that he / she want to fix something he become a Package Developer for this moment (fix the issue, create the SR, and integrate into factory). Am I wrong here? * Public Test [Add Factory testers. Add a new reference] """ - V7.1 Test in real machine. The user (or developer) can go to software.o.o [14] to download the release and install it in the real hardware. If he / she detect a bug a new bug report is created in bugzilla [19] or / and a mail is send to the Factory mailing list. Also, many users decide to test Factory directly updating the repositories [50], without installing the released media. [50] How to install Factory http://en.opensuse.org/openSUSE:Factory_installation """ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org