On Sat, 2007-09-22 at 21:42 -0600, Andy Korvemaker wrote:
> Just quickly touching base on this again. Is a few hours of my time
> tomorrow helpful?
Always!
> If so: Can someone give me a few pointers? How should I be marking bugs
> that need to be fixed for 2.6? Is there any particular criteria I should
> use, or should I just take my best guess?
Any bug that has a reasonable chance of begin triggered that could cause
a crash or dataloss should be top priority, or even a blocker IMO. For
the rest: best guess ;)
Marc
> Andy
>
> On Tue, 18 Sep 2007 10:16:37 -0600, "Andy Korvemaker"
> <abiword@andyland.ca> said:
> > I could spend about 3-4 hours helping this Sunday afternoon/evening (in
> > western Canada time: GMT -7h, I think), but I'd need someone to give me
> > some guidelines and instructions. I've done little work
> > confirming/testing bugs in the past.
> > I'm running on Mac OS X. I *might* be able to access a Windows XP
> > machine too.
> >
> > If I can be of help, let me know.
> >
> > Andy
> >
> > On Tue, 18 Sep 2007 14:42:44 +1000, "Martin Sevior"
> > <martines@unimelb.edu.au> said:
> > >
> > > Hi folks,
> > > Now that we've decided to push for 2.6 release, we need to
> > > decide how good svn trunk is in order to make a 2.6 release.
> > >
> > > To do this we need to locate the bugs that need fixing before we release
> > > 2.6.
> > >
> > > Can we organise people to identify a collection of bugs that need fixing
> > > in order to make a 2.6 release?
> > >
> > > Once we have such a list developers can focus their energies on fixing
> > > the bugs.
> > >
> > > Can we have volunteers for this please?
> > >
> > > Thanks!
> > >
> > > Martin
> > --
> > Andy Korvemaker
> > http://andyland.ca
> >
Received on Sun Sep 23 16:46:42 2007
This archive was generated by hypermail 2.1.8 : Sun Sep 23 2007 - 16:46:43 CEST