Hey David,

I think we should do the transition but I'm definitely not an expert. I think that in the end the people that actually take care of the core packages should make the decision.

However I will help if we decide to do so.

regards, Paul

Am Donnerstag, den 28.05.2009, 19:47 +0200 schrieb David Nielsen:

Dear list,

As previously mentioned, I would love for us to start work migrating to Mono 2. This work has already been done by Ubuntu and Debian and patches are available for nearly all packages.

The effect of this will be cutting the footprint of Mono apps by around 20-40% in most cases and as such presents a major advantages for our users.

Jo Shields wrote a nice post to the Ubuntu devel list explaining this work: https://lists.ubuntu.com/archives/ubuntu-devel/2008-November/026872.html

Debian packages along with migration patches can be found here. http://svn.debian.org/viewsvn/pkg-cli-libs/packages/ http://svn.debian.org/viewsvn/pkg-cli-apps/packages/ http://svn.debian.org/viewsvn/pkg-mono/

Now I would like to get this work into F12 which means we can start doing it now and have it finished hopefully in time for the first milestone release. This will take a concerted effort from everyone currently maintaining a mono based package and the first step has to be agreeing upon a plan of attack. I would propose the following:

1. Compile a list of packages that need patching and maintainers for

these packages. 2. Every package maintainer then extracts patches for his packages from Debian and posts to the list for review. 3. Once every package on the list has patches available we commit them to cvs and announce a rebuild to fedora-devel-announce.

I would like to be at 2. by June 30th, any maintainers having failed to extract a patch and get it reviewed on the list by that day should expect to have their packages manually altered by a provenpackager (this is not an excuse to sit back and let me do the work though). We should aim to be at 3. on July 15th, at which point we are up to date with pkg-mono' current progress and can interact with them for future steps. This gives us a month and a half to complete the work and leaves ample room to shake out the bugs before release.

We should expect fall out, it is a major improvement and it carries risks along with it. I hope we can all pull together resources to handle bug reports stemming from this work.

• David

---

fedora-mono mailing list fedora-mono@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-mono