NDB/Bindings

NDB/Bindings 0.5.6.3.6.6

Cleaned up enum values and other odds and ends.

Milestone information

Project:
NDB/Bindings
Series:
telco-6.3
Version:
0.5.6.3.6.6
Released:
 
Registrant:
NDB/Bindings Developers
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon ndb-connectors-0.5.6.3.6.6.tar.gz (md5) Source Code for NDB/Connectors 12
last downloaded 45 weeks ago
Total downloads: 12

Release notes 

Added explicit keyword to event constructors and calls to BaseEvent constructor
Clean up old files left around
Some fixes for bad enum values

Changelog 

View the full changelog

------------------------------------------------------------
revno: 283
committer: Monty Taylor <email address hidden>
branch nick: telco-6.3
timestamp: Thu 2007-12-06 13:15:14 -0800
message:
  Merged.
    ------------------------------------------------------------
    revno: 192.1.25.1.107.1.21
    committer: Monty Taylor <email address hidden>
    branch nick: devel
    timestamp: Thu 2007-12-06 13:02:06 -0800
    message:
      Made constructors explicit to prevent unexpected type conversions.
    ------------------------------------------------------------
    revno: 192.1.25.1.107.1.20
    committer: Monty Taylor <email address hidden>
    branch nick: devel
    timestamp: Thu 2007-12-06 13:01:46 -0800
    message:
      Added entries to CLEANFILES to clean up old files that might be lying arou
nd.
------------------------------------------------------------
revno: 282
committer: Monty Taylor <email address hidden>
branch nick: telco-6.3
timestamp: Thu 2007-12-06 04:18:25 -0800
message:
  Merged.
    ------------------------------------------------------------
    revno: 192.1.25.1.107.1.19
    committer: Monty Taylor <email address hidden>
    branch nick: devel
    timestamp: Thu 2007-12-06 04:12:19 -0800
    message:
      Make sure we initialize the BaseEvent.
      Put in a workaround for a weird Category of 2... not sure what's up with t
hat.
------------------------------------------------------------
revno: 281
committer: Monty Taylor <email address hidden>
branch nick: telco-6.3
timestamp: Thu 2007-12-06 03:14:09 -0800
message:
  Merged.
    ------------------------------------------------------------
    revno: 192.1.25.1.107.1.18
    committer: Monty Taylor <email address hidden>
    branch nick: devel
    timestamp: Thu 2007-12-06 03:13:17 -0800
    message:
      Readded Connected events... where did those manage to run off to?
------------------------------------------------------------
revno: 280
committer: Monty Taylor <email address hidden>
branch nick: telco-6.3
timestamp: Thu 2007-12-06 02:37:13 -0800
message:
  Merged.
    ------------------------------------------------------------
    revno: 192.1.25.1.107.1.17
    committer: Monty Taylor <email address hidden>
    branch nick: devel
    timestamp: Thu 2007-12-06 02:35:57 -0800
    message:
      Removed non-telco enum values from non-telco tree.
------------------------------------------------------------
revno: 279
committer: Monty Taylor <email address hidden>
branch nick: telco-6.3
timestamp: Thu 2007-12-06 02:33:15 -0800
message:
  Merged
    ------------------------------------------------------------
    revno: 192.1.25.1.107.1.16
    committer: Monty Taylor <email address hidden>
    branch nick: devel
    timestamp: Thu 2007-12-06 02:26:57 -0800
    message:
      Fixed NodeType bug... enum values weren't in the right order.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.