Re: Trac Usage Conventions
Am 27.06.2008 um 02:48 schrieb Michael Stone: On Fri, Jun 27, 2008 at 01:31:24AM +0200, Marco Pesenti Gritti wrote: On Fri, Jun 27, 2008 at 1:24 AM, Michael Stone [EMAIL PROTECTED] wrote: 4. People should indicate the release they _wish_ that changes would land in via the Milestone field. I tend to think the Milestone should be set by the bug owner (or by other developers in its team) and not by the bug reporter. I'm not sure if that's what you mean with people or not. Your suggestion seems good; also, I was intentionally vague. Seems reasonable (unless the reporter is part of the development team of course). Also, the usage conventions should be linked from Trac. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Trac Usage Conventions
On Jun 26 2008, at 20:48, Michael Stone was caught saying: On Fri, Jun 27, 2008 at 01:31:24AM +0200, Marco Pesenti Gritti wrote: On Fri, Jun 27, 2008 at 1:24 AM, Michael Stone [EMAIL PROTECTED] wrote: 4. People should indicate the release they _wish_ that changes would land in via the Milestone field. I tend to think the Milestone should be set by the bug owner (or by other developers in its team) and not by the bug reporter. I'm not sure if that's what you mean with people or not. Your suggestion seems good; also, I was intentionally vague. What do others think? I have a concern that non-developers will use the Milestone field to determine what we (OLPC as an organization) are planning on supporting in a given release and not as a wishlist item. I suggest this field should only be set by one of the release release team members once the team is comfortable promissing a feature/bugfix to based on develper feedback and prioritization based on end-user inputs. ~Deepak -- Deepak Saxena [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Trac Usage Conventions
On Fri, Jun 27, 2008 at 4:17 PM, Deepak Saxena [EMAIL PROTECTED] wrote: On Jun 26 2008, at 20:48, Michael Stone was caught saying: On Fri, Jun 27, 2008 at 01:31:24AM +0200, Marco Pesenti Gritti wrote: On Fri, Jun 27, 2008 at 1:24 AM, Michael Stone [EMAIL PROTECTED] wrote: 4. People should indicate the release they _wish_ that changes would land in via the Milestone field. I tend to think the Milestone should be set by the bug owner (or by other developers in its team) and not by the bug reporter. I'm not sure if that's what you mean with people or not. Your suggestion seems good; also, I was intentionally vague. What do others think? I have a concern that non-developers will use the Milestone field to determine what we (OLPC as an organization) are planning on supporting in a given release and not as a wishlist item. I suggest this field should only be set by one of the release release team members once the team is comfortable promissing a feature/bugfix to based on develper feedback and prioritization based on end-user inputs. It's not a wishlist, it would be if reporters would be setting the milestones. It's what OLPC maintainers *think* they might be able to get in the release. And it's completed by the block:* keyword, which is reserved to release team, which is actually a promise. I think interpreting the milestone field in trac as promissing a feature/bugfix would be a misuse of it. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Trac Usage Conventions
On Fri, Jun 27, 2008 at 1:24 AM, Michael Stone [EMAIL PROTECTED] wrote: 7. We have added a 'Needs Action' field to Trac with several states for common actions (and various kinds of ignorance of what action is needed.) Please use it. Let us know if we need to change the set of actions. I posted comments/questions about this, I should have posted them here prolly. Anyway: http://lists.laptop.org/pipermail/devel/2008-June/015788.html Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Trac Usage Conventions
Dear world, In yesterday's software status meeting, we formulated some conventions for using Trac for the next few months. They are: 1. The release team - presently including me, Greg Smith, and Kim Quirk will occasionally tag a ticket as 'blocks:8.2.0' to indicate that it blocks the 8.2.0 release. Such tickets will be understood to be part of our release criteria. If you think that a ticket should be so marked, please poke us until we deal with it. 2. Greg will record customer preference data according to whatever means he sees fit and will inform us of these data in regular meetings. 3. Kim wants a way to keep track of 'critical' bugs. Michael defined 'critical bugs' as those bugs which receive the most careful oversight by the release team. Shortly, the release team will invent a convention for identifying such bugs which permits their inclusion in reports. These reports will be listed on the frontpage of Trac. 4. People should indicate the release they _wish_ that changes would land in via the Milestone field. 5. People should indicate their confidence that the changes _will_ land by tagging tickets with strings like: 8.2.0:+ -- means that the change is within reach or, preferably, has been included in a dist-olpc3-updates series build. 8.2.0:? -- the change is in danger of missing the boat. 8.2.0:- -- the change is unlikely to be ready for release (NB: Please be conservative in tagging things rel:+.) 6. When it's unambiguous, people should attach test results to tickets with tags like: joyride-2027:- -- the issue persists in joyride-2027 joyride-2029:+ -- the issue was not reproducible in joyride-2027 If appropriate, please also describe the test procedure that was executed to generate the result. 7. We have added a 'Needs Action' field to Trac with several states for common actions (and various kinds of ignorance of what action is needed.) Please use it. Let us know if we need to change the set of actions. 8. The 'priority' field is a place for component maintainers to say what they think is important; however, we expect that our regular IRC meetings and emails will be the primary vehicle for communicating day-to-day priority information. (NB: We may revisit the priority information decisions.) Please comment freely. Regards, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Trac Usage Conventions
On Fri, Jun 27, 2008 at 1:24 AM, Michael Stone [EMAIL PROTECTED] wrote: 4. People should indicate the release they _wish_ that changes would land in via the Milestone field. I tend to think the Milestone should be set by the bug owner (or by other developers in its team) and not by the bug reporter. I'm not sure if that's what you mean with people or not. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Trac Usage Conventions
On Fri, Jun 27, 2008 at 01:31:24AM +0200, Marco Pesenti Gritti wrote: On Fri, Jun 27, 2008 at 1:24 AM, Michael Stone [EMAIL PROTECTED] wrote: 4. People should indicate the release they _wish_ that changes would land in via the Milestone field. I tend to think the Milestone should be set by the bug owner (or by other developers in its team) and not by the bug reporter. I'm not sure if that's what you mean with people or not. Your suggestion seems good; also, I was intentionally vague. What do others think? Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
