Bryce Harrington schrieb:
On Sat, Nov 03, 2007 at 08:27:09PM -0400, Gail Carmichael wrote:
Bryce Harrington wrote:
If everyone's cool with the plan, we could shoot for going into Chill a week or two from now, and see how things go from there.
I know for myself, being in grad courses right now, December was going to be a big time for me to work on refactoring my patch to be committed. If you guys want to chill before then, I suggest maybe checking in what I have done so far, and I can then check in the refactored version once it's done into the branch. I'd like to say that I could push to have it done sooner, but I know it's not realistic given the number of projects I have been working on.
I'm fairly certain we'll be at Chill by December; I'm hoping this gives folks the holidays to squash bugs and do testing. So I'd say if you feel your patch is stable and something you definitely think needs to be in for 0.46, to get it in asap.
I'm probably in a situation similar to Gail's right now. One of my four final examinations will be next Monday (Nov 12). I'm trying to get my loose ends (w.r.t. Inkscape :) ) tied up right now, but I won't be able to spend more than a few hours until then. Afterwards, the schedule is probably going to relax a bit (not much, though :( ) for two or three weeks so that I can try to get the major part of the reworked 3D box tool finished and checked in. Like Gail I was hoping to have until early December for this (I believe this tentative date was mentioned in an earlier post), but I really want to try to get it done even if Chill starts earlier.
It's hard to say if the time will be sufficient, but would you be willing to wait until the end of next week before announcing Chill? It should be clear by then if I can manage to bring my stuff in. Of course, only if it wouldn't mix up the entire schedule.
On the other hand, regarding your description ...
- Chill. Development focuses on wrapping up. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs
... I'm wondering what precisely "Development focuses on wrapping up" means? Does it mean that there must not be any commits above a certain "size"? Or does it just mean that all developers should try to smooth out the existing stuff, eliminate bugs, etc. instead of implementing new features, but any code changes can still occur as required? I'm asking because in my case "wrapping up" does involve major changes (code-wise). This would result in one or more large commits. But except for some non-critical (mostly GUI-related) stuff it would only touch files I created myself, and since all the code is fairly orthogonal to the rest of the program, there shouldn't be a problem - if it doesn't work as intended or introduces too many bugs (in which case I would refrain from committing it in the first place :) ), it is simply excluded from the release branch later on. Or does something like this completely contradict the nature of Chill? Sorry for this probably dumb question but I'd like to know how much I need to hurry up if I want my stuff to hit this release.
Thanks, Max