[p4] How to communicate codeline policies to users?

[Dave Lewis]

I have considered something like this but never did it.  I think its a
good idea.  There were other bits of info I wanted to keep also, but
I've forgotten exactly what they were!

Oh, I know.  Naming issues.  Like when you create a branch with the
release name in it, and then they decide to change the release name.
a little history in that file would be invaluable, perhaps machine
readable so that stuff could be extracted automatically.

Stuff like changing product names also...

dave

On 9/18/07, Jeff A. Bowles <jab at pobox.com> wrote:
> I always liked putting the policy in the top of the source-tree, e.g.,
> //depot/main/policy.txt.
> Keep it short, I would tell people in classes. No more than one page of
> email
>
> On 9/17/07, Chuck Emary <chuck.emary at configuresoft.com> wrote:
> >
> > Hello,
> > We handle it through the user of a wiki and emails, from the notification
> > perspective.  I use triggers to enforce the lockdown of approved defects.
> >
> > Cheers,
> > Chuck
> >
> > -----Original Message-----
> > From: perforce-user-bounces at perforce.com [mailto:
> > perforce-user-bounces at perforce.com] On Behalf Of Roy Smith
> > Sent: Monday, September 17, 2007 3:49 PM
> > To: Perforce Users Mailing List
> > Subject: [p4] How to communicate codeline policies to users?
> >
> > I've taken to putting a policy statement in my branch specs.  For
> > example:
> >
> > > Description:
> > >         Created by smithr3.  Final development branch for DMT-8.0
> > >
> > >         The only changes which should be submitted to this branch are
> > >         critical bug fixes in response to tickets raised by QE.  If in
> > >         doubt about whether it is appropriate to submit to this branch
> > >         or not, please triage through Rich Hammond.
> >
> > The problem is that branch specs are not very visible.  It's not that
> > they're hidden or secret, but you need to know to go looking for
> > them.  Is there any more straight-forward way to advertise to users
> > what the policy for a particular codeline is?  It would be nice, for
> > example, if somebody could do "p4 policy ." and have the above
> > description be printed.
> >
> > How do people deal with these kinds of things in production
> > environments?
> >
> > -------------------
> > Roy Smith <smith_roy at emc.com>
> > Software Guy, EMC Common Management Group
> > 44 South Broadway, 7th floor
> > White Plains, NY 10601
> > (914) 580-3427
> > AIM: roysmith649
> >
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
>
>
>
> --
> ---
> Jeff Bowles - jeff.a.bowles at gmail.com
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>