Re: [Openerp-community] Transition to GitHub
On 05/22/2014 09:44 AM, Nhomar Hernández wrote: Oliver. What about lp:openobject-doc? We'll probably move it to a separate GitHub repo, because it could benefit from the online preview and edit capabilities there. I don't suppose many people depend on it being at its current location. We have to adapt the auto-publish scripts though, so it will not happen immediately. A large part of it will be superseded by newer technical (wiki) and functional documentation (Help/FAQ) too, so it may be less relevant in the future. ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] Transition to GitHub
On 05/22/2014 11:01 PM, Graeme Gellatly wrote: Just a question about transition to github and the single branch. Should we consider renaming addons b4 v8 release?, seems a funny name now given we talk of apps and modules and they are core to using the software not really an add on. The difference between a module and an App is defined by the application flag in the manifest. An App is basically a special higher-level business module that encompasses several components (packaged in related modules). There is no difference between a module and an add-on or addon however, the terms can be used interchangeably in our context. Renaming `addons` to `modules` seems superfluous, it's short and the Python namespace seems clean. The addons are just as optional as before, the framework is still a framework and usable without them. It's just easier to have everything in the same repository, with matching revisions of all files, and only one repo to sync. On a related note, to solve the problem with the dual path for addons (currently in openerp/addons and addons), we'll move the addons/* inside openerp/addons before renaming it to odoo[1]. So this will match the namespace even better than before. Layout: odoo/ odoo/addons odoo/addons/account Python Namespace: from odoo.addons import account [1] Code Namespace step of https://github.com/odoo/odoo/wiki/GitHub-Transition ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] Transition to GitHub
On Fri, May 23, 2014 at 1:28 PM, Nhomar Hernández nho...@gmail.com wrote: 2014-05-23 12:51 GMT-05:00 Olivier Dony o...@openerp.com: Yes we'll create similar labels, this will be defined soon and the process explained on the wiki. Cfr https://github.com/odoo/odoo/wiki/GitHub-Transition#bug-reports Ok. I got it. Labels are created I think: https://docs.google.com/file/d/0BxB2ZgxMIR5MQjlYSGlhMF96QmM/edit?usp=drivesdk What I can't see if if we will have a driver team as in Launchpad to help the mark of the bugs, because I see like I don't have the correct ACL to mark bugs as I had in Launchpad (because I was part of the fdriver team I think): https://docs.google.com/file/d/0BxB2ZgxMIR5MS3ZQVXhBVlMxSEU/edit?usp=drivesdk Even creating my own bug it is not possible add a pre-selected label: At github if you are not in the right team you cant label an issue. https://docs.google.com/file/d/0BxB2ZgxMIR5MSXd3QXc3bFA5LWc/edit?usp=drivesdk Did I miss something or we lost this capability? Regards. -- Saludos Cordiales Nhomar G. Hernandez M. +58-414-4110269 Skype: nhomar00 Web-Blog: http://geronimo.com.ve Servicios IT: http://vauxoo.com Linux-Counter: 467724 Correos: nho...@openerp.com.ve nho...@vauxoo.com twitter @nhomar ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- [image: Cristian Salamea on about.me] Cristian Salamea about.me/ovnicraft http://about.me/ovnicraft ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] Transition to GitHub
2014-05-23 13:33 GMT-05:00 Ovnicraft ovnicr...@gmail.com: At github if you are not in the right team you cant label an issue. really ;-)? I knew that jejeje what I am talking about is if Oliver will build the teams. But BTW I checked in my own branches and you can not set correctly a team that only can edit/mark bugs without give access to the branch too. At least I am missing something, we lost this funtionality, Regards. -- Saludos Cordiales Nhomar G. Hernandez M. +58-414-4110269 Skype: nhomar00 Web-Blog: http://geronimo.com.ve Servicios IT: http://vauxoo.com Linux-Counter: 467724 Correos: nho...@openerp.com.ve nho...@vauxoo.com twitter @nhomar ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] Transition to GitHub
On Fri, May 23, 2014 at 8:28 PM, Nhomar Hernández nho...@gmail.com wrote: 2014-05-23 12:51 GMT-05:00 Olivier Dony o...@openerp.com: Yes we'll create similar labels, this will be defined soon and the process explained on the wiki. Cfr https://github.com/odoo/odoo/wiki/GitHub-Transition#bug-reports Ok. I got it. Labels are created I think: The labels still need some updates along with some documentation in the wiki, as we should take this opportunity to update/simplify the process. We'll also use special labels for pull requests. In terms of process we'd like to put a much stronger focus (and resources) on processing pull requests than bugs, because PRs usually contain more direct value for the product. If a bug is important there is also a good chance that someone will quickly write a patch for it, so that works both ways. If we combine GitHub's one-click merge with the ability to tag commits with CI status (runbot/travis), that should make life easier for reviewers, and we hope to be able to merge simple PRs quickly. Of course this means that even more than before, the best way to have a bug looked at/solved is to fix it and make a PR. What I can't see if if we will have a driver team as in Launchpad to help the mark of the bugs, because I see like I don't have the correct ACL to mark bugs as I had in Launchpad (because I was part of the fdriver team I think): https://docs.google.com/file/d/0BxB2ZgxMIR5MS3ZQVXhBVlMxSEU/edit?usp=drivesdk Even creating my own bug it is not possible add a pre-selected label: https://docs.google.com/file/d/0BxB2ZgxMIR5MSXd3QXc3bFA5LWc/edit?usp=drivesdk Did I miss something or we lost this capability? GitHub's bug tracker does not seem to have the necessary flexibility at the moment. We initially thought of putting the issues in a separate repository for this reason, but it was creating other problems (references, etc.) and making things even more confusing. Anyone can comment on bugs and PRs, though, so it is possible to help sorting out everything. ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] Transition to GitHub
2014-05-16 22:00 GMT-05:00 Olivier Dony o...@openerp.com: 12. Functional Doc [In Progress] The functional documentation for v8 is being rewritten/updated and will be published in the form of cookbook recipes on the new Odoo Help platform, as FAQ entries. Selected FAQ entries will be structured with a Table of Contents, and will be editable based on user karma, like other questions/answers. Oliver. What about lp:openobject-doc? Regards. -- Saludos Cordiales Nhomar G. Hernandez M. +58-414-4110269 Skype: nhomar00 Web-Blog: http://geronimo.com.ve Servicios IT: http://vauxoo.com Linux-Counter: 467724 Correos: nho...@openerp.com.ve nho...@vauxoo.com twitter @nhomar ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] Transition to GitHub
Just a question about transition to github and the single branch. Should we consider renaming addons b4 v8 release?, seems a funny name now given we talk of apps and modules and they are core to using the software not really an add on. On 22/05/2014 7:44 PM, Nhomar Hernández nho...@gmail.com wrote: 2014-05-16 22:00 GMT-05:00 Olivier Dony o...@openerp.com: 12. Functional Doc [In Progress] The functional documentation for v8 is being rewritten/updated and will be published in the form of cookbook recipes on the new Odoo Help platform, as FAQ entries. Selected FAQ entries will be structured with a Table of Contents, and will be editable based on user karma, like other questions/answers. Oliver. What about lp:openobject-doc? Regards. -- Saludos Cordiales Nhomar G. Hernandez M. +58-414-4110269 Skype: nhomar00 Web-Blog: http://geronimo.com.ve Servicios IT: http://vauxoo.com Linux-Counter: 467724 Correos: nho...@openerp.com.ve nho...@vauxoo.com twitter @nhomar ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] Transition to GitHub
On 05/21/2014 12:24 PM, Moises Lopez wrote: Where you comment: 3. Runbot [In Progress] New runbot with GitHub integration will be ready soon. Will you add support for GitHub repositories while preserving bzr compatibility too? The new runbot currently only supports GitHub, and it's not sure yet it will support LP/bzr too. If not then we'll simply keep the previous runbot working on LP branches. It could even be consistent with the location of the reference branch for each series, if we decide to keep the official v7 branches on LP. We'd have: runbot v7 = LP v7 branches and earlier, runbot v8 = GitHub branches, v8.) What do you think? There are downsides to having the same series in 2 places, though, as was discussed for the OCA projects. So even if we have to do it in the short term (for compatibility and for translations), we need to consider the pro/cons for the longer term (e.g. extra confusion, keeping 3 separate repositories instead of just one, lp-gh sync needed, harder forward-ports, etc.) ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] Transition to GitHub
@Olivier, Ok, I got it. Thank you for reply. El may 21, 2014 8:12 AM, Olivier Dony o...@openerp.com escribió: On 05/21/2014 12:24 PM, Moises Lopez wrote: Where you comment: 3. Runbot [In Progress] New runbot with GitHub integration will be ready soon. Will you add support for GitHub repositories while preserving bzr compatibility too? The new runbot currently only supports GitHub, and it's not sure yet it will support LP/bzr too. If not then we'll simply keep the previous runbot working on LP branches. It could even be consistent with the location of the reference branch for each series, if we decide to keep the official v7 branches on LP. We'd have: runbot v7 = LP v7 branches and earlier, runbot v8 = GitHub branches, v8.) What do you think? There are downsides to having the same series in 2 places, though, as was discussed for the OCA projects. So even if we have to do it in the short term (for compatibility and for translations), we need to consider the pro/cons for the longer term (e.g. extra confusion, keeping 3 separate repositories instead of just one, lp-gh sync needed, harder forward-ports, etc.) ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] Transition to GitHub
Very good job with the wiki. Thanks. It's nice to see you working after hours to pave the way. Olivier, can you share with us what would be your advice for our branches? One repo per app bundle, one repo per module? Also, what is your recommendation for odoo localization repos naming? And for community app repos? Thanks again, -- PS: escribí este email desde mi teléfono, por favor disculpe la brevedad y cualquier error de escritura. Carlos Vásquez CTO · Director de Ingeniería carlos.vasq...@clearcorp.co.cr CR: +(506) 4000 CORP (4000 2677) US: +1 (786) 472-4267 Cel: +(506) 8351 4484 skype: crvasquez twitter: cvclearcorp 300 m. Este de la Escuela Calle de Platanares 11402 San Jerónimo, Moravia San José, Costa Rica http://www.clearcorp.co.cr On May 16, 2014 9:00 PM, Olivier Dony o...@openerp.com wrote: Hi everyone, The transition from Launchpad to GitHub has just been announced, and it raises many questions. First of all: Don't Panic!(TM) We should not lose anything in the process, and no urgent action is required on your side. The new Odoo wiki at GitHub attempts to give a comprehensive overview of the transition, with the current status for each part: https://github.com/odoo/odoo/wiki/GitHub-Transition Please have a look at it, comment and propose updates. We *do* read all the feedback, even if we do not answer all the time. If you're in a hurry, here is a quick summary of the transition steps and their current status, but please see the wiki page above for more details. It will also be improved and updated as we make progress. 1. Source Code [In Progress] All 3 bzr repos merged into 1 GitHub repo, and shrunk to 400MB, with history and metadata preserved: https://github.com/odoo/odoo All official series/branches converted, `trunk` renamed to `master` (git fashion). See the wiki for more details regarding the repository layout, etc. WARNING: Some work is still being done in the old bzr branches on LP, but everything will be replayed automatically on the GitHub repo in the coming days, using this script[1]. One reason for this activity is the fact that the new runbot working with GitHub is not fully ready yet. The bzr branches can be seen as staging branches that will be merged into GitHub very soon. They will remain available for a while, but will not have the latest changes. 2. Code Namespace [Planned Q2 2014] `import openerp` - `import odoo` to be implemented with backwards-compatibility in v8 3. Runbot [In Progress] New runbot with GitHub integration will be ready soon. 4. Nightly Builds [In Progress] Nightly builds and official installers will soon be updated to use the GitHub repositories 5. Bug Reports [In Progress] All existing bug reports will stay on Launchpad for reference, and will not be duplicated on GitHub, to keep separate namespaces. The option to report new bugs on the official projects on LP will be closed soon, and new issues will have to be reported on GitHub, via https://github.com/odoo/odoo/issues. After closing the bug tracker on LP projects, it will still be possible to search through the old bug reports using google and the umbrella project group[2]. Direct links to LP bug reports will still work. The community documentation will be updated to explain the new process, including milestones, labels, etc. 6. Merge Proposals [In Progress] Similarly to bug reports, existing LP Merge Proposals will stay on LP and should not be automatically transferred to GitHub. This will keep them next to the bugs they reference. Whenever such a MP is merged it can be forwarded to GitHub using the same replay script [1] as the official branches. New contributions should come in the form of GitHub pull requests. Note: No need to create multiple pull requests for the same patch, 7.0 bugfixes are automatically forwarded to 8.0. 7. Translations [Planned Q3 2014] The v8 release is too soon to allow setting up a new translation process on top of GitHub, especially as there is almost nothing built-in. Translators will still continue to work on LP at least until v8 is released. We will set up a replay system to update the translation templates `addons/i18n/*.pot` on LP with the latest terms from master/v8.0 in GitHub. And in the other direction, we will replay the PO updates on `addons/i18n/*.po` from LP to GitHub. After the release of v8 we will set up a new translation process, probably built on top of Transifex. 8. Apps [In Progress] The Apps platform will soon be updated to add support for GitHub repositories (while preserving bzr compatibility). 9. Help / FAQ [Done] Already moved to new platform on https://www.odoo.com/forum - last quirks being fixed at the moment. 10. Mailing Lists [In Progress] Official mailing list will be migrated to odoo.com mail groups [3], as GitHub does not have lists. This will be announced in each mailing-list before shutting them down. Mailing list archives will
