Opened 11 years ago

Last modified 8 years ago

#1497 new Tasks

Ruling needed on tracker usage

Reported by: Dave Abrahams Owned by: Beman Dawes
Milestone: Boost 1.40.0 Component: trac / subversion
Version: Boost Development Trunk Severity: Problem
Keywords: Cc: Eric Niebler, Daniel James


I know my concerns of were not universally well-received, and Beman was silent on the issue. Beman, I really think the release manager for 1.35 needs to definitively demonstrate support for, or opposition to, this approach. I think you know my opinion: if we don't institute these practices now, our new tracking system will be just as ineffective as the last one was.

I will be happy to write documentation if necessary.

Change History (5)

comment:1 Changed 11 years ago by Dave Abrahams

See also #1079

comment:2 Changed 10 years ago by Daniel James

Component: DocumentationNone

comment:3 Changed 10 years ago by Vladimir Prus

Ping? I think the usage of milestones in the tracker should indeed be clarified.

comment:4 Changed 10 years ago by Dave Abrahams

Cc: Eric Niebler Daniel James added
Milestone: Boost 1.36.0Boost 1.40.0
Version: Boost 1.34.1Boost Development Trunk

Yes, please! Beman, please read the head of that thread:

IMO this is exceedingly important, and the only reason I'm not doing it myself is that it seems to be the domain of the release managers. It will be an especially huge missed opportunity if we don't get this straightened out before the bug sprint. Oops! That starts today! We'd better get moving.

Again, if there's any way I can help, including writing the policy, please let me know. By the way, I'm not attached to eliminating "to be determined," if that helps in any way to resolve this.

comment:5 Changed 8 years ago by viboes

Component: Nonetrac / subversion
Note: See TracTickets for help on using tickets.