Dmitry Timoshkov wrote:
> "TheBlunderbuss" <[EMAIL PROTECTED]> wrote:
>
> [skipped]
>
>
>> This level of security info is something everyone should have easy
>> access to and know before starting Wine. Of course, wherever I'm not
>> accurate, feel free to fill in!
>>
> There is nothing spec
"TheBlunderbuss" <[EMAIL PROTECTED]> wrote:
[skipped]
> This level of security info is something everyone should have easy
> access to and know before starting Wine. Of course, wherever I'm not
> accurate, feel free to fill in!
There is nothing special about Wine that doesn't apply to common
uni
There should be documentation in place
beyond a simple entry in the appdb, since you all know as well as I do
that the database does not and cannot cover every piece of software out
there. For the most part, people don't even know it exists or they
don't use it.
There will be documentation
Hi,
I was trying to look at www.cxtest.org but the site seems not to work.
Can this be fixed?
Cheers,
Maarten.
On Sat, Mar 15, 2008 at 6:06 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> <[EMAIL PROTECTED]> wrote:
> > 6254 had a proposed fix from Tony Rollo, and was worked on both Lai
> > Zhang and myself. Can I send the proposed patch to the dev list for
> > review? The patch fixes the problem stated.
<[EMAIL PROTECTED]> wrote:
> 6254 had a proposed fix from Tony Rollo, and was worked on both Lai
> Zhang and myself. Can I send the proposed patch to the dev list for
> review? The patch fixes the problem stated.
Lei, feel like resubmitting
http://winehq.org/pipermail/wine-patches/2007-June/0
Dan Kegel wrote:
> Per http://wiki.winehq.org/WineReleasePlan,
> in early May, Wine's trunk will go into code freeze,
> and only small, obvious bugfixes will be accepted.
>
> Now might be a good time to start winding down
> development, and switching to cleaning up loose ends.
>
> http://bugs.wineh
On Sat, Mar 15, 2008 at 6:25 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> That's not as hard as it sounds.
> You might consider adapting existing automated installer
> scripts such as the ones at http://wpkg.org/ or
> http://unattended.sourceforge.net/
>
> There are surely dozens of apps that ar
Dan Kegel wrote:
> On Sat, Mar 15, 2008 at 11:04 AM, Alexandre Julliard
> <[EMAIL PROTECTED]> wrote:
>
>> > http://wiki.winehq.org/WineReleasePlan
>>
>> We need a code freeze and stabilization period before the release. My
>> thinking is that we should have a 1.0rc1 release, probably sometime
On Sat, Mar 15, 2008 at 3:52 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> If you can provide an automated test case for your
> favorite platinum app, so that we can just run it without
> any manual work, I'll gladly add it to the list.
That's not as hard as it sounds.
You might consider adapting
Per http://wiki.winehq.org/WineReleasePlan,
in early May, Wine's trunk will go into code freeze,
and only small, obvious bugfixes will be accepted.
Now might be a good time to start winding down
development, and switching to cleaning up loose ends.
http://bugs.winehq.org/buglist.cgi?query_format=
On Sat, Mar 15, 2008 at 3:35 PM, Remco <[EMAIL PROTECTED]> wrote:
> What about growing the list with a few applications that work perfectly at
> the moment (such as the top 10 platinum rated apps)?
The problem with expanding the list is that each new app
adds a huge amount of testing to each rel
- Original Message
> From: Dan Kegel <[EMAIL PROTECTED]>
> I've updated http://wiki.winehq.org/WineReleaseCriteria
> to be a bit more final.
>
> I've also written a draft release plan; see
> http://wiki.winehq.org/WineReleasePlan
>
> Comments?
Please note that I'm not complaining, but
Michael Stefaniuc <[EMAIL PROTECTED]> writes:
> Alexandre Julliard wrote:
>> We need a code freeze and stabilization period before the release. My
>> thinking is that we should have a 1.0rc1 release, probably sometime in
>> May, and from that point on only accept small obvious fixes. Then we'd
> W
"Dan Kegel" <[EMAIL PROTECTED]> writes:
> On Sat, Mar 15, 2008 at 11:04 AM, Alexandre Julliard
> <[EMAIL PROTECTED]> wrote:
>> > http://wiki.winehq.org/WineReleasePlan
>>
>> We need a code freeze and stabilization period before the release. My
>> thinking is that we should have a 1.0rc1 release
Michael Stefaniuc <[EMAIL PROTECTED]> wrote:
> > thinking is that we should have a 1.0rc1 release, probably sometime in
> > May, and from that point on only accept small obvious fixes. Then we'd
> What about small janitorial patches?
If they have low risk, and are obvious, they might well go in
Alexandre Julliard wrote:
> "Dan Kegel" <[EMAIL PROTECTED]> writes:
>
>> I've updated http://wiki.winehq.org/WineReleaseCriteria
>> to be a bit more final.
>>
>> I've also written a draft release plan; see
>> http://wiki.winehq.org/WineReleasePlan
>>
>> Comments?
>
> We need a code freeze and sta
On Sat, Mar 15, 2008 at 11:04 AM, Alexandre Julliard
<[EMAIL PROTECTED]> wrote:
> > http://wiki.winehq.org/WineReleasePlan
>
> We need a code freeze and stabilization period before the release. My
> thinking is that we should have a 1.0rc1 release, probably sometime in
> May, and from that poin
"Dan Kegel" <[EMAIL PROTECTED]> writes:
> I've updated http://wiki.winehq.org/WineReleaseCriteria
> to be a bit more final.
>
> I've also written a draft release plan; see
> http://wiki.winehq.org/WineReleasePlan
>
> Comments?
We need a code freeze and stabilization period before the release. My
Dan Kegel wrote:
> I've updated http://wiki.winehq.org/WineReleaseCriteria
> to be a bit more final.
>
> I've also written a draft release plan; see
> http://wiki.winehq.org/WineReleasePlan
>
> Comments?
>
>
>
+1 to the release plan.
James McKenzie
Dmitry Timoshkov wrote:
> "James McKenzie" <[EMAIL PROTECTED]> wrote:
>
>> Dan Kegel wrote:
>>> On Wed, Mar 12, 2008 at 5:11 PM, jingo811
>>> <[EMAIL PROTECTED]> wrote:
>>>
So I was wondering can you give me an ordered to-do-list in
becoming a Code Monkey for WineHQ?
I'm trying to implement the D3DXGetImageInfoFrom* functions in d3dx8/9 dlls,
and I have a few questions.
As there is no related source file from this kind of functions, I created
texture.c within dlls/d3dx8. I guess this is the way you want it, but I'd
like to hear it from you.
Then I need li
On Fri, Mar 14, 2008 at 11:11 PM, Maarten Lankhorst
<[EMAIL PROTECTED]> wrote:
> > Given each application tends to have different results depending on
> > which version of Wine is emulated, the solution to me seems that there
> > should be a default set like now, such as XP and then the Desktop
>
I've updated http://wiki.winehq.org/WineReleaseCriteria
to be a bit more final.
I've also written a draft release plan; see
http://wiki.winehq.org/WineReleasePlan
Comments?
On Wed, Mar 12, 2008 at 10:13:42AM +1100, Alistair Leslie-Hughes wrote:
> Can I please get Privs on Bugzilla to help with the msxml work I am doing?
done.
Jan
> However, it is true that we should tell users that Wine is
> able to run many Windows malware, and that they
> should be just as careful running Windows software
> with Wine as they would running it with Windows.
> We should also show how to install the standard
> Linux virus checkers.
> -
Dear Sir/Madam,
appologies I have lost my password etc but would be greatful if
you could see a way to remove me from current thread as my inbox is constantly
filling up with stuff, originally about microsoft dll's, that I really do not
understand. Many thanks.
Roy.
--
Huw Davies <[EMAIL PROTECTED]> writes:
> fonts/Makefile.in |1 +
> fonts/symbol.sfd | 83
> +
Upgrading fontforge fixed the gdi32 errors, but now I'm getting errors
in usp10:
../../../tools/runtest -q -P wine -M usp10.dll -T ../../.. -p
28 matches
Mail list logo
