I've also thought about this, but more from a version tracking perspective.
Say I've got version 3.0.1 of an app, and I change 12 templates out of a hundred, and want to now call it version 3.0.2. It would be nice if there was some sort of tag within the fusedocs that could be searched to see what revisions occured where, so I could find the templates containing 3.0.2 updates. It would be nice, therefore, to also have some sort of versioning variable in place. "app.version" or whatever. > -----Original Message----- > From: Erki Esken [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, June 05, 2002 12:16 AM > To: [EMAIL PROTECTED] > Subject: Re: fusedoc type="" > > > Sometimes it takes an outside perspective... this ASP guy I have trying > > to learn CF and Fusebox while working as primary coder on a huge site > > with an impossible deadline has just asked about the fusedoc history tag > > "type" attribute. I said, "it's usually create or update". He gave me a > > blank look, which made me realise that these two values are pretty > > redundant. I mean, we won't be updating a document that has not yet been > > created. What does everyone else use this for? > > > > I've been thinking about adding a type="bugfix" and specifing the bug > track number in comments or within tag content. > > Also, I think that type="refactored" or something like that would make > sense. No? > > .erki > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
