Ros-dev October 2007

ros-dev@reactos.org

30 participants
45 discussions

Re: [ros-dev] ReactOS Development Process

by Aleksey Bragin

I considered that, but it's a bad idea. Try to remember what the hell it was to merge changes into release branch ("stable"), done since 0.3.3-RC1 was released? And that was only to do a RC2, about 1-2 weeks, and complete hell to merge so it was decided that a rebranch was easier (and in fact it worked very well). WBR, Aleksey Bragin. On Oct 3, 2007, at 9:03 PM, Magnus Olsen wrote: > Hi > I think we should have something call stable trunk and devloping trunk > > The stable trunk getting all changes that are ready and stable and > it will > be > the release version of trunk. > > the devloping trunk is where everyone working in > > > But the main problem is we do not have any good tools for regress > testing > and we are missing testcase for each api. I am working at moment > writing > testcase for gdi32, I hope this will make lest gdi32 allot more > stable at > end > then I will start making testcase for win32k later maybe for user32 > then start fixing the real bugs and implement things. or working with > everthing same times. we should need a test kit for each api and > test for evertging invaild param, pointers, and real data in all case > I known it is not fun todo but that is what we need to make ReactOS > more stable and less bugs. Testcase for everthing.

18 years, 1 month

Re: [ros-dev] ReactOS Development Process

by Aleksey Bragin

Herve suggests using a kind of a continuous integration system, describing it this way: * precommit hook if commit not to trunk, abort precommit hook create a REV-abc branch from trunk and do the commit here * regularly go through all REV-abc branches (increasing ABC numbers) test it if not, inform user or whatever that test failed and go to next branch try to merge to trunk if not, inform user or whatever that merge failed and go to next branch commit to trunk delete the branch go to next branch * pros: devs and users will have new version to trunk once they are tested devs and users only have to know trunk * cons: changes are not immediatly available for everyone, except in REV-abc branch On Oct 3, 2007, at 12:50 PM, Aleksey Bragin wrote: > Hello, > recently, different people raised a question: How should development > process evolve with time, when ReactOS has more (much more) > developers willing to contribute code?

18 years, 1 month

Bugzilla error when sending notifications

by Marc Piulachs

I'm getting this error when posting/modifying a bugreport Bugzilla has suffered an internal error. Please save this page and send it to aleksey(a)reactos.org with details of what you were doing at the time this message appeared. URL: http://www.reactos.org/bugzilla/process_bug.cgi There was an error sending mail from 'ReactOS.Bugzilla' to 'hpoussin(a)reactos.org':error when closing pipe to /usr/lib/sendmail:

18 years, 1 month

Re: [ros-dev] [ros-diffs] [hpoussin] 29352: Do not hardcode cdrom directory

by Pablo Menichini

> --- trunk/reactos/base/setup/usetup/drivesup.c (original) > +++ trunk/reactos/base/setup/usetup/drivesup.c Tue Oct 2 16:16:45 2007 > @@ -35,7 +35,8 @@ ... > + if (Ptr) > + RtlCreateUnicodeString(SourceRootDir, Ptr); > + else > + RtlCreateUnicodeString(SourceRootDir, L""); > + > if (Ptr != NULL) > - *Ptr = 0; > - > + *Ptr = 0; You can put *Ptr = 0 in the if-else Pablo

18 years, 1 month

SmartPDF (aka SumatraPDF) in rosapps, linking problems

by Klemens Friedl

SumatraPDF is a lightweight Win32 pdf viewer app http://blog.kowalczyk.info/software/sumatrapdf/ http://code.google.com/p/sumatrapdf/ The name "sumatra" sounds weird (for an app), so I renamed the directory and the output exe file to "SmartPDF" (based on suggestions from #reactos). SumatraPDF comes with VS 2k5 project files. I have fixed various compile issues so that libjpeg, poppler, fitz/mupdf and sumatra app itself compile without errors in mingw (RosBE 0.3.7.2 Win32). All code changes can be found by grep/search for "@note:", I added a comment to each changed code line. The remaining problem is the linking issue. Currently it does NOT link correctly. Timo Kreuzer mentioned on 2007-09-27 in #reactos something that may be related to the issue: "it [sumatrapdf] imports a function from winspool.drv by number, when you add that number to winspool.def, it starts" Please have a look at it, fixes are appreciated :) Klemens

18 years, 1 month

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev October 2007