Hi Paul, Oleg: I don't think I can guarantee a smooth migration, unless you want to > help out. > My managers don't want to invest into such migration without a middle-term advantage. They think that Perforce guys should be responsible for the compatibility since we pay you money ;) I definitely don't want to spend my spare time for such activity.
If we don't end up using the Perforce namespace, I had thought about > splitting the plugin into separate projects > - Is there any need to keep p4-credentials and p4-core separately? - Probably, it could be useful to have p4-api (Credentials, P4Java wrappers, etc.) and p4-scm plugins - p4-labels could be merged with p4-scm I suppose we can go forward with independent workspaces since you agree with such approach Best regards, Oleg Nenashev 2014-06-26 17:53 GMT+04:00 Paul Allen <[email protected]>: > Hi Guys, > > Sorry I missed your earlier emails; it got buried in hundreds of Jenkins > dev emails. > > I'm in the process of moving the project out of the Perforce Workshop into > GitHub. When I'm done you should be able to view the code under: > > https://github.com/p4paul/p4-jenkins > > Oleg: I don't think I can guarantee a smooth migration, unless you want to > help out. > > For the short term a separate namespace might be best, but I will leave > that with you. If we don't end up using the Perforce namespace, I had > thought about splitting the plugin into separate projects: > > p4-core [required] sync, change logging, and repo browsing > p4-credentials [required] server auth > p4-review [optional] Swarm code review > p4-tagging [optional] Labels > > Kind regards, > Paul > > On 24 Jun 2014, at 17:46, Oleg Nenashev <[email protected]> wrote: > > > > Oleg, it sounds like having it in the same namespace might not be > ideal after all? Would you prefer to have it as a separate plugin entirely? > > > > Yes, I think that the same workspace can be used only if Perforce guys > guarantee the smooth migration for users. AFAIK, there's no such short-term > plans, hence I would like to keep plugins separately. > > > > If the new plugin becomes a mainline, we can always deprecate the > existing plugin or to replace it by the migration assistant (which will > depend from the new plugin). > > > > > > > > 2014-06-24 20:09 GMT+04:00 Rob Petti <[email protected]>: > > Let's start with actually uploading it to github. Just create a new > project on your account and push the source to it. > > > > Oleg, it sounds like having it in the same namespace might not be ideal > after all? Would you prefer to have it as a separate plugin entirely? > > > > > > On Friday, 13 June 2014 11:46:50 UTC-6, pallen wrote: > > Hi Guys, > > > > Please can someone help create the branch on GitHub and detail how you > would like me to add the code. > > Strangely enough I know very little about git and GitHub ;-) > > > > My GitHub id is p4paul > > > > In addition to the Wiki notes on version, I could add another page for > the user guide and details of the new plugin. > > > > Thanks, > > Paul > > > > > > On 12 Jun 2014, at 21:20, Oleg Nenashev <[email protected]> wrote: > > > > > 2.0 should be indicate it, but the additional entry on Wiki is > required to explicitly describe the situation. > > > However, the 1.x version is not dead. I'm not sure about the behavior > for common update centers if the 2.x version goes to the main repo. > > > > > > > > > 2014-06-12 23:58 GMT+04:00 Daniel Beck <[email protected]>: > > > > > > On 12.06.2014, at 18:07, Jesse Glick <[email protected]> wrote: > > > > > > > just merge to master, change > > > > 2.0-beta-<n>-SNAPSHOT to 2.0-SNAPSHOT, and release > > > > > > And maybe indicate incompatibility of existing configurations. > > > > > > -- > > > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/v-u3HRvFCi8/unsubscribe. > > > To unsubscribe from this group and all its topics, send an email to > [email protected]. > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > -- > > > 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/d/optout. > > > > > > > > > -------------------------------------------------------------------------------- > > This email and any files transmitted with it are confidential and > intended > > solely for the use of the individual or entity to whom they are > addressed. If > > you have received this email in error please notify the system manager. > Please > > note that any views or opinions presented in this email are solely those > of the > > author and do not necessarily represent those of Perforce Software. > Finally, > > the recipient should check this email and any attachments for the > presence of > > viruses. Perforce Software accepts no liability for any damage caused by > any > > virus transmitted by this email. > > > > Perforce Software UK Ltd is registered in England and Wales as company > no. > > 3816019 at the following address: West Forest Gate, Wellington Road, > Wokingham, > > RG40 2AT, UK > > > -------------------------------------------------------------------------------- > > > > -- > > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/v-u3HRvFCi8/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > 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/d/optout. > > > > > -------------------------------------------------------------------------------- > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If > you have received this email in error please notify the system manager. > Please > note that any views or opinions presented in this email are solely those > of the > author and do not necessarily represent those of Perforce Software. > Finally, > the recipient should check this email and any attachments for the presence > of > viruses. Perforce Software accepts no liability for any damage caused by > any > virus transmitted by this email. > > Perforce Software UK Ltd is registered in England and Wales as company no. > 3816019 at the following address: West Forest Gate, Wellington Road, > Wokingham, > RG40 2AT, UK > > -------------------------------------------------------------------------------- > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/v-u3HRvFCi8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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/d/optout.
