Re: [website-dev] When Does the Redesign Begin?

Lars Nooden wrote:
> On 06/28/2010 03:17 PM, TJ Frazier wrote:
>> But old open bug documents are working means of communication (or
>> they're supposed to be), among users, developers, QA, release
>> engineering . . . They will require some more immediate solution.
> 
> Less urgent that one would expect if after a certain day no new issues
> can be created in the old bug tracker.  New issues would then be created
> in the new bug tracker and the old ones closed out naturally over time.
> 
> There is still a question of what to do with issues that are still open
> after a certain date, say a few months later.  One option would be to
> post updates to them telling people to re-enter them in the new bug
> tracker if they wish the issue carried forward.  The ones that are
> orphaned probably weren't that pressing but if they are they will get
> 'rediscovered' and entered in the new bug tracker.
> 

As I said on another mail in this group the migration plan there is to 
migrate the old issuezilla database into a new bugzilla database and 
than incrementally upgrade it with content grabbed from the website to 
keep the downtime of the bugtracking system down and to keep all old 
issues. This can be done because the issuezilla and the bugzilla 
database design is very similar.


> /Lars
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

Kind regards,
Bernd Eilers