[geeklog-devel] Geeklog 1.8.0 release schedule

[Tom]

Hmmmm....

>> So the plugins could indicate that they require 1.8.0b1 (or 1.8.0hg), but
that looks odd

I agree and it may confuse some users.

I am not sure if this would work but could we make the new version check
just worry about the 1.8.0 part and anything past the third number will be
assumed to be compatible? This would mean no new features or DB changes
could take place in a beta, service release, etc. I am not sure if this
would work for how Geeklog JP distinguishes between their upgraded japan
versions of some plugins though...

Another idea would be to have a standard way for beta, service release and
release candidate version numbers.

For example if 1.8.0b## is found then it is assumed a beta and will consider
1.8.0 and 1.8.0b## to be compatible.

We could then use sr for service release (1.8.0sr##) and rs for release
candidate (or whatever we decide)

I think I like the second idea better

Tom

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: March-27-11 12:33 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule

I ran into a tiny little last-minute problem ...

I've set the Geeklog version number to 1.8.0b1. All the bundled plugins
require Geeklog 1.8.0. Due to the new version check, however, they all
refuse to install since 1.8.0b1 < 1.8.0

Oops ...

Not sure how to go from here. The comparison is correct - it's the data that
isn't. So the plugins could indicate that they require 1.8.0b1 (or 1.8.0hg),
but that looks odd, though it would be technically correct.

Opinions?

bye, Dirk

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://eight.pairlist.net/mailman/listinfo/geeklog-devel