All,
The project repository was migrated to GitHub:
https://github.com/FirebirdSQL/firebird
Please wait a few days for things to settle down, we need to update some
infrastructure. SVN repository is still accessible, but new
contributions are expected to be provided as pull requests at GitHub.
On 15/03/16 02:24, Jim Starkey wrote:
> The combination of cmake and git submodules would let the Firebird
> project to be decomposed in clean, separate, architecturally independent
> projects, a win-win all around.
The key statement there is the 'combination of'. Although the facilities
provide
On 3/14/2016 8:29 AM, Michal Kubecek wrote:
> On Mon, Mar 14, 2016 at 11:20:34AM +, Lester Caine wrote:
>> The fact that git does not handle modular projects at all well was my
>> main objection to being forced to use it. CVS had it's faults, but also
>> it's good points, and being able to crea
On Mon, Mar 14, 2016 at 11:20:34AM +, Lester Caine wrote:
>
> The fact that git does not handle modular projects at all well was my
> main objection to being forced to use it. CVS had it's faults, but also
> it's good points, and being able to create a release made from cherry
> picked parts o
On 13/03/16 22:03, Jim Starkey wrote:
> Splitting the code base would strengthen the underlaying architecture,
> spotlight unnecessary dependencies, and promote cleaner and better
> inter-component interfaces. And, in theory at least, various components
> could be released independently.
The fact
Dmitry,
For qa we only need these projects:
https://github.com/firebirdsql/qa-fbtest (qa tools)
https://github.com/firebirdsql/qa-repository (formerly fbt-repository -
this is repository with tests and other data used by qa tools)
https://github.com/firebirdsql/oltp-emul
"benchmark" is very old
On 2016-03-13 22:47, Egor Pugin wrote:
>> qa-fbtest ... firebird-qa-fbtest
>
> Both looks good. If you're planning to have other 'qa' projects like
> 'jaybird-qa*' second is better.
I can't speak for other projects, but for Jaybird the tests are an
integral part of the codebase (as they usually a
Might this be a good time to restructure the code into separate
projects, maybe:
* Engine
* Remote interface
* Y-valve
* Server (exclusive of Y-valve and engine, etc)
* Utilities
* Common code
Splitting the code base would strengthen the underlaying architecture,
spotlight unnecessary de
> qa-fbtest ... firebird-qa-fbtest
Both looks good. If you're planning to have other 'qa' projects like
'jaybird-qa*' second is better.
Finally, you can rename repositories very easy anytime.
On 13 March 2016 at 23:16, Dmitry Yemanov wrote:
> 13.03.2016 19:10, Egor Pugin wrote:
>>
>> As I unders
13.03.2016 19:10, Egor Pugin wrote:
>
> As I understand 'qa' in svn is a directory, not a project. Github does
> not support hierarchical structure. In 'qa' dir there are some repos:
> 'benchmark', 'fbtest', 'fbt-repository' etc.
> So, you'll have:
> https://github.com/firebirdsql/firebird
> https:
13.03.2016 17:36, Adriano dos Santos Fernandes wrote:
>
>> If the latter, then I agree that we should better replace "core" with
>> either "firebird" or "server".
>
> With "server" I disagree, as our core code is not only server.
Well, I'm pretty sure mariadb/server includes also the client librar
+1
13 марта 2016 г. 7:15 PM пользователь "Mark Rotteveel"
написал:
> On 13-3-2016 17:10, Egor Pugin wrote:
> > Jaybird repos will be prefixed as you wrote.
> > https://github.com/firebirdsql/jaybird
> > https://github.com/firebirdsql/jaybird-manual
> >
> > It's an option to move Jaybird to its ow
On 13-3-2016 17:10, Egor Pugin wrote:
> Jaybird repos will be prefixed as you wrote.
> https://github.com/firebirdsql/jaybird
> https://github.com/firebirdsql/jaybird-manual
>
> It's an option to move Jaybird to its own account. So you won't mix
> repos with same names.
> https://github.com/jaybird
> How should the docs and QA be located?
As I understand 'qa' in svn is a directory, not a project. Github does
not support hierarchical structure. In 'qa' dir there are some repos:
'benchmark', 'fbtest', 'fbt-repository' etc.
So, you'll have:
https://github.com/firebirdsql/firebird
https://github
Em 13/03/2016 07:22, Dmitry Yemanov escreveu:
>
> If the latter, then I agree that we should better replace "core" with
> either "firebird" or "server".
>
With "server" I disagree, as our core code is not only server.
Adriano
-
02.03.2016 16:16, Egor Pugin wrote:
> What about just 'firebird'? 'core' is misleading.
> It does not matter that the same word repeats in address. See:
> https://github.com/git/git
> https://github.com/FFmpeg/FFmpeg
> https://github.com/openssl/openssl
> and many others...
Let's look at closer e
On 2016-03-03 1:19, Adriano dos Santos Fernandes wrote:
> Em 02/03/2016 11:14, Michal Kubecek escreveu:
>> On Wed, Mar 02, 2016 at 10:45:35AM -0300, Adriano dos Santos
>> Fernandes wrote:
>>> Em 02/03/2016 09:31, Michal Kubecek escreveu:
On Wed, Mar 02, 2016 at 02:18:27PM +0300, Dmitry Yemano
Em 02/03/2016 11:14, Michal Kubecek escreveu:
> On Wed, Mar 02, 2016 at 10:45:35AM -0300, Adriano dos Santos Fernandes wrote:
>> Em 02/03/2016 09:31, Michal Kubecek escreveu:
>>> On Wed, Mar 02, 2016 at 02:18:27PM +0300, Dmitry Yemanov wrote:
Firebird Project will be moving its repositori
Hi,
> Firebird Project will be moving its repositories to GitHub soon.
> I'm asking present contributors to create accounts there. If anyone
> (including past contributors) wants your past commits to be
> automatically linked to your GitHub account and be shown in the
> statistics, please repo
Em 02/03/2016 15:37, Egor Pugin escreveu:
> One more reason is that you do not have 'core' word in svn address.
> You have 'firebird/trunk/...' and not 'core/trunk/...'.
>
So, we fixed the previous mistake. ;)
Adriano
One more reason is that you do not have 'core' word in svn address.
You have 'firebird/trunk/...' and not 'core/trunk/...'.
On 2 March 2016 at 21:27, Dmitry Yemanov wrote:
> 02.03.2016 16:16, Egor Pugin wrote:
>
>> What about just 'firebird'? 'core' is misleading.
>> It does not matter that the s
02.03.2016 16:16, Egor Pugin wrote:
> What about just 'firebird'? 'core' is misleading.
> It does not matter that the same word repeats in address. See:
> https://github.com/git/git
> https://github.com/FFmpeg/FFmpeg
> https://github.com/openssl/openssl
> and many others...
Personally, I don't ha
ind Regards,
> Arno Brinkman
>
>
>
> -Oorspronkelijk bericht-
> From: Dmitry Yemanov
> Sent: Wednesday, March 2, 2016 12:18 PM
> To: For discussion among Firebird Developers
> Subject: [Firebird-devel] GitHub
>
> All,
>
> Firebird Project will be moving its
I understand i need to create a GitHub account then.
When will the transistion start?
Kind Regards,
Arno Brinkman
-Oorspronkelijk bericht-
From: Dmitry Yemanov
Sent: Wednesday, March 2, 2016 12:18 PM
To: For discussion among Firebird Developers
Subject: [Firebird-devel] GitHub
All
02.03.2016 14:16, Egor Pugin wrote:
> What about just 'firebird'? 'core' is misleading.
It matches component name in tracker.
--
WBR, SD.
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
A
On Wed, Mar 02, 2016 at 10:45:35AM -0300, Adriano dos Santos Fernandes wrote:
> Em 02/03/2016 09:31, Michal Kubecek escreveu:
> > On Wed, Mar 02, 2016 at 02:18:27PM +0300, Dmitry Yemanov wrote:
> >>
> >> Firebird Project will be moving its repositories to GitHub soon.
> >
> > Is the fact that the
Em 02/03/2016 09:31, Michal Kubecek escreveu:
> On Wed, Mar 02, 2016 at 02:18:27PM +0300, Dmitry Yemanov wrote:
>>
>> Firebird Project will be moving its repositories to GitHub soon.
>
> Is the fact that the git repository hasn't been updated since Sunday
> (and therefore has no B3_0_Release branc
What about just 'firebird'? 'core' is misleading.
It does not matter that the same word repeats in address. See:
https://github.com/git/git
https://github.com/FFmpeg/FFmpeg
https://github.com/openssl/openssl
and many others...
On 2 March 2016 at 15:57, Dmitry Yemanov wrote:
> 02.03.2016 15:53, Di
02.03.2016 15:53, Dimitry Sibiryakov wrote:
> Am I alone who has no idea what the name is?..
https://github.com/FirebirdSQL/core
Dmitry
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM +
02.03.2016 13:47, Dmitry Yemanov wrote:
> The repo name is likely to remain the same.
Am I alone who has no idea what the name is?..
--
WBR, SD.
--
Site24x7 APM Insight: Get Deep Visibility into Application Perfor
02.03.2016 15:44, Dimitry Sibiryakov wrote:
> 02.03.2016 12:18, Dmitry Yemanov wrote:
>> Firebird Project will be moving its repositories to GitHub soon.
>
> Will be a new repository created?
The current mirror repo will be replaced with a freshly imported one.
The repo name is likely to rem
02.03.2016 12:18, Dmitry Yemanov wrote:
> Firebird Project will be moving its repositories to GitHub soon.
Will be a new repository created?
--
WBR, SD.
--
Site24x7 APM Insight: Get Deep Visibility into Applicatio
On Wed, Mar 02, 2016 at 02:18:27PM +0300, Dmitry Yemanov wrote:
>
> Firebird Project will be moving its repositories to GitHub soon.
Is the fact that the git repository hasn't been updated since Sunday
(and therefore has no B3_0_Release branch) related to this migration
or is it a different probl
On 02/03/16 11:18, Dmitry Yemanov wrote:
> Firebird Project will be moving its repositories to GitHub soon.
As someone who has had to put up with the less than useful manor that
'github' handles code on-line can I pass on a useful approach that I've
found makes it a lot less painful ;)
Mercurial
All,
Firebird Project will be moving its repositories to GitHub soon.
I'm asking present contributors to create accounts there. If anyone
(including past contributors) wants your past commits to be
automatically linked to your GitHub account and be shown in the
statistics, please report your a
35 matches
Mail list logo
