Timeline for What's our policy on questions regarding unreleased code?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 7, 2012 at 17:40 | comment | added | Justin Dearing | @voretaq7 yeah the difference between a MS RC/CTP/DeveloperPreview or beta and freebsd-current is that the beta is long lived, and with the Windows8/Server2012, many MSFT downloads mentioned support for particular pre-RTM releases, while current is a point in time. As far as what is professional, yes don't install the latest freebsd current or windows RC on the important servers. However, depending on the nature of your job/shop DO install it on a dev/test/qa environment and possible your workstation. Try to port your software to the next OS before its released. | |
| Sep 6, 2012 at 16:07 | comment | added | voretaq7 Mod | @JohnGardeniers That's an interesting point (albeit a little Microsoft-specific) -- I would say if an MS Release Candidate is widely distributed enough and generating enough quasi-production interest it should receive a special tag (windows-2008-server-rc1 or something similar) as a general-case exception because MS is special... | |
| Sep 6, 2012 at 10:24 | comment | added | MDMarra | @John the problem with RCs and such is that they have the pesky habit of not working the same after release. If they're in the RC or beta stage and you're seeing odd behavior, you should file a bug report with Microsoft (or whoever), not post about it on SF. That's what the whole Beta and RC phase is for, right? If we take questions on prerelease code, we'll amass a bunch of q&as that are close but may not be accurate or relevant to the finished product. | |
| Sep 6, 2012 at 9:58 | comment | added | John Gardeniers | What about things such as MSDN versions of say Windows Server, which are made available so that we can work with it to prepare for it in a production environment when it is eventually officially released to the public? The way I see it these are systems we must deal with at the professional level, often having to build entire networks of such systems, yet which don't meet your definition of professional. Sorry but I believe you've taken too narrow a view in regards to what is professional, possibly because you don't work in those environments. | |
| Sep 5, 2012 at 16:30 | history | answered | voretaq7Mod | CC BY-SA 3.0 |