Skip to:
Content

BuddyPress.org

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#6174 closed enhancement (fixed)

Update readme.txt

Reported by: johnjamesjacoby's profile johnjamesjacoby Owned by: johnjamesjacoby's profile johnjamesjacoby
Milestone: 2.2 Priority: normal
Severity: normal Version:
Component: Core Keywords: 2nd-opinion needs-patch
Cc:

Description

Let's do the standard readme.txt sweep before 2.2 goes out.

  • Anything we want to change?
  • Anything we want to remove?
  • Any words or terminology we no longer think applies?
  • How do we feel about tone?
  • How are our screen shots looking?
  • Are there any videos out there worth linking to?

Change History (12)

#1 @johnjamesjacoby
10 years ago

In 9425:

Update readme.txt in trunk in preparation for next week's 2.2 launch.

  • Bump stable tag
  • Bump testet up to
  • Add link to 2.2 codex page
  • https all applicable links to avoid the bounce

See #6174.

#2 @mercime
10 years ago

Tested up to: 4.1

#3 follow-up: @slaFFik
10 years ago

WordPress 4.1.1 will be released like starting next week (seems @nacin said somewhere, not sure though).

#4 follow-up: @netweb
10 years ago

What versions of WordPress does BuddyPress support?

Currently it's 3.6: Requires at least: 3.6, nothing explicitly comes to mind requiring the bump in required version, except for an opportunity to remove a or a couple of older versions (3.7 & 3.8) from Travis CI speeding up CI reporting.

#5 in reply to: ↑ 3 @netweb
10 years ago

Replying to slaFFik:

WordPress 4.1.1 will be released like starting next week (seems @nacin said somewhere, not sure though).

With Tested up to: 4.1 this includes minor releases such as v4.1.1 AFAIK.

#6 @netweb
10 years ago

Not quite the readme but closely related, update Author URI: http://buddypress.org/community/members/ to a valid URL, the current URL http://buddypress.org/community/members/ is not valid and redirects to http://buddypress.org:

Two instances:

Last edited 10 years ago by netweb (previous) (diff)

#7 @johnjamesjacoby
10 years ago

In 9431:

Remove references to old /community URL. See #6174.

#8 in reply to: ↑ 4 ; follow-up: @johnjamesjacoby
10 years ago

Replying to netweb:

What versions of WordPress does BuddyPress support?

Currently it's 3.6: Requires at least: 3.6, nothing explicitly comes to mind requiring the bump in required version, except for an opportunity to remove a or a couple of older versions (3.7 & 3.8) from Travis CI speeding up CI reporting.

I'd selfishly like to bump this for these reasons, but I think a few others see it as a badge of honor. Let's revisit this in 2.3.

#9 @johnjamesjacoby
10 years ago

  • Owner set to johnjamesjacoby
  • Resolution set to fixed
  • Status changed from new to closed

In 9432:

Update readme.txt for 2.2's imminent release:

  • Clearer installation instructions
  • More detailed activation instructions & setup
  • Update description paragraphs (based on recent bbPress improvements)
  • Inviting tone
  • Refreshing new fragrance
  • Pairs well with dark chocolate
  • Wash, rinse, repeat. Always repeat.

Fixes #6174.

#10 @johnjamesjacoby
10 years ago

In 9433:

Fix editorial snafoo from r9432, and add a Q&A about "how BuddyPress makes money." See #6174.

#11 in reply to: ↑ 8 @netweb
10 years ago

Replying to johnjamesjacoby:

Replying to netweb:

What versions of WordPress does BuddyPress support?

Currently it's 3.6: Requires at least: 3.6, nothing explicitly comes to mind requiring the bump in required version, except for an opportunity to remove a or a couple of older versions (3.7 & 3.8) from Travis CI speeding up CI reporting.


I'd selfishly like to bump this for these reasons, but I think a few others see it as a badge of honor. Let's revisit this in 2.3.

I agree with this, it is an honour, and I am selfish also!

#12 @netweb
10 years ago

P.s. For reference, WP 3.6 was only removed from the Travis CI testing as it was going to be to complex to configure the pre and post switch to WordPress' new "develop" repo with /src and /build folders, see r8017.

Note: See TracTickets for help on using tickets.