10.03.2013 22:48, Julius Schwartzenberg пишет: > Stas Sergeev wrote: >> Have you already filled the bug report with all the >> needed attachments to reproduce the problem? > No not yet, I wasn't sure whether I should do this for the current GIT > as well. Is the current version in GIT indeed considered to be stable > enough for testing? Testing against git is the most important thing in every project. If you by chance report a bug that is already known or already worked on, this is not a big problem at all, compared to the importance of testing git. And it is not very likely to happen, esp if you test "master" branch. Now we have "devel" branch for unstable things, and before that I was creating a separate branches for every new sub-project. People usually refrain from committing the unstable things to master, so master is always "stable enough" for doing some public testing. And if it is not, then we'd need to fix ourselves, not our testers. :) At this point of time, however, "devel" should be stable enough for public testing too. I guess Bart is afraid of merging it simply because no one tested it for regressions.
> Just in case, my initial e-mail should contain enough information to > reproduce both problems if I didn't forget anything. Yes but no one will look it up in an ML archieve a month later. Note that I haven't analized your particular problem. This is just a janitorial task of reminding people to open bug reports. :) ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
