On 10/05/2011 15:40, Franklin, Matthew B. wrote:
Now that we are beginning to see the features start to get implemented, I
think we should start thinking about a release early, release often
schedule.
Matt, your a dynamo!
I really like what you are doing here. I just wish I had more time to do
stuff - seeing you charge ahead is really filling me with a desire to hack.
I have created a 0.1-INCUBATING release in JIRA and attached
the issues that I think would need to be in place to have a very early
"alpha" release.
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQue
ry=project+%3D+RAVE+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%220.1
-INCUBATING%22+ORDER+BY+priority+DESC&mode=hide
Beyond this release, I think we should look at having a release every
month or every other month, reaching (hopefully), a graduation-level (1.0)
release within 1 year.
+1
Releases at the ASF are quite cumbersome in some ways. Our due diligence
processes are thorough (especially here in the incubator). However, a
great deal of it can be automated. Doing a release now will enable us to
put the basic framework for automated release building in place, this
can be enhanced as our code grows and matures and thus the legal due
diligence becomes more onerous.
Ross
