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

Open
myrdd opened this Issue Aug 19, 2014 · 7 comments

Comments

Projects
None yet
4 participants
@myrdd
Member

myrdd commented Aug 19, 2014

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.

  • fix important bugs
  • fix compatibility issues – take over options & features from 0.5 so that it won't be a "downgrade"
    • the "strictness" option (#474)
    • the export/import feature (#342)
    • enable/disable auto reload (#466)
    • ... (list not complete)
    • as soon as there are no compatibility issues anymore, remove the warning on the website.
  • blacklist feature (#443)
  • translations
  • don't link to requestpolicy.com anymore
  • ...

In general, all issues that are important for version 1.0.0 will be marked with the 1.0 milestone.

@myrdd myrdd added this to the 1.0.0 milestone Aug 19, 2014

@myrdd myrdd added the discussion label Aug 19, 2014

@myrdd

This comment has been minimized.

Show comment
Hide comment
@myrdd

myrdd Aug 19, 2014

Member

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! :-)

Member

myrdd commented Aug 19, 2014

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! :-)

@anthologist

This comment has been minimized.

Show comment
Hide comment
@anthologist

anthologist Oct 9, 2014

Contributor

Will you put the translations on Babelzilla like the original one or should we translate the files here?

Contributor

anthologist commented Oct 9, 2014

Will you put the translations on Babelzilla like the original one or should we translate the files here?

@nodiscc

This comment has been minimized.

Show comment
Hide comment
@nodiscc

nodiscc Oct 9, 2014

Member

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.)

Member

nodiscc commented Oct 9, 2014

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.)

@anthologist

This comment has been minimized.

Show comment
Hide comment
@anthologist

anthologist Oct 9, 2014

Contributor

@nodiscc thanks, I already translated on github so I'll do it for this addon too. I'll do a pull request very soon.

Contributor

anthologist commented Oct 9, 2014

@nodiscc thanks, I already translated on github so I'll do it for this addon too. I'll do a pull request very soon.

@myrdd

This comment has been minimized.

Show comment
Hide comment
@myrdd

myrdd Sep 2, 2015

Member

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:

  • issue #641 – migrate Mozmill tests to the Marionette framework
  • issues labeled „1.0 vs 0.5“ – features present in 0.5 but missing in 1.0
  • more… TBD
Member

myrdd commented Sep 2, 2015

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:

  • issue #641 – migrate Mozmill tests to the Marionette framework
  • issues labeled „1.0 vs 0.5“ – features present in 0.5 but missing in 1.0
  • more… TBD
@KuenzelIT

This comment has been minimized.

Show comment
Hide comment
@KuenzelIT

KuenzelIT Jan 25, 2018

Is there anything new on releasing 1.0?

KuenzelIT commented Jan 25, 2018

Is there anything new on releasing 1.0?

@myrdd

This comment has been minimized.

Show comment
Hide comment
@myrdd

myrdd Jan 28, 2018

Member

@KuenzelIT the next step is to release a WE version, see #704. After that, I'll head for a 1.0 release.

Member

myrdd commented Jan 28, 2018

@KuenzelIT the next step is to release a WE version, see #704. After that, I'll head for a 1.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment