Re: Official bug tracker?

Hi.

I think it's time to pick this up again after the snow sprint, where
some major work on AT has happened. FWIW the prior mood to have a common
tracker has been at least partly due to the fact that AT itself has kind
of slept for a while.

But as it gets momentum again and will hopefully see some more in the
next months I think having a separate tracker is a valid option again.

Alexander Limi wrote:
> 
> OK, so how about we do this:
> 
> - Have separate Trac instance for AT (mostly used by developers and
> people somewhat familiar with what components are in Plone) - This is
> used for keeping track of and executing AT releases
> 
> - Add a category "Archetypes" to the Plone tracker, small bugs stay in
> this category, bigger stuff gets "ported" over to the AT tracker as needed.

Now this is a great proposal.
+1

My offer to do the remaining dirty work still stands ;)

> I would still like to see PLIPs being used more extensively for AT
> development. The changes we are making to PSC in SVn will make it
> possible to subscribe to RSS feeds of proposals etc - making the process
> of new proposals much easier to track.
> 
> (everything else also has an RSS feed - categories of software,
> individual projects, etc etc :)

Personally I love PLIP's and I would encourage people to write some
PLIP's (ATIP's?) for the current AT componentization mainly for purposes
of documentation but obviously cannot force anybody to do this ;)

> Anyway - is the above proposed solution for AT something that makes sense?

At least to me, yes :)

Hanno



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642