[Gpe-list] [RFC] Coupling GPE release cycle with gnome release cycle

[Paul Sokolovsky]

Hello Koen,

Thursday, January 11, 2007, 3:39:45 PM, you wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Hi,

> What do you think of making gpe releases at the same time gnome does a release? And more
> importantly, use the same versions as gnome does. I'm not proposing to use the same rigid
> freeze cycle and deadlines like gnome has, but to release a gpe version (2.16, 2.18) each
> 6 months, so distribution know when to package, and more importantly, what to package.

> Related to that, I propose to bring some unification into the package versions. Right now
> you have to have followed gpe development pretty closely to know where API changes
> happened, and what packages are affected. My proposal is to bump the core libs and
> applications (gpe-pim, gpe-conf) to 2.17.x in svn and start doing snapshot releases like
> gnome does.

  Well, this means it will follow OPIE's versioning scheme, and I'd
say, it's one of OPIE problems. There're different components of
different purpose and different update frequency and scope. For
example, updates to add new machines detection should be expected to
be frequent, and worth regular updates. And well, many GPE components
yet at <0.5, which means they may have need frequent updates to fix
simple, but major/critical bugs (like easily reproducible segfaults).

  Of course, that doesn't mean they can't use Gnome version as the
base, just support for separate subreleases should be anticipated, for
example, by using nano-versions (4th component).

> The end result should be an easier to understand platform which is easily buildable by
> third parties.

> What do you think?

  My 2 cents.

> regards,

> Koen

> PS: if you think 'gnome' is a bad word, replace it with 'ubuntu' to get the same idea

-- 
Best regards,
 Paul                            mailto:pmiscml at gmail.com