Maybe a simple web ui would do too, as I think not all devs have “voice” on IRC (and maybe not all should have) on the other hand, one is not forced to use these versions and maybe a user with “voice” can create the version if required. /Domi
On 12.01.2014, at 19:41, Slide <[email protected]> wrote: > That would be great, though I am not sure all plugin developers hang out on > IRC, it would definitely be a start though. I'll take a look at it. > > > On Sun, Jan 12, 2014 at 11:25 AM, Dominik Bartholdi <[email protected]> wrote: > Maybe we can add another command to the IRC bot? > /Domi > > On 12.01.2014, at 18:36, Slide <[email protected]> wrote: > >> Would these be controller by the plugin developers? I can see a problem if >> admins have to add the versions every time. Some plugins have a pretty rapid >> development cycle compared to others. >> >> Thanks, >> >> slide >> >> >> On Sun, Jan 12, 2014 at 3:11 AM, Dominik Bartholdi <[email protected]> wrote: >> A while a go we had a discussion about reorganizing JIRA as a whole, I think >> someone was going to to a "prove of concept” with things like: >> - separate projects for each plugin >> - a naming convention for versions of different components. >> >> I don’t know what happen to that POC, but I think the first one is quite >> hard to change a time present, as we have already such a huge history of >> issues. >> But I guess the second would be quite easy to do, e.g. versions could be >> prefixed with the component id >> - scriptler-1.1 >> - parameterized-trigger-2.16 >> >> /Domi >> >> On 11.01.2014, at 23:48, Slide <[email protected]> wrote: >> >>> The "current" version tag is almost completely useless if you are looking >>> back at bugs from a while ago. Users could be on what they _think_ is >>> current, but it could be old. Can we please remove this as a possible >>> version so that people can't use it? >>> >>> slide >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> -- >> Website: http://earl-of-code.com >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > Website: http://earl-of-code.com > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
