comanage-dev - [comanage-dev] Path to 1.0
Subject: COmanage Developers List
List archive
- From: Benn Oshrin <>
- To: comanage-dev <>
- Subject: [comanage-dev] Path to 1.0
- Date: Mon, 23 Feb 2015 17:24:45 -0500
I'd like to get to 1.0 sooner rather than later, given the recent increasing uptake of COmanage. To that end, I've moved about a quarter of the issues from 0.9.4 and 1.0 to FUTURE (leaving about 150) to provide a better idea of the path there.
My proposal is that 1.0 consists of the current codebase plus
+ Simplification of installation and upgrades
+ Bug fixes, particularly those that affect major components
or are easily noticeable
+ QA Testing
In addition, anything that becomes a priority because of a client gets put into the current release cycle (and potentially therefore part of 1.0).
Is there anything else major that should be considered a "blocker" for 1.0?
It'd be great to get to 1.0 for I2GS, but I don't see that happening. TNC, perhaps?
Thanks,
-Benn-
- [comanage-dev] Path to 1.0, Benn Oshrin, 02/23/2015
Archive powered by MHonArc 2.6.16.