unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
* Items blocking release 1.6.1 (2002-04-21)
@ 2002-04-21 16:22 Rob Browning
  2002-04-22  8:35 ` Thien-Thi Nguyen
  2002-04-22 18:04 ` Marius Vollmer
  0 siblings, 2 replies; 25+ messages in thread
From: Rob Browning @ 2002-04-21 16:22 UTC (permalink / raw)



Since I've had no negative feeback regarding my release management
posts, I'm planning to add those to our policy documentation and
proceed accordingly.

If you haven't read those messages yet, please do, but the summary is
that the stable TODO section and the bugs tagged release critical
represent the *complete* set of items holding up the release, and you
should not change this set after the stable release has branched
without discussing it with the release manager first (i.e. me).

Whenever we're near a stable release, I'll be posting this "blocking
list" on a regular basis as a reminder.  NOTE: if you're working on
something that's listed below, please contact me.  If your bit is not
in the TODO or bugs and marked appropriately, I may release without
it.

Items currently listed as holding up the 1.6 release are listed below.
More information needed from: [mvo], [ttn].

(The bugs listed as belonging to me I can fix in a day, so please
don't wait on me.)

(1) bugs/optargs-bound-gone [mvo?]

  Marius: you discussed a fix for this in email, but also mention that
  it's functionality is fairly easily worked around via default value
  -- so are we fixing it for 1.6, or are we adding a NEWS entry
  recommending the alternative approach?  If we are fixing it, and if
  you can describe the fix, I can do the work.

(2) bugs/intructions-to-distributors [rlb]

  I'll handle this one -- I'll either have full fledged instructions
  by the release, or I'll include some information and a request for
  packagers to contact guile-devel before packaging.  This will depend
  on how far I get before all the other release critical bugs are
  finished.

(3) tasks/TODO - document libtool conventions [rlb]

  Needs to be done -- will do.

(4) tasks/TODO - convert bug tracking/summarization process

  Is this really 1.6 release critical?  It seems like it could be
  moved to a 1.8 section or "Eventually" to me, but I may be missing
  something.  For 1.6, it seems like we can easily just create copy
  BUGS by hand if this is likely to hold things up any longer.

(5) tasks/TODO - write build/bugs-triage.text
               - complete build/stability.text [ttn]
               - make sure all bugs have required headers

  Are these really 1.6 release critical?  I'm inclined to want to move
  these to the 1.8 section as well.  While I think these improvements
  are important, and should certainly be finished by 1.8, they don't
  seem like anything that can't wait until 1.6.2, etc.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD


-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


^ permalink raw reply	[flat|nested] 25+ messages in thread
* Re: Items blocking release 1.6.1 (2002-04-21)
@ 2002-04-22 20:05 Thien-Thi Nguyen
  2002-04-22 20:15 ` Rob Browning
                   ` (2 more replies)
  0 siblings, 3 replies; 25+ messages in thread
From: Thien-Thi Nguyen @ 2002-04-22 20:05 UTC (permalink / raw)
  Cc: rlb, guile-devel, guile-user

   From: Marius Vollmer <mvo@zagadka.ping.de>
   Date: 22 Apr 2002 20:44:36 +0200

   [ice-9/optargs.scm bound? removal]

   Ok, I'll looker closer into this, and I now have to say that we can't
   'fix' it.  We would be changing the default default value from '#f'
   to something else.  That would be an unacceptable interface change.

but removing `bound?' is acceptable?

   Since it is easy for the user to provide the functionality on its
   own, we can just leave it as it is.

to provide out of band info, you can use out of band methods (in fact,
this is the fix i thought you were going to consider).

cc'ing guile-user to see who complains (besides me).  maybe someone can
send a patch to do a clean fix, and explain it.  maybe it's time to fork
guile (again).

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


^ permalink raw reply	[flat|nested] 25+ messages in thread

end of thread, other threads:[~2002-05-07 18:43 UTC | newest]

Thread overview: 25+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-04-21 16:22 Items blocking release 1.6.1 (2002-04-21) Rob Browning
2002-04-22  8:35 ` Thien-Thi Nguyen
2002-04-22 13:02   ` Rob Browning
2002-04-22 18:04 ` Marius Vollmer
2002-04-22 18:26   ` Rob Browning
2002-04-22 18:44   ` Marius Vollmer
2002-04-22 18:56     ` Rob Browning
  -- strict thread matches above, loose matches on Subject: below --
2002-04-22 20:05 Thien-Thi Nguyen
2002-04-22 20:15 ` Rob Browning
2002-04-22 20:52   ` Thien-Thi Nguyen
2002-04-22 21:12     ` Rob Browning
2002-04-22 21:25       ` Rob Browning
2002-04-22 21:30         ` Rob Browning
2002-04-22 21:51       ` Thien-Thi Nguyen
2002-04-22 23:03         ` Rob Browning
2002-04-22 20:29 ` Bill Gribble
2002-04-22 21:20   ` Thien-Thi Nguyen
2002-04-23 18:16 ` Marius Vollmer
2002-04-25  9:09   ` tomas
2002-04-25 10:02     ` rm
2002-04-28 16:00       ` Marius Vollmer
2002-04-28 20:27         ` Thien-Thi Nguyen
2002-05-07 18:43           ` Marius Vollmer
2002-04-28 15:58     ` Marius Vollmer
2002-04-28 20:38       ` spu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).