Am Freitag, den 14.10.2005, 16:29 +0200 schrieb Molle Bestefich:
> Why not do this:
> Accept the patches into trunk, and do the "code freeze" in a branch.
>
> Cons:
> - Can't think of any?
Most Developer are doing the same as before: Working on there Patches.
The Code-Freeze and the Stabilisa
[I can the rest ... there is just one real point I need to make here.]
> I'm saying that from a newcomers fantastically objective POV, there
> might be a more efficient way than what everybody here's used to. And
> I do appreciate that you take time to tell me why I'm wrong. Thanks!
We work thi
On Fri, 14 Oct 2005, Molle Bestefich wrote:
[...]
Ok, maybe there's one. You need a release manager to pick which
patches gets in the RC / release.
But there must be a million ways of doing that automatically, besides
from having an actual release manager. Script your way out of it.
Automatica
Hi,
On Fri, Oct 14, 2005 at 08:51:06AM -0600, Vitaliy Margolen wrote:
> Again that's not in my power to decide. But I would say - not a good time to
> branch Wine. It's not stable enough to have "stable" and "development"
> branches.
> All fixes are important. And lots of fixes are additional fea
> > Why not do this:
> > Accept the patches into trunk, and do the "code freeze" in a branch.
> > Pros:
> > - Developers of patches will not get pissed (ahem) for their stuff not
> > getting in.
>
> In the open source world, anyone submitting
> a patch has to count on patiently resubmitting it
Friday, October 14, 2005, 8:29:19 AM, Molle Bestefich wrote:
> Vitaliy Margolen wrote:
>> > You're rejecting a perfectly fine patch to Wine, because
>> > it's the wrong season of the year to send good patches?
>> I have no power to accept nor reject path. All I'm trying to say, is that
>> right
>>
Molle Bestefich wrote:
>Why not do this:
> Accept the patches into trunk, and do the "code freeze" in a branch.
>
>Pros:
> - Developers of patches will not get pissed (ahem) for their stuff
>not getting in.
> - Development doesn't stop just every time a release is coming up.
> - Developers can ac
Molle Bestefich wrote:
> Pros:
> - Developers of patches will not get pissed (ahem) for their stuff
> not getting in.
> - Development doesn't stop just every time a release is coming up.
> - Developers can actively select whether they'd like to help with the
> release (switch to '0.9-rc' branch)
Vitaliy Margolen wrote:
> > You're rejecting a perfectly fine patch to Wine, because
> > it's the wrong season of the year to send good patches?
> I have no power to accept nor reject path. All I'm trying to say, is that
> right
> now (Oct 14 2005) Wine is in a "code freeze" (see announcement abou
Friday, October 14, 2005, 5:24:40 AM, Molle Bestefich wrote:
> Vitaliy Margolen wrote:
>> 2. This is not a good time for this changes (code freeze is still in affect).
>>
>> Find some bugs in bugzilla to fix
> I'm getting a sick feeling to my stomach here.
> Maybe I'm just misunderstanding things
On 10/14/05, Molle Bestefich <[EMAIL PROTECTED]> wrote:
> Vitaliy Margolen wrote:
> > 2. This is not a good time for this changes (code freeze is still in
> affect).
> >
> > Find some bugs in bugzilla to fix
>
> I'm getting a sick feeling to my stomach here.
> Maybe I'm just misunderstanding thing
Molle Bestefich wrote:
I'm getting a sick feeling to my stomach here.
Maybe I'm just misunderstanding things?
You're rejecting a perfectly fine patch to Wine, because
it's the wrong season of the year to send good patches?
People tell me that Wine are always two steps behind.
Doesn't surp
Vitaliy Margolen wrote:
> 2. This is not a good time for this changes (code freeze is still in affect).
>
> Find some bugs in bugzilla to fix
I'm getting a sick feeling to my stomach here.
Maybe I'm just misunderstanding things?
You're rejecting a perfectly fine patch to Wine, because
it's the w
Le jeudi 13 octobre 2005 à 21:29 -0400, Robert Reif a écrit :
> I guess I could have split it up into half a dozen patches.
>
> This is something I needed for work so I took the opportunity to
> do some wine hacking. I'm way to busy to do much more than
> just reading the mailing lists now and I
Vitaliy Margolen wrote:
1. Don't send patches in gz - only plain text is accepted here. ;)
2. This is not a good time for this changes (code freeze is still in affect).
Find some bugs in bugzilla to fix
Vitaliy.
I guess I could have split it up into half a dozen patches.
This is something
Thursday, October 13, 2005, 6:06:33 PM, Robert Reif wrote:
> Add DirectSoundFullDuplex support.
> This patch is rather large because it was necessary to refactor the
> existing code so it could be used by the full duplex code. Most of
> the changes are either changing all the cod
16 matches
Mail list logo
