Skip to Content.
Sympa Menu

comanage-dev - [comanage-dev] Tagging 0.3 Release, Code Freeze, etc

Subject: COmanage Developers List

List archive

[comanage-dev] Tagging 0.3 Release, Code Freeze, etc


Chronological Thread 
  • From: Benn Oshrin <>
  • To: comanage-dev <>
  • Cc: Heather Flanagan <>
  • Subject: [comanage-dev] Tagging 0.3 Release, Code Freeze, etc
  • Date: Fri, 30 Dec 2011 20:36:22 -0500

Looking through the remaining issues for 0.3...

CO-167, CO-168, CO-169 are all demo server related.

CO-202 (randomized salts on install) is assigned to Scott and flagged as a blocker. We should get this done ASAP (so this should go to the top of Scott's list for when he gets back), but for now I've pushed it to 0.4 so we can get 0.3 tagged before the end of the year.

CO-155 Marie couldn't reproduce it before and I can't now so I resolved it.

So, time to tag 0.3! I've drafted a simple document for how to create a release at

https://spaces.internet2.edu/display/COmanage/Creating+a+Release

I've added a new release "COmanage Demo 3" to JIRA and moved the open demo tickets there. This aligns with having COmanage Directory as a parallel product.

Let's consider the code freeze for Cake 2 in effect as of now. Please don't commit anything until the freeze is over. This will probably be a week or two, depending on how much stuff I end up changing in the migration. (I'm mostly done with the Directory POC, but have a few more things to do before committing it.)

Mostly for Heather: We should add a recurring (monthly?) item to the Friday call agenda to revisit projected release dates.

Also, we should probably have some "The COmanage Project is pleased to announce the release..." boilerplate that we spam on a release.

-Benn-



Archive powered by MHonArc 2.6.16.

Top of Page