Hi Charles,
How the heck can there be a
2.0.1 RC version when there has NEVER even been a stable 2.0.0 version
My plan was to release the RC in july this year ... ?
There will be never a stabil version 2 with an even number at the end.
- even = dev
- odd = production
The first public release
On 11/25/2009, Thomas Eckardt/eck (thomas.ecka...@thockar.com) wrote:
My plan was to release the RC in july this year ... ?
There will be never a stabil version 2 with an even number at the end.
- even = dev
- odd = production
Oh, right, I forgot about that... ;)
The first public release
Chris,
Or to say it a better way we
haven't used it since it want down oh so long ago
But it's available for over a half year now, hosted by SF.
Thomas
-Chris Franklin cfrank...@nomadcf.com schrieb: -
An: ASSP development mailing list assp-test@lists.sourceforge.net
Von: Chris
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
Or to say it a better way we
haven't used it since it want down oh so long ago. When the guy that
hosted it and the forums left.
For the record:
The Griplist was NOT teared down when M.E. left the project.
We decided to move
At 08:20 AM 11/25/2009, Thomas Eckardt/eck wrote:
this is just implemented. Configure 'Notify' and 'NotifyRe' to watch for
the logentry that there is a new version available and you'll get your
email about that event.
But I think version that you has installed, is simply t old!
Nope,
After some hours of thinking - in my humble opinion a autoupdate feature
could break too much. Not only that there could features changed, removed
or added that could break the users spam fighting, there are also some
important dependencies for the used (or not) plugins. It is so easy to
important dependencies for the used (or not) plugins.
Totally agree.but, ASSP already checks for minimum compatibility levels
for perl modules during startup. Surely it's not difficult to do the same
for an auto-update?
Of course, I'm not comparing difficulty of coding vs time to do it.
