I agree with you all that this is a problem and that more information (and earlier) is needed, and apologize for not providing information more quickly.
As others have pointed out, Solaris Express is a completely separate team. I do get information before many people, but don't usually get it immediately. I will try to communicate the details more quickly when the release will be late. However, we can't always give details about the issues for contractual/legal reasons. Half the time, I don't even get all the details. I hope, over time, you all will trust that when we say the release is delayed or can't go out, that there is a good reason. We've definitely had suggestions that we not publish builds for technical reasons, and we've consistently released the build anyway. True legal reasons are the only cause for delays in getting releases out -- at least that has been the case so far. We're working to ensure that all the groups delivering to Solaris are more aware of resolving legal issues before integration, but I expect that there will continue to be mistakes. As much as possible, we'll try to mitigate these with the O/N builds (like we did with the last build: releasing updated SFW packages), but sometimes that just won't be possible. Also, just as a reminder, I did post a note about this on Thursday (2/9) when there were some questions. Still not early enough, I know, but the information was out there. I just talked to the program manager and got an update. Build 33 will be out today: so it's actually ahead of schedule! We're skipping 31 because it was going to be ready at the same time as 33, and 32 had some other legal issue that was fixed in 33. So, they're just pushing 33. Thanks for your patience, Karyn This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
