[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Needs suggestion.

Hi all.

I'm the maintainer of the cocoon2 and cocoon packages. The new
stable release of cocoon is cocoon2 which implies that no
more development will be done on the cocoon branch. The problem
is that it is really a major change and I do not know
if I upset people if I rename the cocoon2 package to cocoon and
removes the cocoon2 from the archive.

I could just keep the cocoon2 package name but I do not want to
maintain the cocoon package (old version) because it is old,
buggy and not as flexible as cocoon2 is.

I need a suggestion on what I should do. What is a proper
procedure. A debconf message indicating the big change?


// Ola

 --------------------- Ola Lundqvist ---------------------------
/  opal@debian.org                     Björnkärrsgatan 5 A.11   \
|  opal@lysator.liu.se                 584 36 LINKÖPING         |
|  +46 (0)13-17 69 83                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /

Reply to: