search

IBMStreams / administration

Umbrella project for the IBMStreams organization. This project will be used for the management of the individual projects within the IBMStreams organization.
Other
19 stars 10 forks source link

Proposal: On-demand Toolkit Release Process #87

Closed chanskw closed 6 years ago

chanskw commented 8 years ago

In IBMStreams organization, toolkits projects are released on-demand.

From the end-user perspective, it is hard to predict when a release will be available. And if the user needs a release, there is no clear documented process on how to get a release to be published.

From the toolkit developer's perspective, there is no clear guidelines on what needs to be done to create a toolkit release. For example, it is not always obvious that toolkit version numbers need to be updated upon a release.

I have started this process to try to clarify these two points:

I also think it will be a good idea to start recording some of these in issues, so we can better keep track of branches, releases and history.

Please review the process and let me know what you think.

This is not a mandatory process. It is up to the project owners to decide if they want to follow this process or not. This is just a guideline.

https://github.com/IBMStreams/administration/wiki/On-Demand-Release-Process

ddebrunner commented 8 years ago

Seek a +1 vote from at least one other committer

Somewhat in conflict with the graduation guidelines that state:

Project must have at least one active committer

So a project can only have one committer and I think a few do, so there is no other committer to seek a vote from. But since it's up to project teams to follow the guidelines, single committer projects can do something else.

chanskw commented 8 years ago

Right, this is up to the project team to follow. I think this process is more applicable to more mature project, where multiple committers are available. For less mature project, the process can be tweaked.

chanskw commented 8 years ago

This is an example of how we implemented this process in streamsx.jdbc: https://github.com/IBMStreams/streamsx.jdbc/issues/38

It helped us catch issues with bumping version numbers and testing is done and making sure that samples are ok.

chanskw commented 6 years ago

Closing this one, if you have more feedback on the process, please open new issues.