WordPress.org

Making WordPress.org

Opened 5 years ago

Closed 4 years ago

#648 closed defect (fixed)

2.1.x branch for BuddyPress on translate.wordpress.org

Reported by: boonebgorges Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords: close
Cc:

Description

nacin - a few weeks ago, when 2.1 was released, you and I had a discussion about how BP strings had not been syncing over to translate.wordpress.org, and so when we released 2.1 we agreed that it made sense to feed 2.1 language packs from the Development branch, so there'd just be one place for translators to do their work.

Now that a number of our most popular languages are fully translated https://translate.wordpress.org/projects/buddypress/dev, we'd like to set up a 2.1.x branch. This is particularly important because we're about to start active development on BP 2.2, which means there may be string changes in trunk; if that happens, the Development translations will dip below 100% and will stop shipping to new installations.

Change History (14)

#1 in reply to: ↑ description @nacin
5 years ago

Replying to boonebgorges:

This is particularly important because we're about to start active development on BP 2.2, which means there may be string changes in trunk; if that happens, the Development translations will dip below 100% and will stop shipping to new installations.

At the moment, the 2.1 branch is being imported into dev, not trunk, so any changes to trunk will not affect translations.

#2 @boonebgorges
5 years ago

Ah, ok, that definitely makes it less urgent. We have had a bit of confusion from translators about the missing branch, so it would be good to get it up sometime soonish, but this puts my mind at ease a bit. Thanks for the clarification.

This ticket was mentioned in Slack in #buddypress by boone. View the logs.


5 years ago

#4 @slaFFik
5 years ago

I'm one of that confused translators. Doing this for BuddyPress for 6 years already (ru_RU).

Right now developers work with 2.2 functionality in trunk. But here we all see 2.0 branch only, and no 2.1. So Development is the current stable 2.1 or new in-progress 2.2? All reference links in Development lead to trunk, so it seems we just don't have 2.1.

Is it possible to clarify all this and finally streamline the process? All translators will be really happy.

#5 @DJPaul
5 years ago

  • Cc djpaul@… added

@nacin can you clarify this for slaFFik? I'm assuming the situation is the same as what you said originally, since I'm not aware of any changes since then. Thanks.

This ticket was mentioned in Slack in #buddypress by djpaul. View the logs.


5 years ago

This ticket was mentioned in Slack in #polyglots by mercime. View the logs.


5 years ago

This ticket was mentioned in Slack in #buddypress by boone. View the logs.


5 years ago

#9 @DJPaul
5 years ago

Since this ticket was created, a 2.1 branch has recently mysteriously appeared.

This ticket was mentioned in Slack in #buddypress by djpaul. View the logs.


5 years ago

This ticket was mentioned in Slack in #polyglots by netweb. View the logs.


4 years ago

This ticket was mentioned in Slack in #meta-i18n by netweb. View the logs.


4 years ago

#13 @netweb
4 years ago

  • Keywords close added

BuddyPress 2.2.x branch is now live (2.1.x is also live) with strings copied from /dev

BuddyPress 2.3.x development will use the current /dev branch

I think everything is now up to date based on the original ticket description.

#14 @ocean90
4 years ago

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.