Development Cycle for 1.0.8

Posted by stylesuxx 
Development Cycle for 1.0.8
March 10, 2016 12:11AM
We have two topics dedicated to collecting ideas for the next release:
* [forum.piratebox.cc]
* [forum.piratebox.cc]

There are already quite a lot ideas. I would suggest the following time table:
* 13.3 Wishlist freeze
* 14.3 - 20.3 Planning - Work through the wishes/issues/bugs and add according issues to the github repos and assign to developers
* 21.3 - 10.4 Development - Everything that is not finished on 10.4 goes to the backlog for the next version
* 11.4 - 21.4 Testing - Dev images are build and distributed to the testers, feedback is in cooperated

Matthias, what do you think? Will this work out with your time planning?
Re: Development Cycle for 1.0.8
March 10, 2016 07:06AM
Hi,
thanks for pushing this.

I would propose the following:

* 21.3 - 21.4 Development - Everything that is not finished on 10.4 goes to the backlog for the next version
* 11.4 - 14.5 Testing - Dev images are build and distributed to the testers, feedback is in cooperated

11.4. - First Beta build
21.4. - Release Candidate 1 build
15.5. - Begin of Release build, if possible release on this day.


This gives us more opportunities for deciding what is next, like should we step to 1.1 and deliver PHP with the package.
In addition, my schedule is currently exploding. :-(

best regards
Matthias
Re: Development Cycle for 1.0.8
March 10, 2016 10:08AM
OK, this is fine with me. So lets set it in stone ;-)
Re: Development Cycle for 1.0.8
March 10, 2016 01:04PM
Should we nail this down into github-milestones?!
Re: Development Cycle for 1.0.8
March 13, 2016 04:51PM
Yeah, we can make a milestone for 1.0.8
Eco
Re: Development Cycle for 1.0.8
March 17, 2016 08:16PM
I'd like to propose macchanger in the 1.0.8 release - on the rpi.

[github.com]

It's also an installable package in raspbian.

Respect, Eco.
Eco
Re: Development Cycle for 1.0.8
March 17, 2016 08:55PM
pacman -S macchanger

and put : macchanger in /opt/piratebox/init.d/piratebox_alt

macchanger -r wlan0

Respect Eco.
Re: Development Cycle for 1.0.8
March 24, 2016 11:08AM
We will keep that in mind for the next release - wish list for 1.0.8 is closed for now.
Re: Development Cycle for 1.0.8
April 20, 2016 09:46PM
seems we are currently quite off our track regarding time and achivable targets.

I'm quite busy with fulldaytime work.. that drives me crazy, to be honest..
Re: Development Cycle for 1.0.8
April 26, 2016 09:28PM
I made some progress today (including some tests):

- Split PHP config and make it optional
- Tested my merge work for OpenWrt
- Updated jQuery to a higher version
- Fixed a bug with the init script & droopy
- Removed the multi-part php uploader and activated droopy again.

I also increase the development snapshot build cycle to "every two days" (all even days).
Re: Development Cycle for 1.0.8
May 12, 2016 08:17PM
I pushed two topics off for a next version:
- timesharing function with modification time
- mismatching urls, like board and Shared (capitalized)

Everything else is done for 1.1, I now need to prepare release-1.1 branches and prepare a first beta build... maybe at the weekend, maybe next week.
Re: Development Cycle for 1.0.8
May 29, 2016 12:44PM
I built the first beta release today: beta.openwrt.piratebox.de/auto/.

I didn't made an initial test for now, to be honest. But I'm done for today (still flu :-( ).
Re: Development Cycle for 1.0.8
June 14, 2016 07:56PM
The first checklist is online: Checklist @ Github

Requesting for Comments,
and requesting test results.
Re: Development Cycle for 1.0.8
June 15, 2016 05:02PM
Should we make a new thread for 1.1.0?


PirateBox Installs:
2x Zsun's (both testing, one with serial interface)
A5-V11 (mostly for OpenWRT testing DIY)
2x RPi Zero's
(one active in car 24/7, gets a lot of hits at Walmart, movie theaters and the mall)
2x RPi3's (both home servers, one Ubuntu custom install along side a ton of other services)
1x RPi2 (currently work server)
Re: Development Cycle for 1.0.8
June 15, 2016 08:08PM
yes, closing this one
Sorry, you can't reply to this topic. It has been closed.