|
Hi There,
Posted this to the user list by accident! Oops :) Just a quick email to request permission to publish a new plugin which we'd like to start using: feature-switch I realise that there are already two plugins for feature switching: Feature Flipper and Feature Toggle. We've opted to not contribute/modify these plugins for a number of reasons: - Neither of these plugins have any tests (it would need to be a complete ground-up rewrite anyway) - Neither plugin works in Grails 2.x (One blows up quite spectacularly) - Code style in one of the plugins is sub-optimal - re-factoring without tests is a huge risk. - One plugin looks like an experiment and is definitely not "production ready" - Roughly 1 year since each plugin has been maintained Hopefully in the near future we could discuss merging or deprecating existing plugins if they are no longer maintained. There are plans to add an admin page to the plugin also. The source code can be viewed here - https://github.com/aiten/grails-feature-switch - your feedback is appreciated. Cheers, Antony -- ________________________________ ꜽ . antony jones . http://www.enzy.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Hi Antony,
Just a quick couple of observations: Do you have any documentation for this ? Also, the scm + issue management properties probably need to be uncommented+defined in your Plugin definition file. Eamonn On 21 August 2012 11:15, Antony Jones <[hidden email]> wrote: > Hi There, > > Posted this to the user list by accident! Oops :) > > Just a quick email to request permission to publish a new plugin which > we'd like to start using: feature-switch > > I realise that there are already two plugins for feature switching: > Feature Flipper and Feature Toggle. We've opted to not > contribute/modify these plugins for a number of reasons: > > - Neither of these plugins have any tests (it would need to be a > complete ground-up rewrite anyway) > - Neither plugin works in Grails 2.x (One blows up quite spectacularly) > - Code style in one of the plugins is sub-optimal - re-factoring > without tests is a huge risk. > - One plugin looks like an experiment and is definitely not "production ready" > - Roughly 1 year since each plugin has been maintained > > Hopefully in the near future we could discuss merging or deprecating > existing plugins if they are no longer maintained. There are plans to > add an admin page to the plugin also. > > The source code can be viewed here - > https://github.com/aiten/grails-feature-switch - your feedback is > appreciated. > > Cheers, > Antony > > -- > ________________________________ > ꜽ . antony jones . http://www.enzy.org > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Hey Eammon,
Ah yes - forgot the SCM url. Documentation is on the way :) Cheers, Antony On 21 August 2012 10:26, Eamonn O'Connell <[hidden email]> wrote: > Hi Antony, > > Just a quick couple of observations: > > Do you have any documentation for this ? > > Also, the scm + issue management properties probably need to be > uncommented+defined in your Plugin definition file. > > Eamonn > > On 21 August 2012 11:15, Antony Jones <[hidden email]> wrote: >> Hi There, >> >> Posted this to the user list by accident! Oops :) >> >> Just a quick email to request permission to publish a new plugin which >> we'd like to start using: feature-switch >> >> I realise that there are already two plugins for feature switching: >> Feature Flipper and Feature Toggle. We've opted to not >> contribute/modify these plugins for a number of reasons: >> >> - Neither of these plugins have any tests (it would need to be a >> complete ground-up rewrite anyway) >> - Neither plugin works in Grails 2.x (One blows up quite spectacularly) >> - Code style in one of the plugins is sub-optimal - re-factoring >> without tests is a huge risk. >> - One plugin looks like an experiment and is definitely not "production ready" >> - Roughly 1 year since each plugin has been maintained >> >> Hopefully in the near future we could discuss merging or deprecating >> existing plugins if they are no longer maintained. There are plans to >> add an admin page to the plugin also. >> >> The source code can be viewed here - >> https://github.com/aiten/grails-feature-switch - your feedback is >> appreciated. >> >> Cheers, >> Antony >> >> -- >> ________________________________ >> ꜽ . antony jones . http://www.enzy.org >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- ________________________________ ꜽ . antony jones . http://www.enzy.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
> Ah yes - forgot the SCM url.
> > Documentation is on the way :) Is it important to publish the plugin before the documentation is available? -- Peter Ledbrook Developer Advocate VMware t: @pledbrook --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Documentation has been added - https://github.com/aiten/grails-feature-switch
On Tue, Aug 21, 2012 at 11:36 AM, Peter Ledbrook <[hidden email]> wrote: >> Ah yes - forgot the SCM url. >> >> Documentation is on the way :) > > Is it important to publish the plugin before the documentation is available? > > -- > Peter Ledbrook > Developer Advocate > VMware > > t: @pledbrook > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
In reply to this post by antony
> Hopefully in the near future we could discuss merging or deprecating
> existing plugins if they are no longer maintained. There are plans to > add an admin page to the plugin also. You might be interested in platform-core and platform-ui for that. > The source code can be viewed here - > https://github.com/aiten/grails-feature-switch - your feedback is > appreciated. It's perhaps a matter of taste, but I think it's better to point the docs URL at the README blob directly, rather than the default page for the plugin on GitHub. If you have a lot of folders/files in your project, the README is pushed below the fold of the page otherwise. And one final thing: which usernames would you like to have permission to publish? :) Peter -- Peter Ledbrook Developer Advocate VMware t: @pledbrook --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Hi Peter,
> You might be interested in platform-core and platform-ui for that. Not looked into these yet, but it seems like a good excuse! > It's perhaps a matter of taste, but I think it's better to point the > docs URL at the README blob directly, rather than the default page for > the plugin on GitHub. If you have a lot of folders/files in your > project, the README is pushed below the fold of the page otherwise. Will change this ASAP The usernames to publish are 'antony' :) Cheers, Antony On 21 August 2012 12:45, Peter Ledbrook <[hidden email]> wrote: >> Hopefully in the near future we could discuss merging or deprecating >> existing plugins if they are no longer maintained. There are plans to >> add an admin page to the plugin also. > > You might be interested in platform-core and platform-ui for that. > >> The source code can be viewed here - >> https://github.com/aiten/grails-feature-switch - your feedback is >> appreciated. > > It's perhaps a matter of taste, but I think it's better to point the > docs URL at the README blob directly, rather than the default page for > the plugin on GitHub. If you have a lot of folders/files in your > project, the README is pushed below the fold of the page otherwise. > > And one final thing: which usernames would you like to have permission > to publish? :) > > Peter > > -- > Peter Ledbrook > Developer Advocate > VMware > > t: @pledbrook > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- ________________________________ ꜽ . antony jones . http://www.enzy.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
> The usernames to publish are 'antony' :)
Done. I thought Tomas and others might want to publish it too. Peter -- Peter Ledbrook Developer Advocate VMware t: @pledbrook --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Tomas doesn't look fazed :)
On 21 August 2012 13:51, Peter Ledbrook <[hidden email]> wrote: >> The usernames to publish are 'antony' :) > > Done. I thought Tomas and others might want to publish it too. > > Peter > > -- > Peter Ledbrook > Developer Advocate > VMware > > t: @pledbrook > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- ________________________________ ꜽ . antony jones . http://www.enzy.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Powered by Nabble | Edit this page |
