Paperizing ideas sounds good. How does the log4net project handle requirements? JIRA? Are there any requirements other than the ones under the 'supercedes' list?
I'm afraid I don't have a 'vision' for the RFA-NG but I think we can take the patch under log4net-patches, make sure to fix the 'supercedes' list and off we go. I wouldn't want to spend time on a grand design because we can't tell how long will it take, and I think it is better to ship a less than perfect RFA-NG and fix it later on when we'll know what we want than to postpone the next release indefinitely. BTW, no offense, but is there a chance it will be easier to fix the current RFA than to rewrite it? Is there a way to measure a given implementation of any RFA to determine if its good enough? On Fri, Aug 9, 2013 at 8:00 PM, Dominik Psenner <dpsen...@gmail.com> wrote: > Howdie, > > the patch there is mainly a first implementation showing the road we would > like to go. There are many things to be discussed and I would start with > paperizing the ideas before starting the implementation. The > reimplementation should solve all known current issues of the rolling file > appender. > > The patches repository is nothing else than a repository that holds > patches that can be applied to the log4net source, which is located at > apache.org's svn. It's there to materialize the ideas without requiring > write permissions to the actual svn and can be used as a sandbox to play > with ideas. > > I started off with an implementation as a patch and wanted to improve that > patch until it is stable enough to join the log4net appenders in svn. > > Cheers > > > 2013/8/9 d_k <mail...@gmail.com> > >> Hi, >> >> So I think I got a working development environment for log4net. >> >> I installed mercurial and forked the log4net-crew repository ( >> https://bitbucket.org/NachbarsLumpi/log4net-crew) and the >> log4net-patches repository ( >> https://bitbucket.org/NachbarsLumpi/log4net-patches) and applied the >> RFA-NG patch with 'hg import'. >> >> Should I prefer to use http://svn.apache.org/viewvc/logging/log4net/trunkover >> https://bitbucket.org/NachbarsLumpi/log4net-crew? Will svn and mercurial >> coexist peacefully? >> >> Do I need anything else to start developing? >> >> Should I create my own RFA-NG2 patch? Or perhaps RFA-NG-NNN for each bug >> in the supercedes list of LOG4NET-367 ( >> https://issues.apache.org/jira/browse/LOG4NET-367)? >> >> Are there any common pitfalls I should avoid? >> > > > > -- > Dominik Psenner > ## OpenPGP Key Signature ################################# > # Key ID: B469318C # > # Fingerprint: 558641995F7EC2D251354C3A49C7E3D1B469318C # > ########################################################## > >
