-
Notifications
You must be signed in to change notification settings - Fork 6
Release_Cabal
Mo Morsi edited this page Jan 4, 2013
·
19 revisions
title: Release_Cabal
updated_on: Thu Dec 20 11:16:25 ~~0500 2012\
\
h1. Release Cabal
\
On this page the Release Committee will report about the meetings’
agenda, the actions taken and the schedule for next meetings. Meetings
will recur on Thursdays / check \#aeolus-meeting on freenode at 16:00
CET.\
We use [MeetBot](http://meetbot.debian.net/Manual.html) to collect logs
and minutes during our meetings. Instructions to setup an instance of
MeetBot are here
[https://github.com/giulivo/aeolus-meetbot](https://github.com/giulivo/aeolus-meetbot)
\
h2. 16 November 2012 / \#aeolus-meeting on freenode at 15:00 CET
\
*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](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-11-16-14.05.html)\
\>
[Logs](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-11-16-14.05.log.html)
\
h2. 21 November 2012 / \#aeolus-meeting on freenode at 15:00 CET
\
*Agenda*
\
\* Review the existing install docs and look for improvements \
\* How to put together some user guide
\
\>
[Minutes](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-11-21-15.02.html)\
\>
[Logs](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-11-21-15.02.log.html)
\
h2. 29 November 2012 / \#aeolus-meeting on freenode at 16:00 CET
\
*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](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?
\
\>
[Minutes](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-11-29-15.04.html)\
\>
[Logs](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-11-29-15.04.log.html)
\
*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](http://justinclift.fedorapeople.org/asettle/use_it.html)\
**\* GitHub repo~~
[https://github.com/justinclift/aeolus-website](https://github.com/justinclift/aeolus-website)
6 December 2012 / \#aeolus-meeting on freenode at 16:00 CET
-----------------------------------------------------------
*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)
\>
[Minutes](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-12-06-15.01.html)\
\>
[Logs](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-12-06-15.01.log.html)
*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](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](http://slinabery.fedorapeople.org/SOP-aeolus.html)
13 December 2012 / \#aeolus-meeting on freenode at 16:00 CET
------------------------------------------------------------
*Agenda*
- follow up on previous action items
\>
[Minutes](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-12-13-15.01.html)\
\>
[Logs](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-12-13-15.01.log.html)
20 December 2012 / \#aeolus-meeting on freenode at 16:00 CET
------------------------------------------------------------
*Agenda*
- consider proposed Sprint schedule for first half or so of 2013
[https://github.com/eggmaster/aeolus-sop/blob/master/sprint\_schedule.markdown](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 at
[https://fedorahosted.org/katello/wiki/ReleasingKatello](https://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](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](https://github.com/aeolusproject/conductor/commit/3d8a881b3409c6de7bbe18bba9df91f158765d95)
\>
[Minutes](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-12-20-15.03.html)\
\>
[Logs](http://www.aeolusproject.org/cabals/release/minutes/aeolus-meeting.2012-12-20-15.03.log.html)
03 January 2013 / \#aeolus-meeting on freenode at 16:00 CET
-----------------------------------------------------------
*Agenda*
- can we assume imgfac and deltacloud will also provide a ‘release
branch’ ?