Answer here:
http://www.profootballtalk.com/2009/05/15/june-1-has-no-meaning-on-this-years-nfl-calendar/June 1 Has No Meaning On This Year’s NFL Calendar
Posted by Mike Florio on May 15, 2009, 7:10 a.m. EDT
Last night, we posted an item asking folks to suggest potential topics for this week’s round of PFTV segments.
A couple of you asked for us to review the potential June 1 cuts this year.
We can do that right here, right now: None.
June 1 became an important date during the first decade under the salary cap system because it allowed a team to spread any cap hit arising from the remaining signing bonus allocation over two years. (It wasn’t a 50-50 thing; instead, the team absorbed the allocation for the current year in the current year and all remaining allocation the next year.)
The 2006 amendments to the Collective Bargaining Agreement allowed teams to cut up to two players per year before June 1, but to process the transaction as a post-June 1 event. This allowed teams to put guys on the market earlier in the offseason — and also to keep them out of the offseason program, during which a player could suffer a severe injury and be entitled to his full base salary if unable to play that season.
For 2009, the entire remaining allocation hits the cap when the player is released, regardless of whether the move comes before or after June 1.
So the date means nothing this year, and any moves made thereafter will have only a coincidental relationship to the fact that the calendar says “June.”