Mailing List Archive: Zope: Dev

Re: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes

Index | Next | Previous | View Threaded

marius at gedmin

Sep 11, 2009, 6:07 AM

Post #1 of 6 (276 views)
Permalink

Re: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes

On Thu, Sep 10, 2009 at 04:23:31PM -0400, Benji York wrote:
> On Thu, Sep 10, 2009 at 4:12 PM, Hanno Schlichting <hanno[at]hannosch.eu> wrote:
> > On Thu, Sep 10, 2009 at 9:46 PM, Alex Chapman<achapman[at]zope.com> wrote:
> >> Log message for revision 103721:
> >> keep trunk version at 0. Update changes
> >
> > I think I've seen the practice of denoting the version on trunk as
> > "zero" from Jim already.
> >
> > It is in conflict with
> > http://docs.zope.org/zopetoolkit/process/releasing-software.html
> > though.
> >
> > The majority of packages still uses the "version='3.4.2dev'" scheme
> > for trunk or branches. Pointing to the next release to be made with a
> > dev marker.
> >
> > Are there any particular reasons, why this policy should be changed?
>
> I like "0" for two reasons:
>
> 1) it doesn't require predicting what the next release will be,

This is why I'd be happier if setuptools supported/sanctioned the
convention sometimes used in Debian: after releasing version 1.2.3 change
it in trunk to 1.2.3+svn.

It has the downside that you're explicitly naming the version control
system you happen to use, but *shrug*, it doesn't have to always be
"svn". Call it the 1.2.3+$vcs convention.

Currently I always assume the next release may be a tiny bugfix release,
so "1.2.3" becomes "1.2.4dev". If I commit something that adds a
feature or breaks an API, I can change it to "1.3dev" or "2.0dev".
I like that it gives me a reminder of the scope of the changes made
since the last release, but, since I'm not disciplined enough to always
update the version number and changelog along with a page, I prefer
reviewing the full diff before releasing to make sure they're up to
date.

> 3) [no] superfluous version bumps on the trunk

I don't understand this one. Could you elaborate?

> Amongst the reasons I like it are that:
>
> - when using a checkout as a develop egg you don't have to worry about finding
> out the exact version used on the trunk, you can always just use 0.

That's nice. I think I tried to use

[versions]
my-dev-package =

to force the regular "use latest" logic, but IIRC it didn't work well.

Marius Gedminas
--
http://pov.lt/ -- Zope 3 consulting and development

Attachments:

signature.asc (0.18 KB)

benji at zope

Sep 11, 2009, 6:53 AM

Post #2 of 6 (259 views)
Permalink

Re: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes [In reply to]

On Fri, Sep 11, 2009 at 9:07 AM, Marius Gedminas <marius[at]gedmin.as> wrote:
> On Thu, Sep 10, 2009 at 04:23:31PM -0400, Benji York wrote:
>> 3) [no] superfluous version bumps on the trunk
>
> I don't understand this one. Could you elaborate?

The current practice is that after doing a release you have to change
the trunk version to the next release number (a version bump).

>> - when using a checkout as a develop egg you don't have to worry about finding
>> out the exact version used on the trunk, you can always just use 0.
>
> That's nice. I think I tried to use
>
> [versions]
> my-dev-package =

Yeah, it'd be nice if buildout allowed that or some other syntax (like
"my-dev-package = *").
--
Benji York
Senior Software Engineer
Zope Corporation
_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )

marius at gedmin

Sep 11, 2009, 9:01 AM

Post #3 of 6 (256 views)
Permalink

Re: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes [In reply to]

On Fri, Sep 11, 2009 at 09:53:51AM -0400, Benji York wrote:
> On Fri, Sep 11, 2009 at 9:07 AM, Marius Gedminas <marius[at]gedmin.as> wrote:
> > On Thu, Sep 10, 2009 at 04:23:31PM -0400, Benji York wrote:
> >> 3) [no] superfluous version bumps on the trunk
> >
> > I don't understand this one. Could you elaborate?
>
> The current practice is that after doing a release you have to change
> the trunk version to the next release number (a version bump).

Right, but where does the "superfluous" come from? You'd have to change
it to 0 anywa...

Ah, I just realized that you do the version change on the branch/tag, so
trunk always stays at version 0.

(I don't do that out of principle that tags ought not to be modified;
and besides in other VCSes they can't be.)

> >> - when using a checkout as a develop egg you don't have to worry about finding
> >> out the exact version used on the trunk, you can always just use 0.
> >
> > That's nice. I think I tried to use
> >
> > [versions]
> > my-dev-package =
>
> Yeah, it'd be nice if buildout allowed that or some other syntax (like
> "my-dev-package = *").

Marius Gedminas
--
http://pov.lt/ -- Zope 3 consulting and development

Attachments:

signature.asc (0.18 KB)

faassen at startifact

Sep 11, 2009, 9:05 AM

Post #4 of 6 (256 views)
Permalink

Re: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes [In reply to]

Hey,

Marius Gedminas wrote:
> On Fri, Sep 11, 2009 at 09:53:51AM -0400, Benji York wrote:
>> On Fri, Sep 11, 2009 at 9:07 AM, Marius Gedminas <marius[at]gedmin.as> wrote:
>>> On Thu, Sep 10, 2009 at 04:23:31PM -0400, Benji York wrote:
>>>> 3) [no] superfluous version bumps on the trunk
>>> I don't understand this one. Could you elaborate?
>> The current practice is that after doing a release you have to change
>> the trunk version to the next release number (a version bump).
>
> Right, but where does the "superfluous" come from? You'd have to change
> it to 0 anywa...
>
> Ah, I just realized that you do the version change on the branch/tag, so
> trunk always stays at version 0.
>
> (I don't do that out of principle that tags ought not to be modified;
> and besides in other VCSes they can't be.)

That's an interesting point. So if we were to adopt another version
control system, the 0 policy wouldn't be much of a win anymore. Perhaps
Gary can tell us whether this would work with bzr?

(I think zest.releaser also does the version bumping before tagging if
I'm not mistaken, even with SVN.)

Regards,

Martijn

_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )

gary.poster at gmail

Sep 11, 2009, 10:56 AM

Post #5 of 6 (256 views)
Permalink

Re: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes [In reply to]

On Sep 11, 2009, at 12:05 PM, Martijn Faassen wrote:

> Hey,
>
> Marius Gedminas wrote:
>> On Fri, Sep 11, 2009 at 09:53:51AM -0400, Benji York wrote:
>>> On Fri, Sep 11, 2009 at 9:07 AM, Marius Gedminas
>>> <marius[at]gedmin.as> wrote:
>>>> On Thu, Sep 10, 2009 at 04:23:31PM -0400, Benji York wrote:
>>>>> 3) [no] superfluous version bumps on the trunk
>>>> I don't understand this one. Could you elaborate?
>>> The current practice is that after doing a release you have to
>>> change
>>> the trunk version to the next release number (a version bump).
>>
>> Right, but where does the "superfluous" come from? You'd have to
>> change
>> it to 0 anywa...
>>
>> Ah, I just realized that you do the version change on the branch/
>> tag, so
>> trunk always stays at version 0.
>>
>> (I don't do that out of principle that tags ought not to be modified;
>> and besides in other VCSes they can't be.)
>
> That's an interesting point. So if we were to adopt another version
> control system, the 0 policy wouldn't be much of a win anymore.
> Perhaps
> Gary can tell us whether this would work with bzr?

bzr supports a classic definition of tags--identifying a specific
revision. If it's of interest or help, I include the help text for
the "tag" command at the end of my message.

(The way we accomplish tagging in svn is by bringing our own semantics
to certain names, of course. svn doesn't help us do that inherently,
it's just convention. Because that's essentially a feature of being
able to name stuff, you can do similar tricks with bzr--I'd make a
branch for a tag if we were were following that pattern.)

Gary

$ bzr help tag
Purpose: Create, remove or modify a tag naming a revision.
Usage: bzr tag TAG_NAME

Options:
--force Replace existing tags.
-v, --verbose Display more information.
-h, --help Show help message.
-q, --quiet Only display errors and warnings.
-d ARG, --directory=ARG
Branch in which to place the tag.
--usage Show usage message and options.
-r ARG, --revision=ARG
See "help revisionspec" for details.
--delete Delete this tag rather than placing it.

Description:
Tags give human-meaningful names to revisions. Commands that take
a -r
(--revision) option can be given -rtag:X, where X is any previously
created tag.

Tags are stored in the branch. Tags are copied from one branch to
another
along when you branch, push, pull or merge.

It is an error to give a tag name that already exists unless you pass
--force, in which case the tag is moved to point to the new revision.

To rename a tag (change the name but keep it on the same revsion),
run ``bzr
tag new-name -r tag:old-name`` and then ``bzr tag --delete oldname``.

_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )

m.van.rees at zestsoftware

Sep 14, 2009, 5:43 AM

Post #6 of 6 (225 views)
Permalink

Re: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes [In reply to]

Martijn Faassen, on 2009-09-11:
> (I think zest.releaser also does the version bumping before tagging if
> I'm not mistaken, even with SVN.)

Correct.

These are the svn logs of releasing a demo package:

$ svn log -v file:///home/maurits/tmp/repo/demo/
------------------------------------------------------------------------
r5 | maurits | 2009-09-14 14:39:50 +0200 (ma, 14 sep 2009) | 1 line
Changed paths:
M /demo/trunk/CHANGES.txt
M /demo/trunk/setup.py

Preparing release 0.1
------------------------------------------------------------------------
r6 | maurits | 2009-09-14 14:39:55 +0200 (ma, 14 sep 2009) | 1 line
Changed paths:
A /demo/tags/0.1 (from /demo/trunk:5)

Tagging 0.1
------------------------------------------------------------------------
r7 | maurits | 2009-09-14 14:40:00 +0200 (ma, 14 sep 2009) | 1 line
Changed paths:
M /demo/trunk/CHANGES.txt
M /demo/trunk/setup.py

Back to development: 0.2dev

--
Maurits van Rees | http://maurits.vanrees.org/
Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]

_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com