-
Notifications
You must be signed in to change notification settings - Fork 35
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
milestone: first stable 1.0 version #446
Comments
By the way, I'd like to say that I'm very happy already about the activity in this new repository! I think that we're on a good way to "reactivate" this project. Keep up the good work! :-) |
Will you put the translations on Babelzilla like the original one or should we translate the files here? |
hi @anthologist I think we should accept translations directly here on github (no need to setup a project on babelzilla, no need to check babelzilla before releasing), but maybe babelzilla could bring us more translators? The process for translation on github is fairly easy (eg. go to https://github.com/RequestPolicyContinued/requestpolicy/blob/dev-1.0/src/locale/fr/requestpolicy.dtd, click the "Edit" button and do a pull request. It should be documented in the wiki.) |
@nodiscc thanks, I already translated on github so I'll do it for this addon too. I'll do a pull request very soon. |
It's important to have 1.0 stable before Electrolysis gets into Firefox Release. Since the wiki page says that could happen end of 2015, it's quite urgent. So in the next time I'll do especially release-critical tasks. Those are:
|
Is there anything new on releasing 1.0? |
@KuenzelIT the next step is to release a WE version, see #704. After that, I'll head for a 1.0 release. |
I consider creating a first stable 1.0 version the most important issue on this project. As there have been quite some changes between the latest 0.5 version and the current 1.0 beta, I'd like to use this page to discuss what needs to be done before we will release 1.0.0 stable.
In this first post, I'll summarize what needs to be done. This means, the following list is only a first proposal and definitely not complete. I'd like to invite everyone to participate especially in this discussion.
In general, all issues that are important for version 1.0.0 will be marked with the 1.0 milestone.
The text was updated successfully, but these errors were encountered: