PHP PEAR Questions and Answers - BC rules for existing package and HTML

You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author

BC rules for existing package and HTML_Progress real case

Laurent Laville

2004-08-08, 8:55 pm

I've a question for the QA team.

After 3 release candidate of package HTML_Progress, i've decided to let down
for a while
usage of PEAR_ErrorStack for error management (until it become stable).
So i've wrote a plugin architecture to allows any error handling system.

On my way to rewrite a version without PEAR dependency, i've completed today
on my localhost a merge version of the 3 main classes
HTML_Progress + HTML_Progress_UI + HTML_Progress_DM
into the same classe : HTML_Progress
All methods in UI and DM (that are not yet present in core) are now included
in main (core) class HTML_Progress.

Is it a BC rule ?
Shall i change the version to HTML_Progress2
or may i just use the version 1.2.0 ready to publish ?

I've still to complete the doc, but all code is ready to be commit to CVS.

What should i do ?

Laurent Laville

Sponsored Links