You mean something like http://cvstrac.pfsense.org/? That would be the bug tracking system that also tracks our commits, not only will you see a list of all open tickets (under reports), but you'll get a list of checkins between any two arbitrary dates you choose.
--Bill On 6/30/07, Dimitri Rodis <[EMAIL PROTECTED]> wrote:
Hey guys, I have a question/suggestion for the devs that I realize may either be very easy or very difficult, but: Would it be possible to make the Automated CVS "snapshot" builds include a txt/html file in the release that contains currently open and "known" issues with the release? The reasoning for it is simply this: short of constantly monitoring the support list, I'm not sure where most people would go to find these issues out. Surely they are documented somewhere in your CVS, so perhaps a script could be added to the automated build process to make this work? Here are 4 suggestions for where you might put it (in order of my preference, but really it doesn't matter in the end) 1. a link from inside the pfSense web interface to a page on pfsense.com that contains "known" issues which gets updated with each automated build 2. a link to a static html page inside the pfSense web interface that contains known issues for that particular build 3. a text file put up on snapshots.pfsense.com with a filename consistent with the snapshot build 4. option number 88 (or some other unused number) on the console menu that simply "cats" the release notes to the console. Again, I don't know if this is easy or hard, but it sure would make it simpler to know what issues you might be facing when you deploy a new snapshot as opposed to bothering you guys in the support list with it. Think it might be a possibility? Thanks, Dimitri Rodis Integrita Systems LLC
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
