On 08/13/2011 04:46 PM, Stefan Bodewig wrote: > I'm not even sure whether some of them still are relevant. They > certainly need to be rescheduled. > > My preference would be to have some release like 1.2.MAINTNENANCE that > we'd assign things to that may eventually get fixed in a 1.2.x release > if we agree that these are the versions that actually work for compact > framework and 1.x - and a few others similar unspecific releases. > > We then pick the pieces from there as we prepare real releases. > > Right now I'm afraid we'll have to visit all open issues and > re-assign/close them.
Its a lot of work, but it has to be done. We're then able to identify (really) open bugs and we can then see forward to resolve them for 1.2.11. Further there are a lot of changesets (101) that are still waiting to be included in the next release. We probably have to work through them too. The other big story is the support for the .NET client profiles. As I understood it, we have to drop everything in log4net that is not supported in a .NET 4.0 client profile (i.e. references to System.Web). To achieve this we have at least two options: 1] refactor everything that doesn't fit with the client profile into a separate project / dll 2] maintain a .net 4.0 client profile branch with a subset of the log4net functionality * Solution [1] is a pain for everyone that uses log4net since they need to reference two libraries instead of one * Solution [2] is a pain to maintain with subversion We have to investigate into all this a little more so that we can come up with a plan that just works. -- Dominik Psenner ## OpenPGP Key Signature ################################# # Key ID: B469318C # # Fingerprint: 558641995F7EC2D251354C3A49C7E3D1B469318C # ##########################################################
signature.asc
Description: OpenPGP digital signature
