Hi, > I am not familiar with the Apache requirements for a project. From > what I understand, there have to be reports filed every three month. > What else? How can we proceed with the limited resources, we have?
> The reports every 3 months shouldn't be a big problem, but you need > to do e.g. votes for releases as well, they need to be signed off > and we currently don't even have a mentor signing off our incubator > reports and such. > > You want details? :-) > > http://incubator.apache.org/guides/releasemanagement.html wow! I am going to read this on the weekend. That will probably be much fun. ;-) > If binary releases are not a must for Apache, which I didn't know > before, in my opinion we should simply reduce to a source release > and don't even care about the build tools too much. If things > don't work as they are, people will create tickets in JIRA and > hopefully provide patches. cpptasks for our ant based build is not > maintained anymore, so I would suggest to cut it off with autoconf > for non-Windows and documentation and maybe template project files > in some "contrib" for Windows. Source only releases sound good to me, and the build process should be held as simple as possible too. One of my problems with log4cxx has always been, that there had been multiple ways to build the project and all had there flaws on our platform (Windows/Visual Studio). log4cxx need one well documented cross platform build process. Last time I dug into autotools (at least ten years ago), they already appeared to be overly complicated. Ant/Maven seemed to be a relict from log4j and needs a Java environment only to build a c++ library. What do you think about changing to cmake? That should work on Linux, Windows and Mac OS. > I don't know how others work, but with my Windows-IDE I need to > create custom projects all the time for various reasons. What do you need these custom projects for? Testing within VS? > But in the end it all boils down to if someone will follow the > official release process. Yes, but first, we have to keep log4cxx out of the Attic. And it might be easier to deal with details (e.g. build process, release process) in separate threads? that -- Regards Torsten
