Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update topic.py #52

Closed
wants to merge 1 commit into from
Closed

Update topic.py #52

wants to merge 1 commit into from

Conversation

oduvan
Copy link

@oduvan oduvan commented Jun 12, 2015

No description provided.

@nitely
Copy link
Owner

nitely commented Jun 12, 2015

Is there a way to automatically fix the string for every (locale) translation?

To fix this, I'd just translate that string in the english locale. Since we have a transifex project, it should be fixed there.

@nitely
Copy link
Owner

nitely commented Jun 12, 2015

Here there is a related stackoverflow question, it seems there is no way to fix this (other than search&replace) for every locale file.

The translation files are out of date at the moment, I'll update them (sync them to transifex) in the experimental branch and let you know when that's done, in case you want to submit another pull request.

@nitely nitely closed this Jun 12, 2015
@oduvan
Copy link
Author

oduvan commented Jun 12, 2015

Where can I read about this experemental branch?

What is inside?

When it is going to be released?

What issues are holding it from releasing?

@nitely
Copy link
Owner

nitely commented Jun 12, 2015

Here there are all the current branches. I made many changes to the project structure, mostly. I think the only real thing keeping me from releasing it is that it has not been deployed to community.spirit-project.com. I will try to get to it this weekend.

@oduvan
Copy link
Author

oduvan commented Jun 12, 2015

Right now we are using it here https://forum.empireofcode.com while closed beta testing

@oduvan
Copy link
Author

oduvan commented Jun 23, 2015

Hi :)

When do you think we can update it?

@nitely
Copy link
Owner

nitely commented Jun 23, 2015

Hi!

I've decided to make all the breaking changes I want before releasing it, ie: there wont be a way to directly upgrade from 0.1 to 0.4 but the upgrade path will be from 0.1 to 0.3 and then to 0.4 instead.
I don't want to force people to do something like that in future releases, other than the next one (no way to avoid it AFAIK). This is coz I'm changing the structure to an app composed by apps (ie: spirit.apps.comments, spirit.apps.topic, etc) instead of a big app.

So, I'm making sure everything will go smoothly after the next release, that's why it's taking so long.

You can expect the next Spirit to be released two weeks from now.

@nitely nitely mentioned this pull request Jun 23, 2015
@auvipy
Copy link

auvipy commented Jun 23, 2015

that would be a better to move on moduler approach

@auvipy
Copy link

auvipy commented Jun 27, 2015

version 3.0 released? when it will be?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants