Nicolas Williams wrote: >>>4.5.2 Exported Interfaces >>> +------------------------------------------------------------------+ >>> | NAME | PROPOSED | DESCRIPTION | >>> | | STABILITY LABEL | | >>> +-----------------------+-----------------+------------------------+ >>> | SUNWunison | Uncommitted | Unison package | >>> |-----------------------+-----------------+------------------------| >>> | /usr/bin/unison | Committed | Unison executable | >>> |-----------------------+-----------------+------------------------| >>> | ~/.unison/default.prf | Uncommitted | Unison default profile | >>> +------------------------------------------------------------------+ >>> >>> >>I probably shouldn't repeat this, but I am again concerned about >>Committed for an application that seems to have a somewhat limited >>audience and may itself no longer be actively developed or maintained. >>(See http://www.cis.upenn.edu/~bcpierce/unison/status.html for that >>status information.) This is all the more so given the above >>limitations, which it now seems are unlikely to be resolved given the >>development status. >> >> > >I agree. Make it Obsolete, make it Uncommitted or Volatile and add a >note explaining what changes might be coming, if any. > > > According to the message from the community web site, there is no active development on this product any more. While bug fixes, small improvements and contributed patches may come. So I suggested to use Committed level. If members think this is not proper, please let me know and it will be fixed.
-Frank
