[Cosmo-dev] Proposed P1/P2 for 0.6

[Ted Leung]

On Dec 6, 2006, at 2:19 AM, Jared Rhine wrote:

> Last week, we said the list of tickets targeted for inclusion in  
> Cosmo 0.6 were those marked P1 or P2.  I was asked to identify  
> bugzilla tickets which should probably be included, but aren't  
> currently marked P1/P2.  There's three I'd like to propose.
>
> 7026: forbidden.jsp not served up for login
> 7169: HTTP caching for Cosmo UI resources
> 7219: ticket ids should be short and sweet

+1 to making these all P2

> I'd love to see as a P1, or measurable progress in this area:
> 7433: Compact/compile Cosmo Javascript (currently P2)

Since it is a P2 it will happen this release, just after all the P1  
features get done.

>
> At next bug council, I suggest we do a search for open bugs with  
> 0.6 as a target milestone and review for deferrals, as this used to  
> be the scheme we used to denote 0.6 inclusion.  (I still think this  
> is probably the easiest mechanism.  Marking dependencies would work  
> fine too, as long as everything is included, not just tasks/ 
> enhancements).

We can either defer or raise priority.  I think that there are too  
many priority levels for shorter release cycles -- realistically most  
p3/p4 bugs will get deferred.

Ted