[Uim] Development reformation: New versioning and release process

[YamaKen]

Hi there,

I've realized that my explanation was lacking actual examples
considerably. See following application and figures to
complement my previous message. And I'll post a short-term
roadmap to 1.1.0 soon.

- next stable version is 1.0.0
- 0.5 series (a "development series") will be discontinued
- any development release is named as trunk-snapshotYYYYMMDD from now
- major version is incremented to indicate conclusion of a
  long-term development phase
- 1.0 will be branded to indicate the conclusion of traditional
  uim architecture, and 2.0 may for the composer framework. I
  have no idea about 3.0 at now


how to branch:

     now     alpha  beta  final   1.0.1  1.0.2
      |    +---+-----+------+(------+------+--...) 1.0 branch      +-- 1.1
      v    |                                                       |
--+--------+----------------+-------------------------+------------+-- trunk
0.5.0      ^      trunk-snapshot20051201    trunk-snapshot20051215
           |
     feature freeze



major upgrade:

     +--- 1.0     +--- 1.1     +--- 1.2     +--- 2.0     +--- 2.1
     |            |            |            |            |         
-----+------------+------------+------------+------------+--- trunk
                                            ^
                                            |
              no special branching even if major version has been incremented



how patchlevel is treated:

                                     not extended if no fixes are backported
                                                      |
         alpha  beta  final   1.0.1           1.0.2   v
      +----+-----+------+-------+---------------+                1.0 branch
      | ^ ^ ^         ^      ^                 ^
      | | | |<-fixes->|      |backport (a)     |backport (b)
------+--------------------+-----------------+------------------ trunk
      ^                    ^                 ^
      |                    |                 |
feature freeze         a bugfix (a)      another fix (b)


At Mon, 28 Nov 2005 11:42:36 +0900,
ashie at homa.ne.jp wrote:
> On Sun, 27 Nov 2005 19:20:55 +0100
> Jeroen Ruigrok/asmodai <asmodai at in-nomine.org> wrote:
> 
> > Increasing a minor version would mean 4 -> 5.  What you increment in the
> > example seems to be the patchlevel.
> > Or have I misunderstood?
> 
> I think Yamaken-san meant that previous versioning rule which was used
> at "0.4.8 -> 0.4.9" may lead user's misunderstanding. (Both "0.4.8" and
> "0.4.9" are marked as stable release in previous versioning rule.)
> 
> So he want to increment minor version like "0.4.x -> 0.5.0" in new
> versioning rule when such changes (like done at "0.4.8 -> 0.4.9") are
> made.

Thanks. The Takuro's explanation is what I meant.

But "0.4.8 -> 0.4.9" was not a good example since it contains
minor changes only.

In another example, we had added a new feature
'uim-module-manager' between "0.4.7.1 -> 0.4.8" in the old
versioning scheme. But if such change is appeared in the new
scheme, it increments minor version as "1.1.1 -> 1.2.0".

-------------------------------
YamaKen  yamaken at bp.iij4u.or.jp