Preparing for an 'official' public alpha...

Nao

  • Dadman with a boy
  • Posts: 16,061
Preparing for an 'official' public alpha...
« on February 6th, 2014, 02:36 PM »
So, basically, could we establish a list of what I forgot to fix, implement or generally do to the codebase in order to make a viable public release..?

Thanks! There are so many topics right now, I feel it'll be faster if everyone chips in!

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: Preparing for an 'official' public alpha...
« Reply #1, on February 6th, 2014, 03:03 PM »Last edited on February 6th, 2014, 11:56 PM
Ok, just a very small list :)
  • User settings for "Home" in admin
  • Adding a user setting for HTML notificatons in admin
  • Like notifications on thoughts done
  • Fixing Moderation Filters
Yeah. That's all?
# dpkg-reconfigure brain
error: brain is not installed or configured

MultiformeIngegno

  • Posts: 1,337

Norodo

  • Oh you Baidu, so randumb. (60 sites being indexed at once? Jeez)
  • Posts: 469
Re: Preparing for an 'official' public alpha...
« Reply #4, on February 6th, 2014, 03:24 PM »
I don't think you should have one to be honest. People will be whining about database changes, not being able to upgrade easily, and everything else from heaven to hell.

I think once the DB is set and there is an upgrade path, the software is ready to be delivered in small packages to the general public.

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: Preparing for an 'official' public alpha...
« Reply #5, on February 6th, 2014, 03:38 PM »
Quote from Norodo on February 6th, 2014, 03:24 PM
I don't think you should have one to be honest. People will be whining about database changes, not being able to upgrade easily, and everything else from heaven to hell.

I think once the DB is set and there is an upgrade path, the software is ready to be delivered in small packages to the general public.
Hm.. for that it's stated as alpha not rc.


Norodo

  • Oh you Baidu, so randumb. (60 sites being indexed at once? Jeez)
  • Posts: 469
Re: Preparing for an 'official' public alpha...
« Reply #6, on February 6th, 2014, 03:41 PM »
Yeah I'm aware. But people will still be bothersome. Just check the alphas over at MyBB.

Anyway, the biggest reason to release an alpha would be to gather more bug reports and get more feedback, but currently, the main developer of Wedge is saying he's bogged down in things to do. Releasing another more easy to download alpha will only make the workload greater.

txcas

  • Bug Zapper
  • Posts: 202
Re: Preparing for an 'official' public alpha...
« Reply #7, on February 6th, 2014, 04:24 PM »Last edited on February 6th, 2014, 04:42 PM
Even though you are getting overwhelmed with bug reports, I think the codebase is pretty solid especially for Alpha code.  Most of the errors I have reported are either cosmetic, caused by a SMF migration, or it is legacy code that will eventually get deleted.  On the latest and greatest code I have found no problem that is visible to the end user, most of them are in the error logs.  I said this before and I will say it again, I find Wedge Alpha so solid that I would put in production as soon as an Ad Management plugin is released.  I am aware that will be a one way ticket with no way to return to SMF anytime soon.  While I am no longer a developer, I have worked for the software industry for over 20 years.  What some people consider whining, we consider customer feedback.  You can not put a price on customer feedback, and feedback is the whole point of having an Alpha release.  It is better to find all these bugs during the Alpha and Beta releases, than after the product is released.  Anyway, the "whiners" are the ones that one day will pay for Wedge. 

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: Preparing for an 'official' public alpha...
« Reply #9, on February 6th, 2014, 04:38 PM »Last edited on February 6th, 2014, 04:47 PM
Yes this plugin will definetly come. But first get some things stable.


I've got the right name for this plugin but i shouldn't speak it out loud :lol:

txcas

  • Bug Zapper
  • Posts: 202

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: Preparing for an 'official' public alpha...
« Reply #12, on February 9th, 2014, 01:16 AM »
It's been really hot here this afternoon, too hot to go out and I am tired from too little sleep last night so cannot do anything too complicated.

So I went through the bug reports since the pre-alpha was released and these appear to be the open ones:


Repositories - to be disabled / code removal? http://wedge.org/pub/feats/8418/tagging/msg293697/#msg293697

Theme removal http://wedge.org/pub/feats/8298/one-theme-to-rule-them-all/msg292498/#msg292498

Membergroup settings - badges http://wedge.org/pub/bugs/8387/membergroup-settings-badges/

Date format is incorrect http://wedge.org/pub/bugs/8391/date-format-is-incorrect/

Error 500 when changing gallery symbol http://wedge.org/pub/bugs/8417/aeme-error-500-while-changing-gallery-symbol/
The database value you're trying to insert does not exist: id_file http://wedge.org/pub/bugs/8416/aeme-the-database-value-you-re-trying-to-insert-does-not-exist-id_file/

Posting pictures on posts generates 8 errors http://wedge.org/pub/bugs/8414/posting-pictures-on-posts-generates-8-errors/

Adding new Media embed thingy doesn't work http://wedge.org/pub/plugins/8352/aeva-soundcloud/

follow_me() intermittent bug http://wedge.org/pub/bugs/8382/follow_me-bug-shows-up-from-time-to-time/

Calendar bugs http://wedge.org/pub/plugins/8339/calendar-plugin/msg293450/#msg293450

Importer

Rank stars not imported ?due to name change star.gif to rank.gif http://wedge.org/pub/bugs/8375/no-rank-stars/

New features for later
Soft deleting posts http://wedge.org/pub/feats/8363/multiple-recycling-bins-for-different-categories-boards/msg293084/#msg293084

Automatic updates http://wedge.org/pub/feats/8395/on-the-desirability-of-automatic-updates/