Christopher Lenz wrote:
> Am 01.04.2007 um 22:23 schrieb Christian Boos:
>   
>> ... So I moved those changes  
>> on a
>> stabilization branch, and as a result the trunk was indeed usable  
>> again
>> but the branch has stalled...
>>     
>
> FYI, I consider it bad style to move someone else's changes to a  
> "stabilization branch" without any kind of notice or dicussion on  
> this list. 

One can consider equally bad style to break the relative stability of 
trunk without any kind of notice or discussion on the list as well.

> I've put a lot of work into those changes, and while I may  
> have missed some places, it would've been better to just fix those --  
>   

Like in "after me the deluge?" ... Well, frankly I had no idea of the 
extent of the changes required, and I didn't want to take the burden to 
clean up the mess after everything went loose. It's true that normally I 
tend to take care of such details, but at that time I was quite busy 
with other things (resync fixes), and didn't want to get distracted. If 
you had brought up the issue on the list in the first place, I would 
have got the chance to raise this timing issue.

> instead of the current situation, which is frankly obnoxious (relying  
> on a version of a dependency that's neither release *nor* trunk).
>   

True. That's also why I wanted that we stick to 0.3.6 until 0.4 would 
get released.

>> So what I'd like to do instead is to release a 0.11beta1, as trunk
>> stands now, and let people know that they should use this if they want
>> to try out 0.11dev, because the trunk will become temporarily quite
>> "unstable". We'll then merge genshi510, then the workflow branch. One,
>> two, three weeks later at most, things will have settled down again  
>> and
>> trunk will recover its "usable" status.
>>     
>
> Huh? That's not a beta. You can't postpone major changes like the  
> addition of workflow to after a beta release. Either such changes are  
> postponed to the next release, or the beta needs to wait until  
> they're in. Anything else is not sane release management in my book.
>   

Well, good points. So what do we do now? Put in bold letters that trunk 
will get a bit unstable in the coming days?

-- Christian

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to