Opened 16 years ago
Closed 16 years ago
#13608 closed enhancement (fixed)
Twenty Ten: screenshot.png needs to be updated
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | WordPress.org | Priority: | lowest |
| Severity: | trivial | Version: | |
| Component: | Themes | Keywords: | needs-patch |
| Focuses: | Cc: |
Description
Search form title (label) is not visible by default due to recent changes. So, 2010 screenshot.png needs to be updated.
Can't submit a patch for that, "photoshopped" probably an option but not the best. Assigning to iammattthomas.
Change History (7)
#2
@
16 years ago
- Milestone changed from 3.0 to WordPress.org site
- Priority changed from normal to lowest
- Severity changed from normal to trivial
- Status changed from new to assigned
#4
follow-up:
↓ 6
@
16 years ago
Yeah, technically, for now. Twenty Ten will be in the theme repo soon enough so we'll be turning it into an external and tracking it through the wp.org milestone. Plus it feels a lot better for this to be off the 3.0 report. :-)
#5
@
16 years ago
nacin, so all new Twenty Ten ticket milestone must be set to WordPress.org site and not 3.0?
There couple of thing that you skipped from previous ticket which I just noticed.
#6
in reply to:
↑ 4
@
16 years ago
Replying to nacin:
Yeah, technically, for now. Twenty Ten will be in the theme repo soon enough so we'll be turning it into an external and tracking it through the wp.org milestone. Plus it feels a lot better for this to be off the 3.0 report. :-)
Interesting. Having a static Milestone makes me a bit nervous. I don't see the disadvantage of using standard milestones to help insure momentum. Further, the updated version will be shipped with a particular version of WordPress.
Can this approach be revisited? I'd prefer to see this marked as milestone 3.1 .
nacin, I think the original category was correct, yes?
The file is wp-content/themes/twentyten/screenshot.png