| Summary: | meta-bug for digikam editor tool release (digikam devels only) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | sero4linux |
| Component: | ImageEditor-Plugins | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | wishlist | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.5.0 | |
Seb, Using B.K.O to make a meta-bug is not the right way. NEWS and TODO files from svn are used for that and are includes to source tarballs. I close this file now. Gilles Caulier |
Version: 0.9.0-beta1 (using KDE KDE 3.5.2) OS: Linux In preparation of the 0.9.0-beta1 release I thought it might be a good idea to create this "meta"-bug for all entries from b.k.o that have to be solved before the release. This gives the devels the chance to collect all release-relevent entries of b.k.o by linking them here ("depends on"). I hope this way the packager (me or Tom usally) gets an good overview when the tarballs can be created for the release. If you are not a member of the digikam team but a user, please don't use this meta-bug (fill separete reports on b.k.o if you think we missed something important). NOTE: this meta-bug is for the "beta1" release only and only relevant for digikamimageplugins - digikam gets its own meta-bug (cause the tarballs are independent of each other). If we want to release in sync with kipi/*-plugins then I recomment the kde-imaging people to create meta-bugs, too so we can coordinate the release date. Please keep this report as clean as possible, e.g. discuss release related things on the MLs if possible. Regards, Sero