guile-gtk-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HEADS UP: pending guile-gnome changes require HEAD G-Wrap


From: Andreas Rottmann
Subject: Re: HEADS UP: pending guile-gnome changes require HEAD G-Wrap
Date: Thu, 14 Apr 2005 16:43:03 +0200
User-agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.4 (gnu/linux)

[CC'ed guile-gtk-general]

Greg Troxel <address@hidden> writes:

> It would be cool for you to sequence this such that you don't need
> HEAD g-wrap.  It has been a bit awkward for me to use guile-gnome in a
> project due to this sort of thing.  I'm using releases of both, so
> this doesn't bother me now, but I think it would be good for the
> projects in terms of others being willing to use it to be more hard
> core about release engineering issues.  Specifically:
>
>   Don't depend on unreleased tools versions.
>
OK, I can see this might be a hassle when someone's working from
guile-gnome HEAD, but doesn't want to install a HEAD G-Wrap. I can see
the following rule being acceptable:

* Changes made (merged into) the master archive must not introduce
  dependencies on unreleased tool versions. 

  In this concrete case, this would have meant I would have tested the
  changes in my private archive, released a new G-Wrap version and
  after that pushed changes into the master archive, along with a
  HEADS-UP message. Sounds OK?

>   All releases from official repositories - not from private ones.
>
I already pestered Wingo about this. He was opposed to doing that
since he can't "lock" the master archive during release as opposed to
his private one. IIRC, he said the two possibilities would be either
using release branches on the master archive, or using his private
archive. I don't think either is inherently superior, since his
archive is public, and I think using a private archive is more
convinient than dealing with the (many) release branches in the master
archive. 

We agreed, however, that the person doing the release would push all
changes made to the release branches (in this case in his private
archive) back to the master immediatly after doing the actual release.

>   Clarity about this in NEWS, README, download pages etc.
>
Could you elaborate a bit what information specifically you want to
have in these places?

Regards, Rotty
-- 
Andreas Rottmann         | address@hidden      | address@hidden | address@hidden
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62
v2sw7MYChw5pr5OFma7u7Lw2m5g/l7Di6e6t5BSb7en6g3/5HZa2Xs6MSr1/2p7 hackerkey.com

Any technology not indistinguishable from magic is insufficiently advanced.
   -- Terry Pratchett




reply via email to

[Prev in Thread] Current Thread [Next in Thread]