sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
- From: Dufflebunk <dufflebunk AT dufflebunk.homeip.net>
- To: "Jeremy A. Kolb" <jkolb AT brandeis.edu>
- Cc: sm-discuss <sm-discuss AT lists.ibiblio.org>
- Subject: Re: [SM-Discuss] bug fix question
- Date: Thu, 04 Sep 2003 21:28:38 -0000
When a bug is fixed, it's usually fixed in both devel and test in
perforce if it's just a simple bug. If it's a more involved problem that
might break things, the fix goes into devel, and the section maintainers
moves the stuff from devel to test when it's working... could take
anywhere from a day to a week (or a month if it's got anythign to do
with open office ;) ...
The only time you should see a message in bugzilla about somethign being
fixed but only available in devel is if the section guru is unsure about
bad side effects with other stuff.
At least, this is my understanding, but I'm not in the grimoire team.
On Thu, 2003-09-04 at 17:15, Jeremy A. Kolb wrote:
> Hey all, since we've talking about bug fixes and devel/test I have a
> question. When a fix has been submitted to perforce how long does it take
> to get into test? Is a new 'test' automatically generated or is it just in
> the next release whenever that is? Who actually sanctions the move? I'm
> just curious and I haven't checked the wiki so if it's there then sorry
> just ignore this. But I am curious as to how this process works.
>
> Jeremy
>
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
-
[SM-Discuss] bug fix question,
Jeremy A. Kolb, 09/04/2003
- Re: [SM-Discuss] bug fix question, Dufflebunk, 09/04/2003
-
Re: [SM-Discuss] bug fix question,
Eric Sandall, 09/04/2003
-
Re: [SM-Discuss] bug fix question,
Jason Flatt, 09/05/2003
- Re: [SM-Discuss] bug fix question, Ladislav Hagara, 09/05/2003
-
Re: [SM-Discuss] bug fix question,
Jason Flatt, 09/05/2003
Archive powered by MHonArc 2.6.24.