This project has moved and is read-only. For the latest updates, please go here.
1

Closed

Countdown to Release Day

description

I would like to see a countdown to release day added to the bottom with the option to replace the countdown to refresh with a weeks, days,hours, minutes, seconds countdown to the release
 
I always either release on the monday after the 1st or 15th every 6 weeks. And it would be good to know how much time my team has till we release
Closed Dec 3, 2009 at 6:57 AM by PandaWood
I think this would be nice in your particular situation but is only thinly related to CI project statuses, so is probably best left at that - ie a change to the source which you make and upload as a patch incase anyone else is interested

comments

BHofmann wrote Nov 5, 2009 at 11:48 AM

I don't feel this belongs with broken builds or build status. This should be on a different radiator that shows code churn, new bugs versus resolved bugs and so on. These are the indicators of whether a build is ready for the release in T-n days time.

zelax25 wrote Nov 7, 2009 at 4:42 AM

In my department I manage a build server for 40+ projects and we release our projects twice a quarter currently we have code bases that are over 10 years old and have some 400 known issues to have a code churn radiator for each one would show that some projects should never have been released 10 years ago. I was just proposing the instead of the countdown to retirving the new status that it could be a count down till release day each project lead manages thier own bug list and known issues but a general knowledge of the amount of time left to fix bugs would apply the necessary pressure to fix bugs first and add features second.