timeline

110 of 10 results
2.4 series Focus of Development
Latest releases: 2.4.1, 2.4, 2.4-rc3, 2.4-rc2
Bugs targeted: None
Blueprints targeted: None

This release adds
   phpass bcrypt password library implemented for stronger passwords
   ssl is now required to keep passwords secret during login
   added a service churn report
   tab gives a green notification when new messages are sent
   seperate tabs for each message group
   added more confirmation to admin billing and service tools
   tab nav style added to online customer account portal

2.3 series Active Development
Latest releases: 2.3, 2.3-rc1
Bugs targeted: None
Blueprints targeted: None

major new features that attach pdf files to email messages for einvoices and does not move invoiced items to new invoices for credit card reruns.

2.2 series Active Development
Latest releases: 2.2
Bugs targeted: None
Blueprints targeted: None

Includes full documentation, ldap support, and tabs for each message group.

2.1 series Active Development
Latest milestones: 2.1-beta7     Latest releases: 2.1.1, 2.1.1-rc2, 2.1.1-rc1, 2.1.1-beta2, 2.1.1-beta1, 2.1-rc2, 2.1-beta7
Bugs targeted: None
Blueprints targeted: None

This new series adds field asset tracking that allows one to associate field asset items with the services they deliver

2.0-pre-alpha series Active Development
Bugs targeted: None
Blueprints targeted: None

This series is for testing the use of GPG to encrypt the stored credit card numbers. TEST THIS ONLY WITH A BACKUP OF NON-PRODUCTION DATA! You should be familiar with how gpg works before using this pre-alpha test. Once you encrypt your card data there is no backsies without knowing how to use your private key.

2.0-beta series Active Development
Latest releases: 2.0-rc1, 2.0-beta2, 2.0-beta1
Bugs targeted: 3 Fix Released
Blueprints targeted: 1 Deferred, 8 Implemented

The 2.0-beta series is for testing of new features. These features include support for ascii armored openpgp storage of encrypted card data, a "dashboard" for the search and tools pages, sub-notes in customer tickets so it is more like a ticket system with responses stored with that item until it is resolved, and logging of user activity to help meet PCI logging requirements. This logging also makes it possible to see what users have done and show the recent customers they have viewed on their dashboard.

2.0 series Active Development
Latest releases: 2.0.2, 2.0.1, 2.0
Bugs targeted: None
Blueprints targeted: None

The 2.0 series is the current release series.

1.3.2 series Current Stable Release
Latest milestones: 1.3.2-rc1     Latest releases: 1.3.2-release, 1.3.2-rc1, 1.3.2-beta1
Bugs targeted: None
Blueprints targeted: None

This release is the current stable release.

1.3.1 series Obsolete
Latest releases: 1.3.1, 1.3.1-rc2, 1.3.1-rc1, 1.3.1-beta1
Blueprints targeted: None

The 1.3 series is the current active series

trunk series Active Development
Bugs targeted: None
Blueprints targeted: None

The "trunk" series represents the primary line of development rather than a stable release branch. This is sometimes also called MAIN or HEAD.

110 of 10 results