[Maria-developers] MariaDB 10.1 is now on github!
Hi! I'm happy to announce that MariaDB-10.1 tree has been completely migrated to github. Since now on we'll use github for the new development in MariaDB. It's https://github.com/MariaDB/server, go on, fork it, hack around, submit pull requests. Have fun! Older trees (10.0, 5.5, 5.3, 5.2, 5.1) are not on github - we do hope to migrate them too eventually, but at the moment they are still on launchpad. If you're a maria-captain on launchpad - for you to get write access to the mariadb repository on github you need to tell me your github account name. Regards, Sergei P.S.: Don't forget that 10.1 is still *pre-alpha*. You've been warned.
Hi Sergei, Do you plan to integrate GitHub commit on JIRA as well ? Thanks, Jocelyn Le 25/05/2014 22:09, Sergei Golubchik a écrit :
Hi!
I'm happy to announce that MariaDB-10.1 tree has been completely migrated to github. Since now on we'll use github for the new development in MariaDB. It's https://github.com/MariaDB/server, go on, fork it, hack around, submit pull requests. Have fun!
Older trees (10.0, 5.5, 5.3, 5.2, 5.1) are not on github - we do hope to migrate them too eventually, but at the moment they are still on launchpad.
If you're a maria-captain on launchpad - for you to get write access to the mariadb repository on github you need to tell me your github account name.
Regards, Sergei
P.S.: Don't forget that 10.1 is still *pre-alpha*. You've been warned.
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
2014-05-25 23:09 GMT+03:00 Sergei Golubchik <serg@mariadb.org>:
I'm happy to announce that MariaDB-10.1 tree has been completely migrated to github. Since now on we'll use github for the new
Hurray! I can't wait to do pull requests on the 10.1 tree using pure git workflow all the way :) -- Check out our blog at http://seravo.fi/blog and follow @ottokekalainen
Awesome job! I note the last tag is mariadb-10.0.10; just wondering if say I fix a bug or make an improvement (in my case, in oqgraph) and make a pull request against this repo, what the procedure would be for backporting to 10.0.12 say? Would the process be as simple as generating a patch from the relevant github changes and then reposting that to the mail list / JIRA issue? Would there still be a need to maintain my own branch on bzr? thanks, Andrew On 26/05/14 05:39, Sergei Golubchik wrote:
Hi!
I'm happy to announce that MariaDB-10.1 tree has been completely migrated to github. Since now on we'll use github for the new development in MariaDB. It's https://github.com/MariaDB/server, go on, fork it, hack around, submit pull requests. Have fun!
Older trees (10.0, 5.5, 5.3, 5.2, 5.1) are not on github - we do hope to migrate them too eventually, but at the moment they are still on launchpad.
If you're a maria-captain on launchpad - for you to get write access to the mariadb repository on github you need to tell me your github account name.
Regards, Sergei
P.S.: Don't forget that 10.1 is still *pre-alpha*. You've been warned.
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
Hi, Andrew! On May 26, Andrew McDonnell wrote:
Awesome job!
I note the last tag is mariadb-10.0.10; just wondering if say I fix a bug or make an improvement (in my case, in oqgraph) and make a pull request against this repo, what the procedure would be for backporting to 10.0.12 say?
Yes, I have 10.0 and older trees in my local git repository. The only reason I didn't push them - to avoid pull requests for thees that we still maintain on launchpad. So, for 10.0 you still need to do a merge request on launchad or submit a patch, e.g. attach it to the jira issue. I hope we'll move other trees soon, but as they're GA, it's safer not to disrupt them now and polish all the procedures on 10.1 first.
Would the process be as simple as generating a patch from the relevant github changes and then reposting that to the mail list / JIRA issue? Would there still be a need to maintain my own branch on bzr?
Yes, I believe it'll work. If you create a branch based on, say, 10.0.10 tag, that should be, basically, a 10.0.10 tree. Just remember - you commit a fix in your git tree, export it as a patch, we apply to 10.0, push, release, tag, you pull into your git tree - and you'll have a merge conflict to resolve. It shouldn't be a big issue though. Whether you want a bzr branch on launchpad is up to you. But, indeed, I don't see what it could be useful for. Regards, Sergei
participants (4)
-
Andrew McDonnell -
Jocelyn Fournier -
Otto Kekäläinen -
Sergei Golubchik