Automating the world one-liner at a time…
Next week we'll be releasing a Community Technology Preview (CTP) of Windows PowerShell V2.0. I'm going to hold off saying what is in it until next week. The purpose of this email is to set your expectations about the CTP.
CTP -NE BETA !
The first thing to get into focus is that a CTP is NOT a Beta release. A CTP is a very early drop of our technology with the following goals:
One of the shared frustrations around Betas is that the feedback comes at a time that is difficult to make changes. At the end of the release, you want to minimize the code changes because one out of every X changes you make breaks something else that you won't detect. The way it works is that there is a standard for what bugs will get fixed and that standard gets tighter and tighter as the release forward. Given that reality, a number of us are pursuing a CTP approach which provides the community access to our technology at a time where "good ideas" can be acted upon, "changes in direction" can be considered, class names can be changed, classes can be refactored, features cut/added, etc. Once we go into beta, the changes we can consider are dramatically reduced, by the time we hit RC (Release Candidate) we basically are determining whether bugs will explode computers, kill users or destroy economies of small nations. If not, well …. (It is not that bad but it sometimes it feels like that – we get really hard core about not messing you up by introducing changes that could break things that we can't detect.)
But as Lao Tzu says, things greatest strengths are their greatest weaknesses.
So while the CTP gives you early access to V2:
This is a tricky blog – I want to entice the right set of people to grab the CTP, kick the tires and then tell us what things to change because they know that they have a real change of getting their suggestions incorporated. I also want to scare off those people that will be unhappy if they use a feature and it goes away or changes in the next CTP.
To quote Robin Williams from the movie DEAD AGAIN: "Someone is either a smoker (CTP user) or a nonsmoker. There's no in-between. The trick is to find out which one you are, and be that. If you're a nonsmoker, you'll know."
If you read the warnings above and said, "AWESOME!" – you're a CTP user.
If you read the warnings above and had a feeling like there was a squirrel in your shirt – you're not a CTP user.
Figure out which one you are and be it. J
Jeffrey Snover [MSFT]Windows Management Partner ArchitectVisit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShellVisit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
If one desired solely to anticipate, then explore and then extend one's understanding of CTP PS 2.0 in a Vista environment ... What would you recommend as a minimal laptop setup ?
The Windows PowerShell Team is pleased to release the first Community Technology Preview (CTP) of Windows
The PowerShell team released a Community Technology Preview of PowerShell 2.0 this week. They have had
The PowerShell 2.0 CTP is nearly here!
I can't believe that there have been all these comments and no one has pointed out the != is invalid syntax and the title should be:
"CTP -ne Beta!"
> I can't believe that there have been all these comments and no one has pointed out the != is invalid syntax and the title should be:
I don't know what you are talking about EB. :-) (yeah for the ability to edit your blogs!)
The Windows PowerShell Team is pleased to release the second Community Technology Preview (CTP2) of Windows
While Santa and co. are getting busy for Christmas, the Windows PowerShell Team is pleased to release