One of the requirements for graduating from incubator is the ability to
cut releases. The guideline says to do a release often -
http://incubator.apache.org/guides/graduation.html#releases.
As more people start running Olio, it will become very difficult to
debug their problems as we are continually checking in changes. Having a
binary release for users to download will greatly ease this.
I think both the php and rails apps are in a stable enough condition to
cut a release. Granted there are some discrepancies and ongoing work,
but we can capture these in the release notes.
There is obviously work involved in doing this. Firstly, there is the
generic groundwork to be done to establish the distribution directory
etc. which I'm happy to take ownership of. After reading the relevant
documents, I'll post an email summarizing my understanding of the tasks
involved (and the mentors can correct me).
Secondly, we need to decide on the distribution layout. We in Sun, have
of course been cutting releases for internal use and have also made the
first Olio release available publicly at
http://wikis.sun.com/display/BluePrints/Web+2.0+Scalable+Performance+Toolkit
I encourage people to please download the php version from this link and
check if this layout is acceptable. We do need to add release notes,
update documentation, assign a version number etc.
It would be great to work towards this with some kind of timeframe in
mind so as to get us all motivated ;) I would like to propose we target
a release for March 16 - that gives us about a month to get our act
together.
Comments ?
Shanti
- Time to cut an Olio release Shanti Subramanyam
-
