Re: [Mixxx-devel] Mapping export?

[RJ Ryan]

I meant to do this but didn't get it done as part of my controller
preferences work in 2.0. I removed myself from the bug in case someone
wants to take it up:
https://bugs.launchpad.net/mixxx/+bug/1296952
Corresponding import button:
https://bugs.launchpad.net/mixxx/+bug/723028

On Wed, Jan 6, 2016 at 6:18 AM, Ferran Pujol Camins <
ferranpujolcam...@gmail.com> wrote:

> Couldn't Mixxx export mappings that were edited? As far as I can see in
> the controllers section we no longer can, isn't it?
>
>
> --
>
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org
>
>
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] 2.1/2.0.1 plans and development cycle going forth

[Daniel Schürmann]

Hi,

here my view:

* Lets skip 2.0.1
* Cut out a 2.1 branch now, it is already pretty mature and includes a lot
of bugfixes and improvements.
* Start the 2.1 beat phase now and apply only bugfixes to it. We do not
need more features.
* Announce a 2.1 release for KW 11
* Do all planed and pending work for new features in master towards a 2.2.
Release scheduled KW 47.
* Schedule the Release  KW 47 and a 2.2 beta KW 36 (After GSOC 2016)
* If we have something urgent, that is not ready before KW 11, we can
release a 2.1.1 once it is ready.

KW = Week of the year 2016

Will this work for all? Other ideas?


Kind regards,

Daniel.





2016-01-07 7:11 GMT+01:00 Be :

> What are the plans for development going forward? How can we keep Mixxx
> consistently releasing updates without huge gaps between releases? Will
> there be a release of 2.0.1 before 2.1? If so, when, and what will this
> release bring? What is the release date target for 2.1? What can
> reasonably get done in that time?
>
> IMO the focus of 2.1 should be tying up the loose ends of 2.0. In
> particular, inconsistency between the skins should be minimized,
> especially for effects. To be clear, I don't think every skin should be
> the same, but they should all provide access to all of Mixxx's features.
>
> Who plans to work on what for 2.1? Let's set deadlines for ourselves. I
> aim to have at minimum a proof of concept for a JS library by the end of
> January.
>
>
> --
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org
>
>
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] 2.1/2.0.1 plans and development cycle going forth

[Sébastien BLAISOT]

 

I would like to have the new installer for 2.1, but we need to merge
PR744 first, install wix on build server and integrate wix with scons
(I'm waiting for the first manual wix package on the build server to
know if this will work) 

---

Sébastien Blaisot 

Le 07/01/2016 10:31, Daniel Schürmann a écrit : 

> Hi, 
> 
> here my view: 
> 
> * Lets skip 2.0.1 * Cut out a 2.1 branch now, it is already pretty mature and 
> includes a lot of bugfixes and improvements. * Start the 2.1 beat phase now 
> and apply only bugfixes to it. We do not need more features. 
> * Announce a 2.1 release for KW 11 * Do all planed and pending work for new 
> features in master towards a 2.2. Release scheduled KW 47. 
> * Schedule the Release KW 47 and a 2.2 beta KW 36 (After GSOC 2016) 
> * If we have something urgent, that is not ready before KW 11, we can release 
> a 2.1.1 once it is ready. 
> 
> KW = Week of the year 2016 
> 
> Will this work for all? Other ideas? 
> 
> Kind regards, 
> 
> Daniel. 
> 
> 2016-01-07 7:11 GMT+01:00 Be :
> 
>> What are the plans for development going forward? How can we keep Mixxx
>> consistently releasing updates without huge gaps between releases? Will
>> there be a release of 2.0.1 before 2.1? If so, when, and what will this
>> release bring? What is the release date target for 2.1? What can
>> reasonably get done in that time?
>> 
>> IMO the focus of 2.1 should be tying up the loose ends of 2.0. In
>> particular, inconsistency between the skins should be minimized,
>> especially for effects. To be clear, I don't think every skin should be
>> the same, but they should all provide access to all of Mixxx's features.
>> 
>> Who plans to work on what for 2.1? Let's set deadlines for ourselves. I
>> aim to have at minimum a proof of concept for a JS library by the end of
>> January.
>> 
>> --
>> ___
>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
>> http://mixxx.org [1]
>> 
>> Mixxx-devel mailing list
>> Mixxx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [2]
> 
> --
>  
> 
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org [1]
> 
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [2]
 

Links:
--
[1] http://mixxx.org
[2] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] 2.1/2.0.1 plans and development cycle going forth

[Tuukka Pasanen]

Hello,
Should we make some Gnome/KDE base timebased release system or Kernel 
when release is made then have merge window and branch new stable that 
is going to be release in sametime window?


Tuukka

07.01.2016, 11:31, Daniel Schürmann kirjoitti:

Hi,

here my view:

* Lets skip 2.0.1
* Cut out a 2.1 branch now, it is already pretty mature and includes a 
lot of bugfixes and improvements.
* Start the 2.1 beat phase now and apply only bugfixes to it. We do 
not need more features.

* Announce a 2.1 release for KW 11
* Do all planed and pending work for new features in master towards a 
2.2. Release scheduled KW 47.

* Schedule the Release  KW 47 and a 2.2 beta KW 36 (After GSOC 2016)
* If we have something urgent, that is not ready before KW 11, we can 
release a 2.1.1 once it is ready.


KW = Week of the year 2016

Will this work for all? Other ideas?


Kind regards,

Daniel.





2016-01-07 7:11 GMT+01:00 Be >:

What are the plans for development going forward? How can we keep
Mixxx
consistently releasing updates without huge gaps between releases?
Will
there be a release of 2.0.1 before 2.1? If so, when, and what will
this
release bring? What is the release date target for 2.1? What can
reasonably get done in that time?

IMO the focus of 2.1 should be tying up the loose ends of 2.0. In
particular, inconsistency between the skins should be minimized,
especially for effects. To be clear, I don't think every skin
should be
the same, but they should all provide access to all of Mixxx's
features.

Who plans to work on what for 2.1? Let's set deadlines for
ourselves. I
aim to have at minimum a proof of concept for a JS library by the
end of
January.


--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/mixxx-devel




--


___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel


--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] 2.1/2.0.1 plans and development cycle going forth

[Be]

What new features are already in the master branch? If it is mostly bug 
fixes with few new features, then I think it might be more appropriate 
to call the next release 2.0.1.

On 01/07/2016 03:31 AM, Daniel Schürmann wrote:
> Hi,
>
> here my view:only bug
>
> * Lets skip 2.0.1
> * Cut out a 2.1 branch now, it is already pretty mature and includes a
> lot of bugfixes and improvements.
> * Start the 2.1 beat phase now and apply only bugfixes to it. We do not
> need more features.
> * Announce a 2.1 release for KW 11
> * Do all planed and pending work for new features in master towards a
> 2.2. Release scheduled KW 47.
> * Schedule the Release  KW 47 and a 2.2 beta KW 36 (After GSOC 2016)
> * If we have something urgent, that is not ready before KW 11, we can
> release a 2.1.1 once it is ready.
>
> KW = Week of the year 201
>
> Will this work for all? Other ideas?
>
>
> Kind regards,
>
> Daniel.
>
>
>
>
>
> 2016-01-07 7:11 GMT+01:00 Be >:
>
> What are the plans for development going forward? How can we keep Mixxx
> consistently releasing updates without huge gaps between releases? Will
> there be a release of 2.0.1 before 2.1? If so, when, and what will this
> release bring? What is the release date target for 2.1? What can
> reasonably get done in that time?
>
> IMO the focus of 2.1 should be tying up the loose ends of 2.0. In
> particular, inconsistency between the skins should be minimized,
> especially for effects. To be clear, I don't think every skin should be
> the same, but they should all provide access to all of Mixxx's features.
>
> Who plans to work on what for 2.1? Let's set deadlines for ourselves. I
> aim to have at minimum a proof of concept for a JS library by the end of
> January.
>
> 
> --
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org
>
>
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
>

--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] 2.1/2.0.1 plans and development cycle going forth

[Daniel Schürmann]

We have already announced Mixxx 2.1 for Q1 2006:
http://mixxxblog.blogspot.de/

I would like to reserve Versions 2.0.x for urgent fixes on top of the 1.12
branch.
This gives us the freedom to release a quick fix whenever required, without
a beta phase.





2016-01-07 15:04 GMT+01:00 Be :

> What new features are already in the master branch? If it is mostly bug
> fixes with few new features, then I think it might be more appropriate to
> call the next release 2.0.1.
>
> On 01/07/2016 03:31 AM, Daniel Schürmann wrote:
>
>> Hi,
>>
>> here my view:only bug
>>
>> * Lets skip 2.0.1
>> * Cut out a 2.1 branch now, it is already pretty mature and includes a
>> lot of bugfixes and improvements.
>> * Start the 2.1 beat phase now and apply only bugfixes to it. We do not
>> need more features.
>> * Announce a 2.1 release for KW 11
>> * Do all planed and pending work for new features in master towards a
>> 2.2. Release scheduled KW 47.
>> * Schedule the Release  KW 47 and a 2.2 beta KW 36 (After GSOC 2016)
>> * If we have something urgent, that is not ready before KW 11, we can
>> release a 2.1.1 once it is ready.
>>
>> KW = Week of the year 201
>>
>> Will this work for all? Other ideas?
>>
>>
>> Kind regards,
>>
>> Daniel.
>>
>>
>>
>>
>>
>> 2016-01-07 7:11 GMT+01:00 Be >:
>>
>> What are the plans for development going forward? How can we keep
>> Mixxx
>> consistently releasing updates without huge gaps between releases?
>> Will
>> there be a release of 2.0.1 before 2.1? If so, when, and what will
>> this
>> release bring? What is the release date target for 2.1? What can
>> reasonably get done in that time?
>>
>> IMO the focus of 2.1 should be tying up the loose ends of 2.0. In
>> particular, inconsistency between the skins should be minimized,
>> especially for effects. To be clear, I don't think every skin should
>> be
>> the same, but they should all provide access to all of Mixxx's
>> features.
>>
>> Who plans to work on what for 2.1? Let's set deadlines for ourselves.
>> I
>> aim to have at minimum a proof of concept for a JS library by the end
>> of
>> January.
>>
>>
>> --
>> ___
>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
>> http://mixxx.org
>>
>>
>> Mixxx-devel mailing list
>> Mixxx-devel@lists.sourceforge.net
>> 
>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>>
>>
>>
--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] Mapping export?

[Sean M. Pappalardo - D.J. Pegasus]

On 01/06/2016 03:18 AM, Ferran Pujol Camins wrote:
> Couldn't Mixxx export mappings that were edited?

Wouldn't this just be a file copy and rename?

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] 2.1/2.0.1 plans and development cycle going forth

[Sean M. Pappalardo - D.J. Pegasus]

On 01/06/2016 10:11 PM, Be wrote:
> What are the plans for development going forward?

We plan to release 2.0.1 when the outstanding issues are resolved,
within a week or two. (RJ and Owen have a better handle on what we're
waiting on.) I'm working on a couple more controller preset fixes/updates.

We're planning to release 2.1.0 in late March. We'll cut the branch
(feature freeze) by the end of January to allow adequate time for beta
testing and bug-fixing. There are a few items outstanding before we can
cut the branch, which is why doing so is delayed. (Owen and RJ can
provide more detail.) For me, the preferences window Interface pane
cleanup will go into 2.1. It's done, I just need to exhaustively test
then merge it.
(I doubt the skin consistency thing will get done in time, but there
again, we'll do 2.2.0 a few months later.)

For clarity, our version numbers are designated like this:
Major.minor.bugfix

Releases that only fix things that are broken without substantial code
changes will be based off of the current release branch, and those
releases will increment the bugfix number. (E.g. 2.0.1, 2.0.2, etc.) The
first release made from a branch will increment the minor number and
reset the bugfix one. (e.g. 2.1.0 from the 2.1 branch) Subsequent ones
made from that branch will in turn increment the bugfix number (e.g.
2.1.1, 2.1.2, etc.)
The major number would increment whenever we feel like it's appropriate. :)
Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel