You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Andrey Dibrov <ad...@softdev.spb.ru> on 2009/09/24 10:32:32 UTC

public/private commits

Здравствуйте, Users.

I uses SVN a long time, so i find out what SVN still doesn't have
someone feature. It will be very useful to organize into future
version of SVN new feature for commit action. Developers sometimes
wants to make commits for yourself to hide changes from other
developers in trunk or in branch. This is very useful if you want to commit
not complete or not enough tested changes to server, go home or other place
and take public update plus self private (not public) update to complete changes
and make later public commit.
Does this feature with public/private commit already exist?

-- 
С уважением,
 Andrey                          mailto:adibrov@softdev.spb.ru

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2399228

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Fwd: Re[2]: public/private commits

Posted by Andrey Dibrov <ad...@softdev.spb.ru>.
Здравствуйте, .

> On Thu, Sep 24, 2009 at 06:32, Andrey Dibrov <ad...@softdev.spb.ru> wrote:
>> Здравствуйте, Users.
>>
>> I uses SVN a long time, so i find out what SVN still doesn't have
>> someone feature. It will be very useful to organize into future
>> version of SVN new feature for commit action. Developers sometimes
>> wants to make commits for yourself to hide changes from other
>> developers in trunk or in branch. This is very useful if you want to commit
>> not complete or not enough tested changes to server, go home or other place
>> and take public update plus self private (not public) update to complete changes
>> and make later public commit.
>> Does this feature with public/private commit already exist?

> Commit your "in progress" work to a branch you create, when complete
> merge your changes back to a common location (trunk or another
> branch).
This is really ambiguous to create branch per developer.

> Developers working together on a project should almost never have a
> need to hide things from each other. It's not good for the team.
Better doesn't see broken sources, than gonna get broken build. Team
shouldn't see private commit, it is useful only for developer who
made it.

-- 
С уважением,
 Andrey                          mailto:adibrov@softdev.spb.ru


---------- Конец пересылаемого письма ----------
-- 
С уважением,
 Andrey                          mailto:adibrov@softdev.spb.ru

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2399706

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Fwd: Re[4]: public/private commits

Posted by Les Mikesell <le...@gmail.com>.
Andrey Dibrov wrote:

>>>> This is really ambiguous to create branch per developer.
> 
>> How so? It keeps everyone's work isolated, which is what you're
>> apparently looking for.
> This is require administrative access to SVN to create a branch or
> maintain it.

No it doesn't, other than than making sure the developers have write access in 
the path where you want their development branches.

> A private/public commits shouldn't require them (may be
> require, but only to active this kind of feature).

Branches are the usual/expected solution to this problem.  Subversion doesn't 
have any public/private concepts.  Everything is just a path like any other to 
subversion and you can do what you want in terms of content or access control 
down any path.  There are, of course, conventions for trunk/branches/tags, and 
the convention for branches are what you are describing.

>> The danger is that the longer you keep people isolated, the harder it
>> will become to merge changes back together.
> This is doesn't matter, developer can just don't commit a week or
> more, what make commit harder too. Difference is in thing what
> developer now can just store its own source changes on server
> instead of local.

Yes, that's the point of branches - they isolate changes from other copies until 
they are merged.

>>>> Developers working together on a project should almost never have a
>>>> need to hide things from each other. It's not good for the team.
>>> Better doesn't see broken sources, than gonna get broken build. Team
>>> shouldn't see private commit, it is useful only for developer who
>>> made it.
> 
>> If each developer is committing to their own branch, who else will see
>> the broken sources/build?
> No one, this is ONLY for store changes, not for apply them.

An occasional broken build during development should not be considered a 
disaster, especially when it is the result of different people making different 
changes.  It is often better to make them visible to everyone so they can agree 
on the best solution which may very well not be in the code that you want to 
keep isolated.

-- 
   Les Mikesell
    lesmikesell@gmail.com

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401001

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Re[4]: public/private commits

Posted by Daniel Becroft <dj...@gmail.com>.
On Fri, Sep 25, 2009 at 4:21 PM, Andrey Dibrov <ad...@softdev.spb.ru>wrote:

> Здравствуйте, users@subversion.tigris.org.
>
> >>>> I uses SVN a long time, so i find out what SVN still doesn't have
> >>>> someone feature. It will be very useful to organize into future
> >>>> version of SVN new feature for commit action. Developers sometimes
> >>>> wants to make commits for yourself to hide changes from other
> >>>> developers in trunk or in branch. This is very useful if you want to
> commit
> >>>> not complete or not enough tested changes to server, go home or other
> place
> >>>> and take public update plus self private (not public) update to
> complete changes
> >>>> and make later public commit.
> >>>> Does this feature with public/private commit already exist?
> >>
> >>> Commit your "in progress" work to a branch you create, when complete
> >>> merge your changes back to a common location (trunk or another
> >>> branch).
> >> This is really ambiguous to create branch per developer.
>
> > How so? It keeps everyone's work isolated, which is what you're
> > apparently looking for.
> This is require administrative access to SVN to create a branch or
> maintain it. A private/public commits shouldn't require them (may be
> require, but only to active this kind of feature).
>

How does creating a branch require administrative access to SVN? It's just a
simple "svn cp" command.

The only thing I can think of is path-based authorisation, but that can be
easily worked around (free-for-all folder, branches-private, for example).


> > The danger is that the longer you keep people isolated, the harder it
> > will become to merge changes back together.
> This is doesn't matter, developer can just don't commit a week or
> more, what make commit harder too. Difference is in thing what
> developer now can just store its own source changes on server
> instead of local.



> >>> Developers working together on a project should almost never have a
> >>> need to hide things from each other. It's not good for the team.
> >> Better doesn't see broken sources, than gonna get broken build. Team
> >> shouldn't see private commit, it is useful only for developer who
> >> made it.
>
> > If each developer is committing to their own branch, who else will see
> > the broken sources/build?
> No one, this is ONLY for store changes, not for apply them.
>

If your changes are simple, generate and store patches. If not, private
branches are the generally accepted solution.

Cheers,
Daniel B.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2400991

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Fwd: Re[4]: public/private commits

Posted by Andrey Dibrov <ad...@softdev.spb.ru>.
Здравствуйте, users@subversion.tigris.org.

>>>> I uses SVN a long time, so i find out what SVN still doesn't have
>>>> someone feature. It will be very useful to organize into future
>>>> version of SVN new feature for commit action. Developers sometimes
>>>> wants to make commits for yourself to hide changes from other
>>>> developers in trunk or in branch. This is very useful if you want to commit
>>>> not complete or not enough tested changes to server, go home or other place
>>>> and take public update plus self private (not public) update to complete changes
>>>> and make later public commit.
>>>> Does this feature with public/private commit already exist?
>>
>>> Commit your "in progress" work to a branch you create, when complete
>>> merge your changes back to a common location (trunk or another
>>> branch).
>> This is really ambiguous to create branch per developer.

> How so? It keeps everyone's work isolated, which is what you're
> apparently looking for.
This is require administrative access to SVN to create a branch or
maintain it. A private/public commits shouldn't require them (may be
require, but only to active this kind of feature).

> The danger is that the longer you keep people isolated, the harder it
> will become to merge changes back together.
This is doesn't matter, developer can just don't commit a week or
more, what make commit harder too. Difference is in thing what
developer now can just store its own source changes on server
instead of local.

>>> Developers working together on a project should almost never have a
>>> need to hide things from each other. It's not good for the team.
>> Better doesn't see broken sources, than gonna get broken build. Team
>> shouldn't see private commit, it is useful only for developer who
>> made it.

> If each developer is committing to their own branch, who else will see
> the broken sources/build?
No one, this is ONLY for store changes, not for apply them.

-- 
С уважением,
 Andrey                          mailto:adibrov@softdev.spb.ru

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2400093

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: public/private commits

Posted by Andy Levy <an...@gmail.com>.
On Thu, Sep 24, 2009 at 06:32, Andrey Dibrov <ad...@softdev.spb.ru> wrote:
> Здравствуйте, Users.
>
> I uses SVN a long time, so i find out what SVN still doesn't have
> someone feature. It will be very useful to organize into future
> version of SVN new feature for commit action. Developers sometimes
> wants to make commits for yourself to hide changes from other
> developers in trunk or in branch. This is very useful if you want to commit
> not complete or not enough tested changes to server, go home or other place
> and take public update plus self private (not public) update to complete changes
> and make later public commit.
> Does this feature with public/private commit already exist?

Commit your "in progress" work to a branch you create, when complete
merge your changes back to a common location (trunk or another
branch).

Developers working together on a project should almost never have a
need to hide things from each other. It's not good for the team.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2399232

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: public/private commits

Posted by Udo Rader <li...@bestsolution.at>.
you should reconfigure your mailer to compose plain text emails only ...

Andrey Dibrov wrote:
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html><head><title>Re[2]: public/private commits</title>
> <META http-equiv=Content-Type content="text/html; charset=utf-8">
> <meta http-equiv="Content-Style-Type" content="text/css">
> <style type="text/css"><!--
> body {
>   margin: 5px 5px 5px 5px;
>   background-color: #ffffff;
> }
> /* ========== Text Styles ========== */
> hr { color: #000000}
> body, table /* Normal text */
> {
>  font-size: 9pt;
>  font-family: 'Courier New';
>  font-style: normal;
>  font-weight: normal;
>  color: #000000;
>  text-decoration: none;
> }
> span.rvts1 /* Heading */
> {
>  font-size: 10pt;
>  font-family: 'Arial';
>  font-weight: bold;
>  color: #0000ff;
> }
> span.rvts2 /* Subheading */
> {
>  font-size: 10pt;
>  font-family: 'Arial';
>  font-weight: bold;
>  color: #000080;
> }
> span.rvts3 /* Keywords */
> {
>  font-size: 10pt;
>  font-family: 'Arial';
>  font-style: italic;
>  color: #800000;
> }
> a.rvts4, span.rvts4 /* Jump 1 */
> {
>  font-size: 10pt;
>  font-family: 'Arial';
>  color: #008000;
>  text-decoration: underline;
> }
> a.rvts5, span.rvts5 /* Jump 2 */
> {
>  font-size: 10pt;
>  font-family: 'Arial';
>  color: #008000;
>  text-decoration: underline;
> }
> span.rvts6
> {
>  font-size: 11pt;
>  font-family: 'tahoma';
>  font-weight: bold;
>  color: #ffffff;
>  background-color: #0000ff;
> }
> span.rvts7
> {
>  font-size: 11pt;
>  font-family: 'tahoma';
> }
> a.rvts8, span.rvts8
> {
>  font-size: 11pt;
>  font-family: 'tahoma';
>  color: #0000ff;
>  text-decoration: underline;
> }
> span.rvts9
> {
>  font-size: 11pt;
>  font-family: 'tahoma';
>  color: #888888;
> }
> span.rvts10
> {
>  font-size: 8pt;
>  font-family: 'arial';
>  font-style: italic;
>  color: #c0c0c0;
> }
> a.rvts11, span.rvts11
> {
>  font-size: 8pt;
>  font-family: 'arial';
>  color: #0000ff;
>  text-decoration: underline;
> }
> /* ========== Para Styles ========== */
> p,ul,ol /* Paragraph Style */
> {
>  text-align: left;
>  text-indent: 0px;
>  padding: 0px 0px 0px 0px;
>  margin: 0px 0px 0px 0px;
> }
> .rvps1 /* Centered */
> {
>  text-align: center;
> }
> --></style>
> </head>
> <body>
> 
> <p>Здравствуйте, David.</p>
> <p><br></p>
> <p>Вы писали 24 сентября 2009 г., 23:56:46:</p>
> <p><br></p>
> <div><table border=0 cellpadding=1 cellspacing=2>
> <tr valign=top>
> <td width=12 style="background-color: #0000ff;">
> <p><span class=rvts6>&gt;</span></p>
> </td>
> <td width=867 style="background-color: #ffffff;">
> <p><span class=rvts7>There's a danger if you allow developers to commit code without it being part of the build. When you give developers this ability, they tend to bite off big chunks of code since they know they can commit changes without breaking the build.</span></p>
> </td>
> </tr>
> </table>
> </div>
> <p>They already have this ability just through public commit.</p>
> <div><table border=0 cellpadding=1 cellspacing=2>
> <tr valign=top>
> <td width=12 style="background-color: #0000ff;">
> <p><span class=rvts6>&gt;</span></p>
> </td>
> <td width=867 style="background-color: #ffffff;">
> <p><br></p>
> <p><span class=rvts7>If developers are forced to check in their changes on the main development line, they have to be more careful with their changes, check for errors, and make sure they don't make too big a change at once. You actually get a better, more error free development.</span></p>
> </td>
> </tr>
> </table>
> </div>
> <p>This is true and without private commits. Private commits doesn't solve or break things around error free development, this is not a target.</p>
> <div><table border=0 cellpadding=1 cellspacing=2>
> <tr valign=top>
> <td width=12 style="background-color: #0000ff;">
> <p><span class=rvts6>&gt;</span></p>
> </td>
> <td width=867 style="background-color: #ffffff;">
> <p><br></p>
> <p><span class=rvts7>If you have a major change that will take more than a day or two, you can create a branch for that particular feature. But, if you do that, you have to be careful. Make sure that the changes from the main development line are being merged into this branch. Also make this branch part of the automated build process. This ensures that the developers aren't writing code that will be impossible to merge into your main development line.</span></p>
> </td>
> </tr>
> </table>
> </div>
> <p>Branches requires if some part of application or program detaches from main development line, and team require to test and build it independently to trunk or other branches. Private commits is just different feature which doesn't correlate with truck or branches. Private commits is just a way to store changes on server instead of locally.</p>
> <p><br></p>
> <p><br></p>
> <p><span class=rvts10>--&nbsp;</span></p>
> <p><span class=rvts10>С уважением,</span></p>
> <p><span class=rvts10>&nbsp;Andrey &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</span><a class=rvts11 href="mailto:adibrov@softdev.spb.ru">mailto:adibrov@softdev.spb.ru</a></p>
> 
> </body></html>
> 
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2400094
> 
> To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].


-- 
Udo Rader, CTO
http://www.bestsolution.at
http://riaschissl.blogspot.com

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2400114

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: public/private commits

Posted by Michael Diers <md...@elego.de>.
Andrey Dibrov wrote:
[...]
> Branches requires if some part of application or program detaches
> from main development line, and team require to test and build it
> independently to trunk or other branches. Private commits is just
> different feature which doesn't correlate with truck or branches.
> Private commits is just a way to store changes on server instead of
> locally.

You may wish to persist your working copy state in the repository, then.
(This is likely not quite what you're after, but perhaps it's
sufficiently close.)

Assume you're working on project "coolstuff" in working copy
~/svnwc/coolstuff.

$ cd ~/svnwc/coolstuff
$ svn cp . ^/work-in-progress/andrey/coolstuff/2009-09-24_007

-- 
Michael Diers, elego Software Solutions GmbH, http://www.elego.de

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2400180

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re[2]: public/private commits

Posted by Andrey Dibrov <ad...@softdev.spb.ru>.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><title>Re[2]: public/private commits</title>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
body {
  margin: 5px 5px 5px 5px;
  background-color: #ffffff;
}
/* ========== Text Styles ========== */
hr { color: #000000}
body, table /* Normal text */
{
 font-size: 9pt;
 font-family: 'Courier New';
 font-style: normal;
 font-weight: normal;
 color: #000000;
 text-decoration: none;
}
span.rvts1 /* Heading */
{
 font-size: 10pt;
 font-family: 'Arial';
 font-weight: bold;
 color: #0000ff;
}
span.rvts2 /* Subheading */
{
 font-size: 10pt;
 font-family: 'Arial';
 font-weight: bold;
 color: #000080;
}
span.rvts3 /* Keywords */
{
 font-size: 10pt;
 font-family: 'Arial';
 font-style: italic;
 color: #800000;
}
a.rvts4, span.rvts4 /* Jump 1 */
{
 font-size: 10pt;
 font-family: 'Arial';
 color: #008000;
 text-decoration: underline;
}
a.rvts5, span.rvts5 /* Jump 2 */
{
 font-size: 10pt;
 font-family: 'Arial';
 color: #008000;
 text-decoration: underline;
}
span.rvts6
{
 font-size: 11pt;
 font-family: 'tahoma';
 font-weight: bold;
 color: #ffffff;
 background-color: #0000ff;
}
span.rvts7
{
 font-size: 11pt;
 font-family: 'tahoma';
}
a.rvts8, span.rvts8
{
 font-size: 11pt;
 font-family: 'tahoma';
 color: #0000ff;
 text-decoration: underline;
}
span.rvts9
{
 font-size: 11pt;
 font-family: 'tahoma';
 color: #888888;
}
span.rvts10
{
 font-size: 8pt;
 font-family: 'arial';
 font-style: italic;
 color: #c0c0c0;
}
a.rvts11, span.rvts11
{
 font-size: 8pt;
 font-family: 'arial';
 color: #0000ff;
 text-decoration: underline;
}
/* ========== Para Styles ========== */
p,ul,ol /* Paragraph Style */
{
 text-align: left;
 text-indent: 0px;
 padding: 0px 0px 0px 0px;
 margin: 0px 0px 0px 0px;
}
.rvps1 /* Centered */
{
 text-align: center;
}
--></style>
</head>
<body>

<p>Здравствуйте, David.</p>
<p><br></p>
<p>Вы писали 24 сентября 2009 г., 23:56:46:</p>
<p><br></p>
<div><table border=0 cellpadding=1 cellspacing=2>
<tr valign=top>
<td width=12 style="background-color: #0000ff;">
<p><span class=rvts6>&gt;</span></p>
</td>
<td width=867 style="background-color: #ffffff;">
<p><span class=rvts7>There's a danger if you allow developers to commit code without it being part of the build. When you give developers this ability, they tend to bite off big chunks of code since they know they can commit changes without breaking the build.</span></p>
</td>
</tr>
</table>
</div>
<p>They already have this ability just through public commit.</p>
<div><table border=0 cellpadding=1 cellspacing=2>
<tr valign=top>
<td width=12 style="background-color: #0000ff;">
<p><span class=rvts6>&gt;</span></p>
</td>
<td width=867 style="background-color: #ffffff;">
<p><br></p>
<p><span class=rvts7>If developers are forced to check in their changes on the main development line, they have to be more careful with their changes, check for errors, and make sure they don't make too big a change at once. You actually get a better, more error free development.</span></p>
</td>
</tr>
</table>
</div>
<p>This is true and without private commits. Private commits doesn't solve or break things around error free development, this is not a target.</p>
<div><table border=0 cellpadding=1 cellspacing=2>
<tr valign=top>
<td width=12 style="background-color: #0000ff;">
<p><span class=rvts6>&gt;</span></p>
</td>
<td width=867 style="background-color: #ffffff;">
<p><br></p>
<p><span class=rvts7>If you have a major change that will take more than a day or two, you can create a branch for that particular feature. But, if you do that, you have to be careful. Make sure that the changes from the main development line are being merged into this branch. Also make this branch part of the automated build process. This ensures that the developers aren't writing code that will be impossible to merge into your main development line.</span></p>
</td>
</tr>
</table>
</div>
<p>Branches requires if some part of application or program detaches from main development line, and team require to test and build it independently to trunk or other branches. Private commits is just different feature which doesn't correlate with truck or branches. Private commits is just a way to store changes on server instead of locally.</p>
<p><br></p>
<p><br></p>
<p><span class=rvts10>--&nbsp;</span></p>
<p><span class=rvts10>С уважением,</span></p>
<p><span class=rvts10>&nbsp;Andrey &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</span><a class=rvts11 href="mailto:adibrov@softdev.spb.ru">mailto:adibrov@softdev.spb.ru</a></p>

</body></html>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2400094

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: public/private commits

Posted by David Weintraub <qa...@gmail.com>.
There's a danger if you allow developers to commit code without it being
part of the build. When you give developers this ability, they tend to bite
off big chunks of code since they know they can commit changes without
breaking the build.
If developers are forced to check in their changes on the main development
line, they have to be more careful with their changes, check for errors, and
make sure they don't make too big a change at once. You actually get a
better, more error free development.

If you have a major change that will take more than a day or two, you can
create a branch for that particular feature. But, if you do that, you have
to be careful. Make sure that the changes from the main development line are
being merged into this branch. Also make this branch part of the automated
build process. This ensures that the developers aren't writing code that
will be impossible to merge into your main development line.

I've seen this type of issue when we use ClearCase and Git because these two
version control systems make it so easy to work off the main development
line.

On Thu, Sep 24, 2009 at 6:32 AM, Andrey Dibrov <ad...@softdev.spb.ru>wrote:

> Здравствуйте, Users.
>
> I uses SVN a long time, so i find out what SVN still doesn't have
> someone feature. It will be very useful to organize into future
> version of SVN new feature for commit action. Developers sometimes
> wants to make commits for yourself to hide changes from other
> developers in trunk or in branch. This is very useful if you want to commit
> not complete or not enough tested changes to server, go home or other place
> and take public update plus self private (not public) update to complete
> changes
> and make later public commit.
> Does this feature with public/private commit already exist?
>
> --
> С уважением,
>  Andrey                          mailto:adibrov@softdev.spb.ru
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2399228
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe@subversion.tigris.org].
>



-- 
David Weintraub
qazwart@gmail.com

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2399972

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].