You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by Andy Cutright <An...@borland.com> on 2003/07/25 11:15:04 UTC
[juddi-Developers] checkin/ merge/ branching policies
hi y'all,
i'd like to checkin/ merge my test code. do we have an informal policy
for checkin/ merges? i'm new to CVS, mostly used to clearcase, so sorry
for any incorrect term usages. httpd appears to follow a voting
procedure. given the size of our developer group, this might be a bit
unwieldy. i'd like to get some stuff into CVS today or monday..
cheers,
andy
RE: [juddi-Developers] checkin/ merge/ branching policies
Posted by Steve Viens <sv...@attbi.com>.
The key is to make sure that all of the targets in the build function
when you're done (i.e. use the 'dist' target).
Steve
-----Original Message-----
From: juddi-developers-admin@lists.sourceforge.net
[mailto:juddi-developers-admin@lists.sourceforge.net] On Behalf Of Steve
Viens
Sent: Friday, July 25, 2003 2:00 PM
To: juddi-developers@lists.sourceforge.net
Subject: RE: [juddi-Developers] checkin/ merge/ branching policies
Well said Adam.
Andy, go right ahead and check in what you've got.
Steve
-----Original Message-----
From: juddi-developers-admin@lists.sourceforge.net
[mailto:juddi-developers-admin@lists.sourceforge.net]
Sent: Friday, July 25, 2003 12:26 PM
To: juddi-developers@lists.sourceforge.net
Subject: RE: [juddi-Developers] checkin/ merge/ branching policies
I probably ought be able to point you to a bunch of information on this,
but I can't w/o a search that probably isn't warranted. I'm no expert,
but I'll summarize what *I understand* as the norm from other projects:
As a developer (committer) you've earned the right to be trusted
[hopefully you earned this status through (1) helping users -- i.e.
understand the project (2) submitting patches -- i.e. understanding the
implementation.] As such, you ought have the right to do any
checkin/merge you like. CVS is there (with history) in case you mess up
& something needs to be recovered. [Branching is for *big big changes*,
but I think the same stands.]
Since you've "worked with" the other committers on the team, you know
them and *respect* them & their views, you (1) already know what
constitutes a "votable" issue (i.e. contentious or debatable) and (2)
know that the other probably approve of. Do what you feel is right for
the project/team, and others ought respect that without question.
There is a lot written on not having the voting procedure slow down
development. I think the thought is -- ask forgiveness not permission.
BTW: Commits break things, so be it --- there is no progress without
some risk. That is what junit and gump are for...
regards,
Adam
-----Original Message-----
From: juddi-developers-admin@lists.sourceforge.net
[mailto:juddi-developers-admin@lists.sourceforge.net]On Behalf Of Andy
Cutright
Sent: Friday, July 25, 2003 10:14 AM
To: juddi-developers@lists.sourceforge.net
Subject: [juddi-Developers] checkin/ merge/ branching policies
hi y'all,
i'd like to checkin/ merge my test code. do we have an informal policy
for checkin/ merges? i'm new to CVS, mostly used to clearcase, so sorry
for any incorrect term usages. httpd appears to follow a voting
procedure. given the size of our developer group, this might be a bit
unwieldy. i'd like to get some stuff into CVS today or monday..
cheers,
andy
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01
/01
_______________________________________________
juddi-developers mailing list juddi-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-developers
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01
/01
_______________________________________________
juddi-developers mailing list juddi-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-developers
RE: [juddi-Developers] checkin/ merge/ branching policies
Posted by Steve Viens <sv...@attbi.com>.
Well said Adam.
Andy, go right ahead and check in what you've got.
Steve
-----Original Message-----
From: juddi-developers-admin@lists.sourceforge.net
[mailto:juddi-developers-admin@lists.sourceforge.net]
Sent: Friday, July 25, 2003 12:26 PM
To: juddi-developers@lists.sourceforge.net
Subject: RE: [juddi-Developers] checkin/ merge/ branching policies
I probably ought be able to point you to a bunch of information on this,
but I can't w/o a search that probably isn't warranted. I'm no expert,
but I'll summarize what *I understand* as the norm from other projects:
As a developer (committer) you've earned the right to be trusted
[hopefully you earned this status through (1) helping users -- i.e.
understand the project (2) submitting patches -- i.e. understanding the
implementation.] As such, you ought have the right to do any
checkin/merge you like. CVS is there (with history) in case you mess up
& something needs to be recovered. [Branching is for *big big changes*,
but I think the same stands.]
Since you've "worked with" the other committers on the team, you know
them and *respect* them & their views, you (1) already know what
constitutes a "votable" issue (i.e. contentious or debatable) and (2)
know that the other probably approve of. Do what you feel is right for
the project/team, and others ought respect that without question.
There is a lot written on not having the voting procedure slow down
development. I think the thought is -- ask forgiveness not permission.
BTW: Commits break things, so be it --- there is no progress without
some risk. That is what junit and gump are for...
regards,
Adam
-----Original Message-----
From: juddi-developers-admin@lists.sourceforge.net
[mailto:juddi-developers-admin@lists.sourceforge.net]On Behalf Of Andy
Cutright
Sent: Friday, July 25, 2003 10:14 AM
To: juddi-developers@lists.sourceforge.net
Subject: [juddi-Developers] checkin/ merge/ branching policies
hi y'all,
i'd like to checkin/ merge my test code. do we have an informal policy
for checkin/ merges? i'm new to CVS, mostly used to clearcase, so sorry
for any incorrect term usages. httpd appears to follow a voting
procedure. given the size of our developer group, this might be a bit
unwieldy. i'd like to get some stuff into CVS today or monday..
cheers,
andy
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01
/01
_______________________________________________
juddi-developers mailing list juddi-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-developers
RE: [juddi-Developers] checkin/ merge/ branching policies
Posted by Adam Jack <aj...@trysybase.com>.
I probably ought be able to point you to a bunch of information on this, but
I can't w/o a search that probably isn't warranted. I'm no expert, but I'll
summarize what *I understand* as the norm from other projects:
As a developer (committer) you've earned the right to be trusted [hopefully
you earned this status through (1) helping users -- i.e. understand the
project (2) submitting patches -- i.e. understanding the implementation.] As
such, you ought have the right to do any checkin/merge you like. CVS is
there (with history) in case you mess up & something needs to be recovered.
[Branching is for *big big changes*, but I think the same stands.]
Since you've "worked with" the other committers on the team, you know them
and *respect* them & their views, you (1) already know what constitutes a
"votable" issue (i.e. contentious or debatable) and (2) know that the other
probably approve of. Do what you feel is right for the project/team, and
others ought respect that without question.
There is a lot written on not having the voting procedure slow down
development. I think the thought is -- ask forgiveness not permission.
BTW: Commits break things, so be it --- there is no progress without some
risk. That is what junit and gump are for...
regards,
Adam
-----Original Message-----
From: juddi-developers-admin@lists.sourceforge.net
[mailto:juddi-developers-admin@lists.sourceforge.net]On Behalf Of Andy
Cutright
Sent: Friday, July 25, 2003 10:14 AM
To: juddi-developers@lists.sourceforge.net
Subject: [juddi-Developers] checkin/ merge/ branching policies
hi y'all,
i'd like to checkin/ merge my test code. do we have an informal policy
for checkin/ merges? i'm new to CVS, mostly used to clearcase, so sorry
for any incorrect term usages. httpd appears to follow a voting
procedure. given the size of our developer group, this might be a bit
unwieldy. i'd like to get some stuff into CVS today or monday..
cheers,
andy
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
juddi-developers mailing list
juddi-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-developers