Jens Hatlak wrote:
Daniel wrote:
Jens Hatlak (SM Dev team) now seems to want me to start a separate Bug
for this Windows problem (as distinct to the Mac's problem), so knowing
the release/time frame is handy.
Handy maybe, but certainly not required to get started. The first thing
to do once a problem has been verified would be to create a bug. Then
everyone has a place to store and update additional information such as
attachments, analyses, and findings.
[After all, identifying the release that first introduced an issue is
only the first step anyway. What we really need is regression windows
down to the day, and that you only get with nightly builds. If the bug
reporter can provide that level of detail it's fine. But it's also OK if
not.]
HTH
Jens
Gee, tempting, Jens, tempting!!
Where might I d/l the Win x64_86 nightly's from??
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101
Firefox/25.0 SeaMonkey/2.22 Build identifier: 20131023190953
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101
Firefox/25.0 SeaMonkey/2.22 Build identifier: 20131023190942
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
