I would like to propose the following:
- since IA64 support is currently broken
- since CVS is frozen
- since there's at least some pending work that has been waiting for about
a month (i.e., can't be committed)
- since this means that other OSCAR work has come to a standstill
We should do one of the following:
1. release what we have now as 2.1.1 without support for IA64; the big
selling point is more network drivers, etc. This is with intent to
someday do 2.2 with IA64 support restored (i.e., when SI -- or
whatever the problem is -- gets fixed). IA64 people would still use
2.1.
2. forget the idea of releasing now, and unfreeze CVS so that IA64
support can be fixed and other OSCAR development can progress.
3. branch CVS so that 2.2 is on its own branch and development work can
progress at the head.
I'm actually pretty opposed to #3, but it is a legitimate option, so it's
only fair that it should be listed.
Comments? Suggestions?
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
