 |
 |
Hi Brian, Dirk, it's a good idea but it is quite difficult to predict what sort of bugs we will find. So this is what I would like to achieve (Geneva time): * 04.10 - rc1 * 04.10 - 10.10 - testing and fixing bugs found in -rc1 * 10.10 - rc2 * 10.10 - 17.10 - testing and fixing bugs found in -rc2 * 17.10 - 3.1.0 gets built Lukasz 2011/10/3 Dirk Duellmann <[log in to unmask]>: > Hi Brian, > > +1 from me. > > We discussed this already a few times and I think even a monthly updated schedule > could help to watch the planning from inside and outside the project. Unfortunately > so far the several web improvements we discussed in the monthly calls were suppressed > by other important work, but an update once a month eg before/after the "monthly" project > call might be good. > > Cheers, Dirk > > > > > On 3 Oct 2011, at 14:56, Brian Bockelman wrote: > >> Hi Lukasz, >> >> Can you fill in the release timeline? I.e., any bug reports need to be in by date X, any RC fixes need to be in by date Y, release is set for date Z. Condor actually keeps a Google calendar that I find useful... >> >> As I timeshare between projects, knowing the next few week's schedule helps me set my own priorities. >> >> Brian >> >> On Oct 3, 2011, at 2:06 AM, Lukasz Janyst wrote: >> >>> OK, so is everyone ready? Gerri you mentioned that you still have some >>> commits but I haven't seen any from you recently... >>> >>> Cheers, >>> Lukasz >> >> > >