Posted by brmassa on May 31, 2007 at 8:25am
Guys,
is there a schedule or deadlines to ecommerce development?
How to define wich features should be created/updated to new releases?
There are more than 50 issues marked as "Patch - review" and hundreds of active issues to be evaluated.
I believe its important to determinate a deadline or a footprint to next releases. Its good to do a follow up and see cleary where we are on slow motion and where we are advancing well.
regards,
massa
Comments
Hi massa Welcome to the ec
Hi massa
Welcome to the ec team!
I haven't done much since the v3 release, but just after v3 happened we created a list of goals. This should give you a useful idea of where people's heads are at. I don't think you can deadline this, unfortunately schedules are only possible when you accurately know your resources. Also, these goals change with the people who are actually doing them, so you will bring your own ideas and goals to the table - you should add them in.
The queue for ec is deadly. It hovers at 20+ pages constantly. I sometimes update this page to try and see where all the action is. On 2 or 3 occasions in the previous year, I have battled to close 5 or 6 pages of issues (yes, like 100+ tickets!), only to have them build up again within a month.
Hope some of this info helps a bit. Look forward to trying live subproducts.
Cheers
.s
Schedules
Simon,
Great list of goals. im gonna contribute with that soon.
I really most agree athat Issues list is deadly! i updated 50 issues past few days but its already growing again.
about schedules: why not release a monthly release for v3? there are so many small fixed issues that many users will be benefited from. v3dev has many fixes from v3-0. It also reduces the number of duplicated issues. Keeping this code only on dev wont help much or even possibly not help anyone if takes so long to be replaced by v4. Now, it seems like the famous Microsoft Service Packs for WinXP: one each 2 years.
regards,
massa
Release cycle depends on how
Release cycle depends on how much time Gordon has had to be confident there are no "gotchas". Another symptom of the size of the project.
Commits
Hi Guys,
I am pretty sure that if some of the patches in the queue were committed, we would see quite a large reduction in some of the issues coming through. While there is always a risk that more could be created, the queue is certainly not shrinking as users opt for the release version 3 (which has some major issues), and not for the dev version.
Cheers
Superstar