Ticket #2425 (closed enhancement: fixed)
Implement dotted activity versions to sugar 0.92
| Reported by: | godiard | Owned by: | erikos |
|---|---|---|---|
| Priority: | Normal | Milestone: | 0.92 |
| Component: | sugar | Version: | Unspecified |
| Severity: | Unspecified | Keywords: | |
| Cc: | godiard | Distribution/OS: | Unspecified |
| Bug Status: | New |
Description
When we are supporting old releases, we need to update activities but without changing the version number, because there are activities released with the next numbers.
For example, in sugar 0.84 we are using Browse 108, the last version of Browse is 112. We need to create a new activity, but can't be 109, because exists, and we don't want to inhibit future updates.
Another use case is we can need create a modified activity to a unique group, by example a deployment, then we can create the activity Browse 108.1-peru
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

