Dolibarr 6.0 freeze

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Dolibarr 6.0 freeze

Laurent Destailleur

Hi Dolibarr developers.


Time to start the beta of the next major version has come. The release candidate version should be ready for end of June, so as usual, we must start the beta period several weeks before, so now.

So, starting from next week-end, the beta period for 6.0 will be launched. No new features will be added from PR.

As usual, "started development" are allowed to be continued to be finished for final release. Work on not stable modules are also still opened because such modules won't be visible by end users.  Among works already started and that are qualified to continue to push non bug fixed PR, we may find:

- work on advanced accountancy (double party) module to finished/make stable changes done during development period,  

- new variant module

- work on look and feel standardization

- code to make online payment process standardized (this include work on module "stripe").

- translation changes

- changes required to allow package generations


After the freeze, new features will be suspended until the branch for 6.0 is created. Then merging PR for new features will be possible again into develop branch.

Also, architecture, re-engineering, or best practice code enhancements will be discarded during this period. Instead any help is welcome to fix all opened bug: See https://github.com/Dolibarr/dolibarr/issues

More information on what a "freeze" mean: https://wiki.dolibarr.org/index.php/Category:RoadMap


Version 6.0 beta period should be shorter as usual. It has a very good compatibility behavior with external modules, so you can already check your external modules are still working with this version, even if freeze is done in few days only.

The Changelog into develop branch does not contains for the moment list of new features, but you can read to get information on what was changed and may need attention of external developers or upgraders.


Also, note that maintenance versions for branch 4 and 5 should be released soon to provide recent bug and security fixes available.

More information on what a "maintenance version" mean: https://wiki.dolibarr.org/index.php/Category:RoadMap


Laurent Destailleur, aka Eldy


------------------------------------------------------------------------------------

_______________________________________________
Dolibarr-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
Reply | Threaded
Open this post in threaded view
|

Re: Dolibarr 6.0 freeze

Hubert Andriolo
Hello Eldy, and dear dolibarr developpers

We were working on our side, for a core modification to make possible, the return in stock of products already shipped.

In the process now, there is no possibility to "modify"selectively products of a shipment, 
it is necessary to delete all articles of shipment (and it puts back those articles in stock) when pressing delete button and make shipment again (sometimes my shipments are with 100 articles, and 3 batch/dlc per products, which is "very" long.
/expedition/card.php?id=11386&action=delete

it could be nice to be able to "reopen" shipment, add articles of the stock (preferably with origin on the order), and/or delete "articles" of the shipment, mistakenly added.

Sometimes my logistics team make some mistake and take products with short expiry dates, and have to chage the shipment (clear these articles from shipment or replace them by articles with longer expiry dates).

Could this be added to 6.0 milestone, or is it too late ? 

Are there any developpers having this problem too ? 

We could link this feature request with "credit notes" for products sent back form customers, that have to be recorded back in stock ?

Thanks for you answer

HubZ

2017-05-13 18:00 GMT+02:00 <[hidden email]>:
Send Dolibarr-dev mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Dolibarr-dev digest..."


Today's Topics:

   1. Upgrading from git to git. (Sasa Ostrouska)
   2. Dolibarr 6.0 freeze (Laurent Destailleur)


----------------------------------------------------------------------

Message: 1
Date: Fri, 12 May 2017 18:48:55 +0000
From: Sasa Ostrouska <[hidden email]>
To: Posts about Dolibarr development and coding
        <[hidden email]>
Subject: [Dolibarr-dev] Upgrading from git to git.
Message-ID:
        <CALFERdw_GN57DhgUvjij-bKwXQQMtMwM0qMVW2he=[hidden email]>
Content-Type: text/plain; charset="utf-8"

Hi, it is a while that i am upgrading my install from git to git.
In the updates made today and on 5th of May i got the following error
when running the installer:

Errore DB_ERROR_1452: ALTER TABLE llx_supplier_proposaldet ADD CONSTRAINT
fk_supplier_proposaldet_fk_unit FOREIGN KEY (fk_unit) REFERENCES
llx_c_units (rowid);
Cannot add or update a child row: a foreign key constraint fails
(`banco_dolibarr`.`#sql-4a2_f81b`, CONSTRAINT
`fk_supplier_proposaldet_fk_unit` FOREIGN KEY (`fk_unit`) REFERENCES
`llx_c_units` (`rowid`))

First time I got this error was whne updating from git of devel branch
dated April 12, 2017 and updating to git of May 5th 2017.

I also filled a bug on github[1] at the time.

Does anybody have an idea on why this is happening and if it is harmful ?

Rgds
Saxa


[1]https://github.com/Dolibarr/dolibarr/issues/6803
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/dolibarr-dev/attachments/20170512/2a50f337/attachment.html>

------------------------------

Message: 2
Date: Sat, 13 May 2017 14:01:45 +0200
From: Laurent Destailleur <[hidden email]>
To: ML Dolibarr dev <[hidden email]>
Subject: [Dolibarr-dev] Dolibarr 6.0 freeze
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset="utf-8"

Hi Dolibarr developers.


Time to start the beta of the next major version has come. The release
candidate version should be ready for end of June, so as usual, we must
start the beta period several weeks before, so now.

So, starting from next week-end, the beta period for 6.0 will be launched.
No new features will be added from PR.

As usual, "started development" are allowed to be continued to be finished
for final release. Work on not stable modules are also still opened because
such modules won't be visible by end users.  Among works already started
and that are qualified to continue to push non bug fixed PR, we may find:

- work on advanced accountancy (double party) module to finished/make
stable changes done during development period,

- new variant module

- work on look and feel standardization

- code to make online payment process standardized (this include work on
module "stripe").

- translation changes

- changes required to allow package generations


After the freeze, new features will be suspended until the branch for 6.0 is
created. Then merging PR for new features will be possible again into
develop branch.

Also, architecture, re-engineering, or best practice code enhancements will
be discarded during this period. Instead any help is welcome to fix all
opened bug: See https://github.com/Dolibarr/dolibarr/issues

More information on what a "freeze" mean: https://wiki.dolibarr.or
g/index.php/Category:RoadMap


Version 6.0 beta period should be shorter as usual. It has a very good
compatibility behavior with external modules, so you can already check your
external modules are still working with this version, even if freeze is
done in few days only.

The Changelog into develop branch does not contains for the moment list of
new features, but you can read to get information on what was changed and
may need attention of external developers or upgraders.


Also, note that maintenance versions for branch 4 and 5 should be released
soon to provide recent bug and security fixes available.

More information on what a "maintenance version" mean:
https://wiki.dolibarr.org/index.php/Category:RoadMap


Laurent Destailleur, aka Eldy


------------------------------------------------------------------------------------
Google+: https://plus.google.com/+LaurentDestailleur-Open-Source-Expert/
Facebook: https://www.facebook.com/Destailleur.Laurent
Twitter: http://www.twitter.com/eldy10
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/dolibarr-dev/attachments/20170513/4902eff9/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
Dolibarr-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev


------------------------------

End of Dolibarr-dev Digest, Vol 168, Issue 5
********************************************


_______________________________________________
Dolibarr-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
Reply | Threaded
Open this post in threaded view
|

Re: Dolibarr 6.0 freeze

cam.lafit@azerttyu.net
HI

I've found some typo on SOAP webservice since 4.0 code.

I've got :
-* some error on webservice declaration,
-* error on user loading (actioncom can't act)
-* and need to add a new webservice.

I know SOAP should be deprecated to RESET but code is again present on
all branches and some externals services as dolispip use it again. A
big refactoring must be done before to be rest call compliant

Where to push these PR ? Looks possible to do a backport on old branches ?


Thanks

Km

_______________________________________________
Dolibarr-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
Reply | Threaded
Open this post in threaded view
|

Re: Dolibarr 6.0 freeze

Laurent Destailleur (aka Eldy)
For errors, you can push PR on 5.0 branch.

For new web services into develop branch.


2017-05-16 11:10 GMT+02:00 [hidden email] <[hidden email]>:
HI

I've found some typo on SOAP webservice since 4.0 code.

I've got :
-* some error on webservice declaration,
-* error on user loading (actioncom can't act)
-* and need to add a new webservice.

I know SOAP should be deprecated to RESET but code is again present on
all branches and some externals services as dolispip use it again. A
big refactoring must be done before to be rest call compliant

Where to push these PR ? Looks possible to do a backport on old branches ?


Thanks

Km

_______________________________________________
Dolibarr-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev



--
------------------------------------------------------------------------------------
Google+: https://plus.google.com/+LaurentDestailleur-Open-Source-Expert/
Facebook: https://www.facebook.com/Destailleur.Laurent
------------------------------------------------------------------------------------
* Dolibarr (Project leader): https://www.dolibarr.org (make a donation for Dolibarr project via Paypal: [hidden email])
* AWStats (Author) : http://awstats.sourceforge.net (make a donation for AWStats project via Paypal: [hidden email])
* AWBot (Author) : http://awbot.sourceforge.net
* CVSChangeLogBuilder (Author) : http://cvschangelogb.sourceforge.net



_______________________________________________
Dolibarr-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
Reply | Threaded
Open this post in threaded view
|

Re: Dolibarr 6.0 freeze

Sasa Ostrouska
In reply to this post by Hubert Andriolo
Hi Hubert,

On Tue, May 16, 2017 at 8:27 AM, Hubert Andriolo <[hidden email]> wrote:
Hello Eldy, and dear dolibarr developpers

We were working on our side, for a core modification to make possible, the return in stock of products already shipped.


Thats a great feature. A kind of back order. Very useful IMHO.

In the process now, there is no possibility to "modify"selectively products of a shipment, 
it is necessary to delete all articles of shipment (and it puts back those articles in stock) when pressing delete button and make shipment again (sometimes my shipments are with 100 articles, and 3 batch/dlc per products, which is "very" long.
/expedition/card.php?id=11386&action=delete

it could be nice to be able to "reopen" shipment, add articles of the stock (preferably with origin on the order), and/or delete "articles" of the shipment, mistakenly added.

Sometimes my logistics team make some mistake and take products with short expiry dates, and have to chage the shipment (clear these articles from shipment or replace them by articles with longer expiry dates).

Could this be added to 6.0 milestone, or is it too late ? 

I have no idea for this question.
 
Are there any developpers having this problem too ? 

For me this feature for sure would be very useful. In our business of spare parts we ofetn see missing items on a shipment.

Another thing I would like to see is a possibility to define a transporter for some certain order. Has anybody solved this in some way already ?
 
We could link this feature request with "credit notes" for products sent back form customers, that have to be recorded back in stock ?


Yes , why not, it is the correct way in my view.
 
Thanks for you answer

HubZ


Rgds
Saxa

_______________________________________________
Dolibarr-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev