VOTE: Midgard Release Synchronicity
-
Henri Bergius
VOTE: Midgard Release Synchronicity
Thu July 31 2008 10:34:11 UTCMidgard Release Synchronicity
============================
This is a proposal to move Midgard to a more coordinated release
process in order to make development more predictable, marketing
efforts clearer and more focused, and to align ourselves with the
release synchronicity movement implemented with related projects like
GNOME and Ubuntu.
Some background
---------------
* http://www.markshuttleworth.com/archives/150
* http://coccinella.im/synchronized-releases
* http://www.midgard-project.org/discussion/developer-forum/read/f2eba8125d7511dda1900b3dd91b5a5c5a5c.html
Actions
-------
* Clarify naming of different aspects of Midgard: Midgard Platform,
Midgard MVC, Midgard CMS
* Combine releases of Midgard and MidCOM into "generations" that are
compatible with each other and are targeted to specific set of
dependencies (libgda and PHP versions for instance)
* Focus on names of the generations instead of individual version
numbers: thor instead of 1.8 and 2.8, ragnaroek instead of 1.9 and 2.9
etc
* Write down a fixed ragnaroek feature list ASAP and prepare for
release during September
* Schedule a Midgard developer meeting to October for discussion of
ragnaroek+1 (former 2.0, vinland?) feature list
* Switch to git and feature branches after ragnaroek is out
* Introduce a concept of long-term supported (LTS) releases. Ragnaroek
will be the first one. LTS means the generation gets fixes at least
for a few years
Proposed schedule
-----------------
* Aug 2008: Decision on release syncronicity, ragnaroek beta
* Sep 2008: Ragnaroek stable, new Midgard website
* Oct 2008: Ragnaroek+1 planning developer meeting, switch to new PEAR
channel structure
* Nov 2008: Git migration, starting automatic builds (and tests?) of
ragnaroek and ragnaroek+1
* Feb 2009: Ragnaroek+1 beta
* Mar 2009: Ragnaroek+1 stable
* Apr 2009: Ragnaroek+2 planning developer meeting
* May 2009: Midgard 10th anniversary party, Helsinki, Finland
* Aug 2009: Ragnaroek+2 beta
* ...
What is a release?
------------------
Release is a launch of same generation of at least Midgard Platform
and Midgard MVC (MidCOM). CMS may be released a month or two later as
components may need time to catch up with the generation. This would
be consistent of the "release waves" approach proposed by Mark
Shuttleworth, where first wave consists of libraries (Midgard
Platform, Midgard MVC), second of applications (Midgard CMS), and
third of distributions.
Release must include:
* Marketing information on the website (/midgard/generationname)
* Tarballs
* RPMs, debs, built on opensuse build service
* Preinstalled images for at least Parallels and VMware
* Updated/correctly tagged documentation
* Demo site (both online and as downloadable image)
Automated tests
---------------
We all need to learn test-driven development, and actually make unit
tests for both Midgard and MidCOM, so that we can more easily
safeguard against regressions when feature branches land into trunk. I
propose we arrange a unit testing workshop in the next Midgard
developer meeting.
http://en.wikipedia.org/wiki/Test-driven_development
--
Henri Bergius
Motorcycle Adventures and Free Software
http://bergie.iki.fi/
Skype: henribergius
Jabber: henri.bergius@gmail.com
Jaiku: http://bergie.jaiku.com/
_______________________________________________
dev mailing list
dev@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/dev -
-
Re: [midgard-dev] VOTE: Midgard Release Synchronicity
Thu July 31 2008 10:51:10 UTCHenri Bergius writes:
Hi!
> Midgard Release Synchronicity
> ============================
>
> This is a proposal to move Midgard to a more coordinated release
> process in order to make development more predictable, marketing
> efforts clearer and more focused, and to align ourselves with the
> release synchronicity movement implemented with related projects like
> GNOME and Ubuntu.
Yay :) Let's face it! :)
Piotras
_______________________________________________
dev mailing list
dev@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/dev -
-
Re: [midgard-dev] VOTE: Midgard Release Synchronicity
Thu July 31 2008 11:02:44 UTCA yes from me
/Johan
-
Johan Bernhardsson
Linux/CMS/Network/Cups/Asterisk Consultant
Phone: +46-13-73244
Mobile: +46-705-111751
Fax: +46-13-73190
Email/Jabber/Sip: johan@anykey.se
Web: www.anykey.se
On Thu, 2008-07-31 at 13:34 +0300, Henri Bergius wrote:
> Midgard Release Synchronicity
> ============================
>
> This is a proposal to move Midgard to a more coordinated release
> process in order to make development more predictable, marketing
> efforts clearer and more focused, and to align ourselves with the
> release synchronicity movement implemented with related projects like
> GNOME and Ubuntu.
>
> Some background
> ---------------
>
> * http://www.markshuttleworth.com/archives/150
> * http://coccinella.im/synchronized-releases
> * http://www.midgard-project.org/discussion/developer-forum/read/f2eba8125d7511dda1900b3dd91b5a5c5a5c.html
>
> Actions
> -------
>
> * Clarify naming of different aspects of Midgard: Midgard Platform,
> Midgard MVC, Midgard CMS
> * Combine releases of Midgard and MidCOM into "generations" that are
> compatible with each other and are targeted to specific set of
> dependencies (libgda and PHP versions for instance)
> * Focus on names of the generations instead of individual version
> numbers: thor instead of 1.8 and 2.8, ragnaroek instead of 1.9 and 2.9
> etc
> * Write down a fixed ragnaroek feature list ASAP and prepare for
> release during September
> * Schedule a Midgard developer meeting to October for discussion of
> ragnaroek+1 (former 2.0, vinland?) feature list
> * Switch to git and feature branches after ragnaroek is out
> * Introduce a concept of long-term supported (LTS) releases. Ragnaroek
> will be the first one. LTS means the generation gets fixes at least
> for a few years
>
> Proposed schedule
> -----------------
>
> * Aug 2008: Decision on release syncronicity, ragnaroek beta
> * Sep 2008: Ragnaroek stable, new Midgard website
> * Oct 2008: Ragnaroek+1 planning developer meeting, switch to new PEAR
> channel structure
> * Nov 2008: Git migration, starting automatic builds (and tests?) of
> ragnaroek and ragnaroek+1
> * Feb 2009: Ragnaroek+1 beta
> * Mar 2009: Ragnaroek+1 stable
> * Apr 2009: Ragnaroek+2 planning developer meeting
> * May 2009: Midgard 10th anniversary party, Helsinki, Finland
> * Aug 2009: Ragnaroek+2 beta
> * ...
>
> What is a release?
> ------------------
>
> Release is a launch of same generation of at least Midgard Platform
> and Midgard MVC (MidCOM). CMS may be released a month or two later as
> components may need time to catch up with the generation. This would
> be consistent of the "release waves" approach proposed by Mark
> Shuttleworth, where first wave consists of libraries (Midgard
> Platform, Midgard MVC), second of applications (Midgard CMS), and
> third of distributions.
>
> Release must include:
>
> * Marketing information on the website (/midgard/generationname)
> * Tarballs
> * RPMs, debs, built on opensuse build service
> * Preinstalled images for at least Parallels and VMware
> * Updated/correctly tagged documentation
> * Demo site (both online and as downloadable image)
>
> Automated tests
> ---------------
>
> We all need to learn test-driven development, and actually make unit
> tests for both Midgard and MidCOM, so that we can more easily
> safeguard against regressions when feature branches land into trunk. I
> propose we arrange a unit testing workshop in the next Midgard
> developer meeting.
>
> http://en.wikipedia.org/wiki/Test-driven_development
> -
-
Re: [midgard-dev] VOTE: Midgard Release Synchronicity
Thu July 31 2008 11:21:10 UTCOn Thu, Jul 31, 2008 at 14:34, Henri Bergius <henri.bergius@iki.fi> wrote:
> Midgard Release Synchronicity
> ============================
>
> This is a proposal to move Midgard to a more coordinated release
> process in order to make development more predictable, marketing
> efforts clearer and more focused, and to align ourselves with the
> release synchronicity movement implemented with related projects like
> GNOME and Ubuntu.
As a whole, +1 but I have some little suggestions below.
* Focus on names of the generations instead of individual version
> numbers: thor instead of 1.8 and 2.8, ragnaroek instead of 1.9 and 2.9
> etc
>
May be better to adopt a versioning scheme discussed by Linus?
http://kerneltrap.org/Linux/Kernel_Release_Numbering_Redux
> * Write down a fixed ragnaroek feature list ASAP and prepare for
> release during September
> * Schedule a Midgard developer meeting to October for discussion of
> ragnaroek+1 (former 2.0, vinland?) feature list
My personal preference would be November 1st-4th. This coincides with state
holiday in Russia and it is easier to escape from work. Git conversion can
happen at this stage as well, we might also introduce a gitorious
installation at our git server to facilitate team collaboration.
--
/ Alexander Bokovoy -
-
Re: [midgard-dev] VOTE: Midgard Release Synchronicity
Thu July 31 2008 11:30:00 UTCHi!
On Thu, Jul 31, 2008 at 2:21 PM, Alexander Bokovoy <a.bokovoy@gmail.com> wrote:
> May be better to adopt a versioning scheme discussed by Linus?
> http://kerneltrap.org/Linux/Kernel_Release_Numbering_Redux
So the idea would be to scrap the 1.9, 2.0, 2.1 scheme completely?
With that proposal:
* ragnaroek
- Midgard 2008.09
- MidCOM 2008.09
* vinland
- Midgard 2009.04
- MidCOM 2009.04
etc.
Actually, why not? Having numbers that correspond to generation names,
and which go up with every release would be good for package
management.
Then later patches to ragnaroek MidCOM would be 2008.09.01 etc,
regardless of their release time?
> My personal preference would be November 1st-4th. This coincides with state
> holiday in Russia and it is easier to escape from work.
Would probably work for me too: http://www.dopplr.com/traveller/bergie
Location is another question. Original idea was to go to Rome, but as
Alessio has been mostly offline the arrangements would be a bit
difficult. If nothing else appears, we can go again to Otaniemi or
Linköping, as those two can be arranged very easily and cheaply.
> Git conversion can
> happen at this stage as well, we might also introduce a gitorious
> installation at our git server to facilitate team collaboration.
Sounds like a good idea.
I would like some web-based translation editor there too. Something
like Pootle? http://translate.sourceforge.net/wiki/pootle/index
> / Alexander Bokovoy
/Henri
--
Henri Bergius
Motorcycle Adventures and Free Software
http://bergie.iki.fi/
Skype: henribergius
Jabber: henri.bergius@gmail.com
Jaiku: http://bergie.jaiku.com/
_______________________________________________
dev mailing list
dev@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/dev -
-
Re: [midgard-dev] VOTE: Midgard Release Synchronicity
Thu July 31 2008 11:40:15 UTCHenri Bergius schrieb:
> Hi!
>
> On Thu, Jul 31, 2008 at 2:21 PM, Alexander Bokovoy <a.bokovoy@gmail.com> wrote:
>> May be better to adopt a versioning scheme discussed by Linus?
>> http://kerneltrap.org/Linux/Kernel_Release_Numbering_Redux
>
> So the idea would be to scrap the 1.9, 2.0, 2.1 scheme completely?
>
> With that proposal:
>
> * ragnaroek
> - Midgard 2008.09
> - MidCOM 2008.09
> * vinland
> - Midgard 2009.04
> - MidCOM 2009.04
> etc.
A short practical question: How many suitable names for generations
exist approximately? I'm not really familiar with Northern mythology, so
at least I would run out of names pretty quickly :-)
Also, when using generation names, how can you tell if version xxxx is
newer or older than version yyyyy?
Bye,
Andreas
>
> Actually, why not? Having numbers that correspond to generation names,
> and which go up with every release would be good for package
> management.
>
> Then later patches to ragnaroek MidCOM would be 2008.09.01 etc,
> regardless of their release time?
>
>> My personal preference would be November 1st-4th. This coincides with state
>> holiday in Russia and it is easier to escape from work.
>
> Would probably work for me too: http://www.dopplr.com/traveller/bergie
>
> Location is another question. Original idea was to go to Rome, but as
> Alessio has been mostly offline the arrangements would be a bit
> difficult. If nothing else appears, we can go again to Otaniemi or
> Linköping, as those two can be arranged very easily and cheaply.
>
>> Git conversion can
>> happen at this stage as well, we might also introduce a gitorious
>> installation at our git server to facilitate team collaboration.
>
> Sounds like a good idea.
>
> I would like some web-based translation editor there too. Something
> like Pootle? http://translate.sourceforge.net/wiki/pootle/index
>
>> / Alexander Bokovoy
>
> /Henri
>
_______________________________________________
dev mailing list
dev@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/dev -
-
Re: [midgard-dev] VOTE: Midgard Release Synchronicity
Thu July 31 2008 11:53:26 UTCOn Thu, Jul 31, 2008 at 15:30, Henri Bergius <henri.bergius@iki.fi> wrote:
> Hi!
>
> On Thu, Jul 31, 2008 at 2:21 PM, Alexander Bokovoy <a.bokovoy@gmail.com>
> wrote:
> > May be better to adopt a versioning scheme discussed by Linus?
> > http://kerneltrap.org/Linux/Kernel_Release_Numbering_Redux
>
> So the idea would be to scrap the 1.9, 2.0, 2.1 scheme completely?
>
> With that proposal:
>
> * ragnaroek
> - Midgard 2008.09
> - MidCOM 2008.09
> * vinland
> - Midgard 2009.04
> - MidCOM 2009.04
> etc.
>
> Actually, why not? Having numbers that correspond to generation names,
> and which go up with every release would be good for package
> management.
>
> Then later patches to ragnaroek MidCOM would be 2008.09.01 etc,
> regardless of their release time?
Yep. I don't think we'll have more than 30 point releases between
generations.
Location is another question. Original idea was to go to Rome, but as
> Alessio has been mostly offline the arrangements would be a bit
> difficult. If nothing else appears, we can go again to Otaniemi or
> Linköping, as those two can be arranged very easily and cheaply.
>
Otaniemi is better for me :-)
>
> I would like some web-based translation editor there too. Something
> like Pootle? http://translate.sourceforge.net/wiki/pootle/index
I'd propose to use Transifex. http://www.transifex.org/ which is used by
Fedora Project. Seems much more superior to other solutions.
--
/ Alexander Bokovoy -
-
Re: VOTE: Midgard Release Synchronicity
Thu July 31 2008 12:49:38 UTCI'm +1 with some suggestions:
Testing should be included into the code guidelines so that code without tests cannot be submitted.
This should happen now, as it is important to engineer MidCOM 3 so that every part of the framework is testable.
One thing that we may consider is the Twisted guidelines for code submission: http://twistedmatrix.com/trac/wiki/ReviewProcess
see also:
http://divmod.org/trac/wiki/UltimateQualityDevelopmentSystem
Regards, Tarjei
-
-
Re: [midgard-dev] VOTE: Midgard Release Synchronicity
Thu July 31 2008 13:14:28 UTCAndreas Flack writes:
> Henri Bergius schrieb:
>> Hi!
Hi!
>> So the idea would be to scrap the 1.9, 2.0, 2.1 scheme completely?
>>
>> With that proposal:
>>
>> * ragnaroek
>> - Midgard 2008.09
>> - MidCOM 2008.09
>> * vinland
>> - Midgard 2009.04
>> - MidCOM 2009.04
>> etc.
>
> A short practical question: How many suitable names for generations
> exist approximately? I'm not really familiar with Northern mythology, so
> at least I would run out of names pretty quickly :-)
We would use those names per generation. Not per release.
Generation like ragnaroek is supposed to be LTS so we will use this name
for next years.
> Also, when using generation names, how can you tell if version xxxx is
> newer or older than version yyyyy?
Do you mean minor releases of ragnaroek and vinland released about the
same time?
ragnaroek 2009.5.2
vinland 2009.5.1
?
Piotras
_______________________________________________
dev mailing list
dev@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/dev -
-
Re: [midgard-dev] VOTE: Midgard Release Synchronicity
Thu July 31 2008 13:26:20 UTCPiotr Pokora schrieb:
> Andreas Flack writes:
>> Henri Bergius schrieb:
>>> Hi!
>
> Hi!
>
>>> So the idea would be to scrap the 1.9, 2.0, 2.1 scheme completely?
>>>
>>> With that proposal:
>>>
>>> * ragnaroek
>>> - Midgard 2008.09
>>> - MidCOM 2008.09
>>> * vinland
>>> - Midgard 2009.04
>>> - MidCOM 2009.04
>>> etc.
>> A short practical question: How many suitable names for generations
>> exist approximately? I'm not really familiar with Northern mythology, so
>> at least I would run out of names pretty quickly :-)
>
> We would use those names per generation. Not per release.
> Generation like ragnaroek is supposed to be LTS so we will use this name
> for next years.
>
Ah ok, I was a bit confused there. I thought a new name was needed every
six months
>> Also, when using generation names, how can you tell if version xxxx is
>> newer or older than version yyyyy?
>
> Do you mean minor releases of ragnaroek and vinland released about the
> same time?
>
> ragnaroek 2009.5.2
> vinland 2009.5.1
>
Ok, but then you could go all the way to Ubuntu compatiblity and just
call it ragnaroek 9.05.2. It's also a bit shorter to type :-)
> ?
>
> Piotras
>
> _______________________________________________
> dev mailing list
> dev@lists.midgard-project.org
> http://lists.midgard-project.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
dev@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/dev -
