Girvin R. Herr wrote
> Now I know why I keep getting 3.x update notices when 4.x has been 
> released some time ago.  That surprised, but pleased, me.  As a result 
> of your description, I will have to repackage and install 3.6.7 after my 
> monthly backup today.

Absolutely, there is nothing wrong with continuing to use the earlier

Just be aware that the 3.6.x minor release will be designated EOL
development status the 15th of this month.  Meaning, it is a final release
(for the minor and 3.6 major branch) "No further patches will be accepted
for the release" and no project effort to fix compatibility or security
issues.  Support will continue in the mail list forum and the Ask site as
well as Bugzilla issue tracking---but quality of that support will slack off
as fewer users maintain a 3.6.x branch install.


This graphic from the release plan presents a concise view of the project.  
With work on the "master" branch extending into the future, each minor
release branch is categorized as "release canidate", for "Early adopters",
for "Recommended" use, for "Conservative" use.

With its EOL eminent, using 3.6.7 you would be well in the "Conservative"
category--meaning simply that it is not the Project recommended category,
which has shifted to the 4.0 major release--a 4.0.4 build.  Please note,
that when released at the end of the month--the 4.0.5 build will also
transition to a conservative category. 

But as you say, what ever works best for your "productivity", we just want
you and others to understand the project infrastructure and how best they
can contribute.


View this message in context:
Sent from the Users mailing list archive at

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted

Reply via email to