|Re: [eclipse.org-planning-council] Shorter release cycles (cont...)|
Yes, but my scenario was more driven by a committer team that didn’t work as a unit. On a diverse project, there are many bosses and they don’t report to each other. The train helped me bring the different factions together and helped us work as a unit. And ironically enough, it was because the releases were yearly and people didn’t want to miss it. I kinda loose that hammer if we release too often. You may end up with committers taking a release off knowing they can jump back on for the next release in three months. It’s a strain on the rest of the team.
It something we can over come, and sometimes face anyway. We just need to make sure the projects have strong leadership to pull it all together. I just wanted to add the data to the mix.
From: Ian Bull <irbull@xxxxxxxxxxxxxxxxx>
Reply-To: Eclipse Planning Council <eclipse.org-planning-council@xxxxxxxxxxx>
Date: Wednesday, May 6, 2015 at 2:19 PM
To: Eclipse Planning Council <eclipse.org-planning-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-planning-council] Shorter release cycles (cont...)
Back to the top