-
Notifications
You must be signed in to change notification settings - Fork 6
Release_Cabal
giulivo edited this page Jan 24, 2013
·
19 revisions
On this page the Release ommittee will report about the meetings’ agenda and the actions taken. Meetings usually recur on Thursdays in #aeolus-meeting on freenode at 16:00 CET.
We use MeetBot to collect the logs and minutes of our meetings. In case of troubles, the instructions to setup an instance of MeetBot are here https://github.com/giulivo/aeolus-meetbot
Agenda
- Wrap up on the current status of art
- Decide on our officially supported platform for upcoming release
- Define some ‘recurring’ date for our next meetings
Minutes
Agenda
- Review the existing install docs and look for improvements
- How to put together some user guide
Minutes
Agenda
- Release schedule
- shall dev-tools require root credentials?
- giulivo’s proposal for the user guide to split it into three sections: 1. install deltacloud-core ; 2. install imagefactory ; 3. install conductor via dev-tools using rbenv
- this is what I tested and was rather successfull with: http://etherpad-aeolusproject.rhcloud.com/p/aeolus-upstream-deployment-notes
- or should we pursue dev-tools installing other components. sloranz is reputed to have made some progress on from-source factory install.
- do we want to require a real RDBMS for a real release?
Followed up items from previous meetings
- The latest “dev” version of the install docs can be found here
- Generated HTML - http://justinclift.fedorapeople.org/asettle/use_it.html
- GitHub repo - https://github.com/justinclift/aeolus-website
Minutes
Agenda
- shall we bundle templates with next release?
- can we mandate all Aeolus project’s must send an email to aeolus-devel every time they do a new release?
- Some projects do already (i.e Oz), some don’t (ie Bundler, ImageFactory).
- Without release info somewhere, it’s very hard to tell which version of a project to use.
- We should assign some people to the unclaimed action items from last weeks agenda.
- SOP draft needs documentation completed around release procedures (the work, in progress, of this cabal)
Followed up items from previous meetings
- Release schedule
- Justin is collecting the release info and ETA of next release for each Aeolus project here https://etherpad-aeolusproject.rhcloud.com/p/all-project-release-dates
- Justin invited Crag to next meeting. Crag will attend.
- Justin is in early stage discussion with Hideki Yamane (debian-cloud guy) about the versions of Aeolus components being packaged. Has recommended using the packages from the soon-to-be-released version of Aeolus, but hasn’t heard back yet (will prob take a few days).
- eggmaster confirmed with sloranz that imagefactory from source is in progress and expected functional/delivered early Jan
- eggmaster emailed link to draft of SOP to cabal members privately for first round of review, http://slinabery.fedorapeople.org/SOP-aeolus.html
Minutes
Agenda
Followed up items from previous meetings
Minutes
Agenda
- consider proposed Sprint schedule for first half or so of 2013 https://github.com/eggmaster/aeolus-sop/blob/master/sprint_schedule.markdown
- current sprint is ending without major release, discuss needed steps for minor release and assign action items for same
- Documenting steps in the release process, example from katello athttps://fedorahosted.org/katello/wiki/ReleasingKatello
- people at imgfac decided to abandon setuptools in favour of native distro packaging https://github.com/aeolusproject/imagefactory/issues/165
- where should we track potential fedora/rhel packaging issues, e.g. when package availability in fedora/rhel trail our reqs in Gemfile.lock https://github.com/aeolusproject/conductor/commit/3d8a881b3409c6de7bbe18bba9df91f158765d95
Minutes
Agenda
- check in where people are at with release related stuff
- can we assume imgfac and deltacloud will also provide a ‘release branch’ ?
- someone needs to take some steps to have audrey installed by dev-tools!
- do we agree on using dev-tools as a single bootstrap script for the whole aeolus project, supposed to checkout and build all the components we develop from sources but not the deps? AND, is this good for end users?
- work still required for minor release for 2012-December-1 sprint which just ended
Minutes
Agenda
- reminders re: sprint schedule and release-related dates
- checkin/status of release related work
- are we ready to merge the notes from http://etherpad-aeolusproject.rhcloud.com/p/aeolus-upstream-deployment-notes into a single list of install steps?
- review list of required release documentation
Minutes
Agenda
- reminders re: sprint schedule and release-related dates
- checkin/status of release related work
Minutes